From: David Kastrup <dak@gnu.org>
Cc: lennart.borgman.073@student.lu.se, eliz@gnu.org, jasonr@gnu.org,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Options menu
Date: Tue, 22 Mar 2005 00:35:52 +0100 [thread overview]
Message-ID: <x5sm2ok1wn.fsf@lola.goethe.zz> (raw)
In-Reply-To: <200503212328.j2LNSkd28100@raven.dms.auburn.edu> (Luc Teirlinck's message of "Mon, 21 Mar 2005 17:28:46 -0600 (CST)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Lennart Borgman wrote:
>
> > As I mentioned before, I think the sanest way would be to have
> > "Save Options" prompt "Options have been set by Customize.
> > Save them too?"
>
> Agree. This would be much less surprising than the current
> situation and as far as I remember our discussions it would not
> be too difficult to implement.
>
> Any of this should _clearly_ wait till after the release. It very
> much depends on what happens with the Custom discussion,
I don't see that at all. Customize is involved only as far as it is a
menu entry in the "Options" menu and can be used to set options in a
different way.
This will not change at all.
> which we can not afford to re-open right now.
Correct, but I don't see how it would be relevant.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-03-21 23:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 8:54 Options menu Kim F. Storm
2005-03-18 10:31 ` David Kastrup
2005-03-18 12:57 ` Kim F. Storm
2005-03-18 14:58 ` Chong Yidong
2005-03-18 22:56 ` Lennart Borgman
2005-03-19 10:20 ` Eli Zaretskii
2005-03-19 11:24 ` David Kastrup
2005-03-19 15:32 ` Eli Zaretskii
2005-03-19 15:55 ` David Kastrup
2005-03-19 15:51 ` Lennart Borgman
2005-03-19 16:51 ` David Kastrup
2005-03-19 17:22 ` Eli Zaretskii
2005-03-19 18:18 ` Lennart Borgman
2005-03-20 12:59 ` Richard Stallman
2005-03-20 16:26 ` David Kastrup
2005-03-20 16:58 ` Luc Teirlinck
2005-03-20 17:31 ` David Kastrup
2005-03-20 17:43 ` Luc Teirlinck
2005-03-20 18:06 ` David Kastrup
2005-03-21 1:19 ` Richard Stallman
2005-03-21 1:19 ` Richard Stallman
2005-03-20 19:31 ` Lennart Borgman
2005-03-20 20:49 ` David Kastrup
2005-03-20 20:45 ` Jason Rumney
2005-03-20 21:40 ` David Kastrup
2005-03-20 22:27 ` Lennart Borgman
2005-03-20 23:10 ` Luc Teirlinck
2005-03-21 0:02 ` David Kastrup
2005-03-21 1:26 ` Luc Teirlinck
2005-03-22 3:34 ` Richard Stallman
2005-03-21 1:41 ` Luc Teirlinck
2005-03-21 6:12 ` Lennart Borgman
2005-03-21 23:28 ` Luc Teirlinck
2005-03-21 23:35 ` David Kastrup [this message]
2005-03-21 23:50 ` Luc Teirlinck
2005-03-22 0:15 ` David Kastrup
2005-03-22 6:20 ` Lennart Borgman
2005-03-22 20:44 ` Richard Stallman
2005-03-22 22:37 ` David Kastrup
2005-03-20 22:12 ` Miles Bader
2005-03-18 15:48 ` Drew Adams
2005-03-18 20:30 ` Eli Zaretskii
2005-03-18 20:53 ` Drew Adams
2005-03-19 10:13 ` Eli Zaretskii
2005-03-19 3:08 ` Richard Stallman
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=x5sm2ok1wn.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=rms@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).