[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Cookies and command line operation

From: Klaus Weide
Subject: Re: lynx-dev Cookies and command line operation
Date: Sun, 31 Oct 1999 11:13:42 -0600 (CST)

On Sat, 30 Oct 1999 address@hidden wrote:

> >29-Oct-99 20:48 Klaus Weide wrote:
> >> So here's a somewhat different idea: A 'save_cookies' flag that
> >> tells lynx whther to *write* cookies to file or not.
> >> In interactive mode, default is
> >>  - ON if persistent cookies are enabled
> >>  - OFF if persistent cookies are disabled
> >> In noninteractive mode, default is
> >>  - OFF
> So does this mean in the options menu there will be the existing Cookies 
> item and a Save Cookies item?

That's only a consequence if you belong to the "every config option must
also be a command line flag must also be configurable at runtime" school
of thought, which I don't.

> Though I thought I'd never say it, it seems as if there's almost too many
> options..  

Well that's the (or:: one) reason why the Forms Options Thingie was made:
so new stuff can be added without space problems.  You can continue to
use the old-style Non-Forms Option Thingie.

> Though if someone were arguing to get rid of cookies I'd say make
> it an option.. heh.

There is no need for a new option to "get rid of cookies", I believe.

> >> I am not sure whether this should be command line flag, lynx.cfg option,
> >> or both, but probably both.
> >
> >> What do you think?  (And what do the consumers-of-cookies think?)
> Well, I hope I could set it up from the options menu so I don't have to
> give a command line option (obviously I could add it to an alias like I 
> already
> do for the other options I use for my 'generic' Lynx alias, 
> lynx -nopause -pseudo_inlines -nolist).

If with the "it" you mean my proposal, then you wouldn't need to do
anything except if you really want to have cookies saved when using
-dump or -source.

> I don't think I'd ever use this explicitly, since I use persistent cookies and
> obviously want them saved..

Even when using -dump or -source?  One may or may not want to have cookies
saved in that case, and may wish the behavior to be different from the
interactive case.  That's all this is (or, initially was) about.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]