From: Richard Stallman <rms@gnu.org>
Cc: abraham@dina.kvl.dk, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Eliminating "changed in Emacs outside of Customize"
Date: Sat, 05 Feb 2005 00:31:20 -0500 [thread overview]
Message-ID: <E1CxIXQ-0007XC-Kn@fencepost.gnu.org> (raw)
In-Reply-To: <878y65mnyz.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 03 Feb 2005 14:45:29 -0500)
I think it'd be useful to add a warning/prompt when saving, along the lines
of "set outside customize: saving may not work". With such a warning, we
could drop the "changed outside customize" state (well: keep it internally,
of course, but not show it to the user) and still know that users won't be
surprised when things don't work.
In effect, this would be equivalent to maintaining the two states
but treating them more or less the same aside from their names.
next prev parent reply other threads:[~2005-02-05 5:31 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:03 Eliminating "changed in Emacs outside of Customize" Richard Stallman
2005-01-31 10:33 ` Per Abrahamsen
2005-02-01 13:30 ` Richard Stallman
2005-02-01 14:32 ` Per Abrahamsen
2005-02-01 18:58 ` Drew Adams
2005-02-01 20:04 ` Stefan Monnier
2005-02-01 20:38 ` Drew Adams
2005-02-01 20:44 ` David Kastrup
2005-02-01 21:05 ` Drew Adams
2005-02-01 23:52 ` Robert J. Chassell
2005-02-01 21:19 ` Lennart Borgman
2005-02-01 21:35 ` David Kastrup
2005-02-01 22:11 ` Luc Teirlinck
2005-02-01 22:26 ` Lennart Borgman
2005-02-02 1:03 ` Luc Teirlinck
2005-02-02 1:34 ` Drew Adams
2005-02-02 2:11 ` Luc Teirlinck
2005-02-02 2:51 ` Luc Teirlinck
2005-02-03 6:40 ` Richard Stallman
2005-02-01 22:28 ` David Kastrup
2005-02-01 22:40 ` Drew Adams
2005-02-03 6:39 ` Richard Stallman
2005-02-03 7:29 ` Lennart Borgman
2005-02-05 5:27 ` Richard Stallman
2005-02-03 16:54 ` Drew Adams
2005-02-01 22:40 ` Drew Adams
2005-02-01 21:25 ` Lennart Borgman
2005-02-03 6:39 ` Richard Stallman
2005-02-02 7:57 ` Per Abrahamsen
2005-02-02 18:33 ` Drew Adams
2005-02-02 21:04 ` Lennart Borgman
2005-02-02 22:11 ` Drew Adams
2005-02-02 22:55 ` Stefan Monnier
2005-02-02 22:45 ` Luc Teirlinck
2005-02-03 15:49 ` Lennart Borgman
2005-02-03 16:12 ` Luc Teirlinck
2005-02-03 15:51 ` Lennart Borgman
2005-02-03 16:01 ` Lennart Borgman
2005-02-03 19:14 ` Richard Stallman
2005-02-04 7:27 ` Lennart Borgman
2005-02-03 19:12 ` Richard Stallman
2005-02-03 19:45 ` Stefan Monnier
2005-02-03 19:59 ` Lennart Borgman
2005-02-03 20:34 ` Stefan Monnier
2005-02-05 5:31 ` Richard Stallman [this message]
2005-02-03 20:53 ` Drew Adams
2005-02-03 22:08 ` Luc Teirlinck
2005-02-03 22:13 ` Luc Teirlinck
2005-02-04 1:04 ` Luc Teirlinck
2005-02-04 1:31 ` Luc Teirlinck
2005-02-04 3:16 ` Luc Teirlinck
2005-02-03 21:10 ` Robert J. Chassell
2005-02-03 6:39 ` Richard Stallman
2005-02-03 6:41 ` Richard Stallman
2005-02-03 14:42 ` Stefan Monnier
2005-02-03 15:23 ` Luc Teirlinck
2005-02-03 15:48 ` Luc Teirlinck
2005-02-01 15:41 ` Lennart Borgman
2005-02-02 7:40 ` Per Abrahamsen
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=E1CxIXQ-0007XC-Kn@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=abraham@dina.kvl.dk \
--cc=drew.adams@oracle.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.