From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: nnir.el and split-string
Date: Thu, 12 Jun 2008 08:12:57 +0900 [thread overview]
Message-ID: <b4mmylrlg5i.fsf@jpl.org> (raw)
In-Reply-To: <87skvnp7pw.fsf@ID-24456.user.uni-berlin.de>
>>>>> Christoph Conrad wrote:
> Hi Katsumi,
>> Though Emacs 21 seems not to be in demand nowadays especially for
>> using with the Gnus bleeding edge.
> Probably this is true, but it's your (and my) unproved hypothesis.
>> (I vote to making Gnus drop Emacs 21 support.)
Ok, Anything should be done (or not should be done) after having
changed the regulation anyhow.
> It's very easy to emulate the third arg by using (e.g.)
> (delete "" (split-string "a,b,,c" ","))
> instead of
> (split-string "a,b,,c" "," t)
> So my vote is to make that change and keep Emacs 21 support for a while
> longer.
I've made changes in nnir.el in this way. Thanks.
next prev parent reply other threads:[~2008-06-11 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 23:37 Katsumi Yamaoka
2008-06-09 3:58 ` Christoph Conrad
2008-06-11 23:12 ` Katsumi Yamaoka [this message]
2008-06-15 12:28 ` Reiner Steib
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=b4mmylrlg5i.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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).