Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!rpi!tale
From: tale@pawl.rpi.edu (David C Lawrence)
Newsgroups: comp.emacs
Subject: Re: possible s-expr management error (? naw, but ...)
Message-ID: <1989Nov16.061626.22143@rpi.edu>
Date: 16 Nov 89 06:16:26 GMT
References: <8911160201.AA04995@NMSU.Edu> <31688@news.Think.COM>
Organization: Rensselaer Polytechnic Institute, Troy NY
Lines: 28

In article <8911160201.AA04995@NMSU.Edu> jthomas@NMSU.EDU writes:
Jim> I realize this scenario is a bit hard to believe, but has anyone
Jim> else seen something like this?  I looks to me as if the pointers
Jim> for the unsub and newsrc lists have gotten too intermingled.  Or
Jim> am I dreaming?

I've not seen the problem at all with multiple invocations of the hook
daily since I wrote it; that does not mean, however, that there isn't
a problem.  Perhaps I am have just never done whatever it was that
triggered this for you.  If you could please send me more information
on the problem I would be happy (well, sorta ... :-) to work through
it with you.

In <31688@news.Think.COM> barmar@leander.think.com (Barry Margolin) writes:
Barry> SORT is a destructive operation; it actually reorders the
Barry> original list by rearranging the cdr chain.  [...]

Barry> The above code should then be changed to
Barry> (setq gnus-unsub-assoc (sort (copy-list gnus-unsub-assoc) 'gnus-assoc-lessp))

It should not.  That screws the function up.  I used sort because
sort was what I wanted.  I am well aware of the lisp functions which
directly alter list structure and the usage of both sort and setcdr in
the function was for exactly that behaviour.

Dave
-- 
 (setq mail '("tale@pawl.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))