From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2575 Path: news.gmane.org!not-for-mail From: Michael R. Wolf Newsgroups: gmane.emacs.gnus.user Subject: Re: Why asterisks in nnmail-split-fancy rule? Date: Tue, 03 Jun 2003 17:07:54 -0700 Organization: LCL Software & Training, Inc. Message-ID: References: <84znl46967.fsf@lucy.is.informatik.uni-duisburg.de> <87ptm0edoa.fsf@mail.paradoxical.net> <84vfvso03d.fsf@lucy.is.informatik.uni-duisburg.de> <4nbrxk858v.fsf@lockgroove.bwh.harvard.edu> <84he7b2yk9.fsf@lucy.is.informatik.uni-duisburg.de> <4nsmqv5nv8.fsf@lockgroove.bwh.harvard.edu> <84d6hzdw4u.fsf@lucy.is.informatik.uni-duisburg.de> <4nof1i6duy.fsf@lockgroove.bwh.harvard.edu> <848yslraqf.fsf@lucy.is.informatik.uni-duisburg.de> <84he783oju.fsf@lucy.is.informatik.uni-duisburg.de> <84n0gzzo9b.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138668959 15636 80.91.229.2 (31 Jan 2006 00:55:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:55:59 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:30:54 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: sense-sea-megasub-1-477.oz.net Original-X-Trace: quimby.gnus.org 1054686208 11937 216.39.145.223 (4 Jun 2003 00:23:28 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 4 Jun 2003 00:23:28 GMT User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.2 (windows-nt) Cancel-Lock: sha1:P8U7SoRE0iSe8GEw/X3piU7k5FQ= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2715 Original-Lines: 19 X-Gnus-Article-Number: 2715 Tue Jan 17 17:30:54 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2575 Archived-At: kai.grossjohann@gmx.net (Kai Großjohann) writes: > Michael R. Wolf writes: > >> I understand. That's how I found it. In addition, I think that >> restating the need for restriction at the message-fetch-field level >> would be helpful. > > Documented. Will commit soon. Thanks, but as Benjamin suggested, I'd prefer to see his *total* solution get applied. He did a great job of researching where the code changes should be made to bring it into alignment with the doc change. And he created a patch, too. -- Michael R. Wolf All mammals learn by playing! MichaelRunningWolf@att.net