From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Inconsistency in meaning of "user options"
Date: Tue, 13 Dec 2005 18:32:52 -0500 [thread overview]
Message-ID: <E1EmJdc-0002Pg-71@fencepost.gnu.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICOEBPDAAA.drew.adams@oracle.com>
We discussed this a while back, but I agree that it would be good to come to
a conclusion. Are you proposing that we discuss and decide this _now_, and
make the necessary changes before the 22.1 release?
Yes. These are problems in changes that I've made since Emacs 21,
and we should fix them before it goes out.
prev parent reply other threads:[~2005-12-13 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 16:18 Inconsistency in meaning of "user options" Richard M. Stallman
2005-12-12 22:23 ` Drew Adams
2005-12-12 23:33 ` Lennart Borgman
2005-12-13 0:02 ` Drew Adams
2005-12-13 0:23 ` Lennart Borgman
2005-12-13 0:29 ` Drew Adams
2005-12-13 23:33 ` Richard M. Stallman
2005-12-13 23:32 ` Richard M. Stallman [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
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=E1EmJdc-0002Pg-71@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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).