[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev cookie file observation/question
From: |
dickey |
Subject: |
Re: lynx-dev cookie file observation/question |
Date: |
Fri, 28 May 1999 05:18:02 -0400 (EDT) |
> On Thu, May 27, 1999, brian j. pardy (address@hidden) said:
> |
> | > A curiousity that I've noticed, is that on each lynx invocation,
> | > the new .cookie file that is written upon exiting lynx, is written
> | > in the reverse order of the pre-invocation file (ie, invoke/exit
> | > lynx twice in a row, and the .cookie file is back to the original
> | > order).
> |
> | Indeed that does happen, and led me down quite a few incorrect paths
> | when I was attempting to debug the trunc problems. It's an annoyance
> | more than anything, AFAICT it is not being done for a reason -- it's
> | just an artifact of how they're stored in cookie_list (in store_cookie())
> | when read from the file. Each new cookie is inserted at the head of
> | the list, not at the end.
>
> In case you haven't seen it yet, in one of the recent -pre.n distributions
> (pre.6 or pre.7, IIRC), Tom seems to have fixed this, so that now the
> .cookie file is written the same on each invocation (cookies now get
> added to the end of the internal list).
yes (there appears to be nothing broken by appending to the end, right?)
> /kim
--
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey