From: Richard Stallman <rms@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: Re: gnus-summary-catchup turns ticked into unread
Date: Thu, 16 Aug 2007 14:39:18 -0400 [thread overview]
Message-ID: <E1ILkFa-0007g0-VK@fencepost.gnu.org> (raw)
In-Reply-To: <b4mhcn0s0pf.fsf@jpl.org> (message from Katsumi Yamaoka on Thu, 16 Aug 2007 10:54:52 +0900)
I worry that changing the arguments list of such a generic function
in Emacs causes further confusion.
I think that compatibility in the long term will do more good
than the short-term confusion.
We might, if anything, give up using that argument, since it doesn't
seem to be very important in the codes in question actually.
That means that Gnus can easily avoid being affected the confusion.
Right?
So I conclude it is ok to change this.
It also
might suggest that such arguments that are not indispensable and are
incompatible with versions of Emacsen will be doomed to be not used.
I think that an arg which is compatible between future Emacs versions
and XEmacs could be used easily enough, when there is a need to use it.
So I tend to think we should go ahead with this change,
unless there is some other reason not to.
next prev parent reply other threads:[~2007-08-16 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070702160929.C21251C8115@galatea.esat.kuleuven.be>
[not found] ` <b4mmyydn5r2.fsf@jpl.org>
[not found] ` <b4m64501nt8.fsf@jpl.org>
[not found] ` <E1I6GBH-0006d2-HI@fencepost.gnu.org>
[not found] ` <b4mejjn1usy.fsf@jpl.org>
[not found] ` <E1I6Y2D-00062v-Iq@fencepost.gnu.org>
[not found] ` <b4mr6nhjgq1.fsf@jpl.org>
[not found] ` <E1I8Nlq-0000oX-F6@fencepost.gnu.org>
[not found] ` <b4mps2zzivn.fsf@jpl.org>
2007-08-06 14:22 ` gnus-summary-catchup turns ticked into unread Richard Stallman
2007-08-14 0:28 ` Richard Stallman
2007-08-16 1:54 ` Katsumi Yamaoka
2007-08-16 18:39 ` Richard Stallman [this message]
2007-08-17 1:22 ` Katsumi Yamaoka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1ILkFa-0007g0-VK@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).