From: Colin Rafferty <colin@xemacs.org>
Subject: Re: problem with fancy-split's ! operator; bug?
Date: 04 Feb 2000 14:07:40 -0500 [thread overview]
Message-ID: <vgvwvokkcqr.fsf@ms.com> (raw)
In-Reply-To: Toby Speight's message of "04 Feb 2000 15:44:41 +0000"
Toby Speight writes:
> Colin Rafferty writes:
>> Toby Speight writes:
>>> 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.
> Did this used to work at one time? I have old code which I don't use
> any more, which looks like
I guess if you used to use it, then the it must have worked as
advertised at one point, and now it doesn't.
I'll submit a patch.
--
Colin
prev parent reply other threads:[~2000-02-04 19:07 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
2000-02-04 15:44 ` Toby Speight
2000-02-04 19:07 ` Colin Rafferty [this message]
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=vgvwvokkcqr.fsf@ms.com \
--to=colin@xemacs.org \
/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).