From: Colin Rafferty <colin.rafferty@msdw.com>
Subject: Re: problem with fancy-split's ! operator; bug?
Date: 04 Feb 2000 08:08:50 -0500 [thread overview]
Message-ID: <vgvn1phktct.fsf@ms.com> (raw)
In-Reply-To: Toby Speight's message of "03 Feb 2000 19:50:52 +0000"
Toby Speight writes:
>>> Colin Rafferty <URL:mailto:colin@xemacs.org>
0> In article <vgvsnzanwqi.fsf@ms.com>,
0> > wrote:
>>> However, here is the code:
>>>
>>> ;; Builtin ! operation.
>>> ((eq (car split) '!)
>>> (funcall (cadr split) (nnmail-split-it (caddr split))))
>>>
>>> It should be this (to match `:'):
>>>
>>> ;; Builtin ! operation.
>>> ((eq (car split) '!)
>>> (nnmail-split-it (save-excursion (funcall (cadr split) (nnmail-split-it (caddr split))))))
>>>
>>> I'm not sure that Lars should change the code to match documentation,
>>> since there may be many people out there who depend on this.
> Can you give an example of something that works with the former code,
> that behaves differently in the latter?
Just about anything. Since the former code expects a list of groups
in which to put the mail, and the latter code expects a split to
parse, pretty much anything will owrk differently.
For example, if I had a .gnus that looked like this:
(defun test-split (dummy)
'("one "two"))
(setq nnmail-split-fancy '(! test-split "dummy"))
Then in the former, the resulting split would be ("one" "two"), but in
the latter, the resulting split would be ("one").
--
Colin
next prev parent reply other threads:[~2000-02-04 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-02 0:10 Matt Swift
2000-02-02 17:24 ` Colin Rafferty
2000-02-03 4:07 ` Matt Swift
2000-02-03 15:15 ` Colin Rafferty
2000-02-03 19:50 ` Toby Speight
2000-02-04 13:08 ` Colin Rafferty [this message]
2000-02-04 15:44 ` Toby Speight
2000-02-04 19:07 ` Colin Rafferty
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=vgvn1phktct.fsf@ms.com \
--to=colin.rafferty@msdw.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).