Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <teodor.zlatanov@divine.com>
Subject: Re: [patch] hierarchical lists in message.el
Date: Tue, 26 Feb 2002 06:40:19 -0500	[thread overview]
Message-ID: <a5fsnr$16m$1@quimby2.netfonds.no> (raw)
In-Reply-To: <m3r8n9du4g.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Mon, 25 Feb 2002 18:22:17 -0500")

prj@po.cwru.edu (Paul Jarc) writes:

> Ted Zlatanov <teodor.zlatanov@divine.com> wrote:
>> It being the first patch I've done for Gnus, I don't know if it
>> should go to the list or to someone in particular.
>
> This is the place for it.  Have you signed the copyright paperwork?

No, can someone get in touch with me?

>> +(defcustom message-hierarchical-lists nil
>> +  "A list of hierarchical mailing list definitions.
>> +
>> +Inside each entry, the first address is the top list, everything after
>> +it are secondary addresses contained in the list.  The secondaries
>> +will be removed from the list of recipients when mail is prepared for
>> +delivery."
>> +  :group 'message-headers)
>
> We should also say that secondaries of secondaries, and so on, will be
> removed, and it probably would be good to spell out more explicitly
> that this is a way for the user to express to Gnus that messages sent
> to the first address are automatically delivered to the others, which
> is *why* Gnus will remove the subordinates, so no one is left
> wondering when this thing would be useful.  Maybe that would be better
> off in the manual than in the docstring; the manual could also give an
> example.  I also don't quite like the word "secondaries" (maybe
> "sublists"?) but that's just a nit.

Detailed instructions should definitely go in the manual.  "sublists"
does sound better than "secondaries."

>> +      ;; remove hierarchical lists that are contained within each other,
>> +      ;; if message-hierarchical-lists is defined
>> +      (when message-hierarchical-lists
>
> It happens that this "when" test is not strictly necessary; the code
> will have nothing to remove if m-h-l is empty.  But maybe this is
> still a worthwhile optimization for the common case.

Yes, I think it improves the code for someone glancing through it -
they don't have to figure out the logic to see that it will do nothing
without m-h-l (code comments being the first thing no one reads :)

Thanks
Ted




  parent reply	other threads:[~2002-02-26 11:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 16:59 possible strange idea about hierarchical lists 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
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:04                       ` Ted Zlatanov
2002-02-25 23:22                         ` Paul Jarc
2002-02-26 11:40                           ` Ted Zlatanov
2002-02-26 11:40                           ` Ted Zlatanov [this message]
2002-02-25 23:22                         ` Paul Jarc
2002-03-01 21:23                         ` Paul Jarc
2002-03-01 21:23                         ` Paul Jarc
2002-03-04 17:34                           ` Ted Zlatanov
2002-03-04 17:34                           ` Ted Zlatanov
2002-03-04 18:11                             ` Paul Jarc
2002-03-04 18:11                             ` Paul Jarc

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='a5fsnr$16m$1@quimby2.netfonds.no' \
    --to=teodor.zlatanov@divine.com \
    /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).