From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: possible strange idea about hierarchical lists
Date: Thu, 31 Jan 2002 16:40:10 -0500 [thread overview]
Message-ID: <m3sn8mmc6n.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m3hepmt7jh.fsf@onyx.nimbus.northernlight.com> (Ted Zlatanov's message of "Wed, 16 Jan 2002 14:33:38 -0500")
Ted Zlatanov <tzz@northernlight.com> wrote:
> (let* ((recipients '(("foo@bar" . "Name <foo@bar>") ("baz@quux" . "None <baz@quux>")))
> (s recipients)
> (gnus-hierarchical-lists '( ("foo@bar" . "baz@quux"))))
> (while gnus-hierarchical-lists
> (let* ((node (pop gnus-hierarchical-lists))
> (parent (car node))
> (child (cdr node)))
> (when (and (assoc parent recipients) (assoc child recipients))
> (delq parent recipients)))))
How about this:
(let* ((recipients '(("foo@bar" . "Name <foo@bar>")
("baz@quux" . "None <baz@quux>")))
(plain-addrs (mapcar 'car recipients))
(gnus-hierarchical-lists '(("baz@quux" "foo@bar")))
sublists recip)
(while plain-addrs
(setq sublists (assoc (car plain-addrs) gnus-hierarchical-lists)
plain-addrs (cdr plain-addrs))
(when sublists
(setq sublists (cdr sublists))
(while sublists
(setq recip (assoc (car sublists) recipients)
sublists (cdr sublists))
(if recip
(setq recipients (delq recip recipients)))))))
Note that this is a different structure for gnus-hierarchical-lists.
An entry (A B C) means that A contains B and C. (No further
relationship between B and C is implied.) So if A appears in the
recipient list, then B and C will be removed from it, if present. If
B and C have sublists of their own, they should get their own
top-level entries in gnus-hierarchical-lists. In this case,
gnus-hierarchical-lists says that messages to baz@quux also go to
foo@bar, so foo@bar is removed from the recipient list.
paul
next prev parent reply other threads:[~2002-01-31 21:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 16:59 Ted Zlatanov
2001-12-04 17:31 ` Kai Großjohann
2001-12-04 17:28 ` Ted Zlatanov
2001-12-04 17:44 ` Paul Jarc
2001-12-04 17:38 ` Ted Zlatanov
2001-12-05 8:55 ` Kai Großjohann
2001-12-05 16:52 ` Matt Armstrong
2001-12-07 14:09 ` Ted Zlatanov
2001-12-29 2:02 ` Lars Magne Ingebrigtsen
2002-01-16 19:33 ` Ted Zlatanov
2002-01-16 20:12 ` Ted Zlatanov
2002-01-18 9:18 ` Kai Großjohann
2002-01-31 21:40 ` Paul Jarc [this message]
2002-02-01 22:14 ` Ted Zlatanov
2002-02-02 3:37 ` Paul Jarc
2002-02-25 23:04 ` [patch] hierarchical lists in message.el Ted Zlatanov
2002-02-25 23:22 ` Paul Jarc
2002-02-25 23:22 ` Paul Jarc
2002-02-26 11:40 ` Ted Zlatanov
2002-02-26 11:40 ` Ted Zlatanov
2002-03-01 21:23 ` Paul Jarc
2002-03-01 21:23 ` Paul Jarc
2002-03-04 17:34 ` Ted Zlatanov
2002-03-04 18:11 ` Paul Jarc
2002-03-04 18:11 ` Paul Jarc
2002-03-04 17:34 ` Ted Zlatanov
2002-02-25 23:04 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3sn8mmc6n.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).