[Top][All Lists]

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

Re: lynx-dev lynx2.8.5dev.11

From: Thomas E. Dickey
Subject: Re: lynx-dev lynx2.8.5dev.11
Date: Mon, 2 Dec 2002 09:47:14 -0500 (EST)

On Mon, 2 Dec 2002 address@hidden wrote:

> In a recent note, Thomas Dickey said:
> > Date: Mon, 2 Dec 2002 09:01:57 -0500 (EST)
> >
> > maybe.  What the script does is to save the customizations that it finds
> > in lynx.cfg and put them on the end of the installed lynx.cfg
> >
> "finds"?  How?  Does it do a "diff" against the presumed previous

It uses grep to pick out the lines that aren't commented (and ignores the
couple of lines in the original lynx.cfg which aren't).  What is left must
be the user's customizations.

> version?  What if I skip one (or several) versions?  Do the
> differences between lynx.cfg two versions back and one version
> back appear as customizations to the latter, so enhancements you
> made may be regressed?

actually all of the saved versions may have customizations.  But my intent
was that reinstalls don't save a new version unless it differs.

> > If you apply the same changes each time, it "should" mean that you don't
> > have to apply the patch to lynx.cfg (since it would be redundant).  It
> > might be confusing if you change the customization, since what's installed
> > is read last.
> >
> I've always put my customizations to lynx.cfg inline, close to the
> comment (and the original).  Does this get me in even more trouble?

not really - they simply get moved to the end.  I would like to keep them
in context, but didn't see a way to do this (other than making some
complicated script in Perl, for instance).  Putting them on the end (and
preserving order) makes it reliable (doesn't change the meaning).

T.E.Dickey <address@hidden>

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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