From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: eliz@gnu.org, emacs-devel@gnu.org, rms@gnu.org, jasonr@gnu.org
Subject: Re: Options menu
Date: Sun, 20 Mar 2005 17:10:48 -0600 (CST) [thread overview]
Message-ID: <200503202310.j2KNAmk09163@raven.dms.auburn.edu> (raw)
In-Reply-To: <002e01c52d9c$000e4350$0200a8c0@sedrcw11488> (lennart.borgman.073@student.lu.se)
Lennart Borgman wrote:
3) Choose menu "Save Options".
What happens on your computer? On my computer debug-on-error is saved as far
as I can see.
If I understood the code in menu-bar.el correctly (I did not try out
anything), then an oversimplified description of the situation if you
choose "Save Options" is:
1. The following options get saved if their value was set
either through the menu bar _or_ through Custom.:
scroll-bar-mode debug-on-quit debug-on-error menu-bar-mode
tool-bar-mode save-place uniquify-buffer-name-style fringe-mode
fringe-indicators case-fold-search display-time-mode
auto-compression-mode current-language-environment default-input-method
text-mode-hook.
In as far as text-mode-hook is concerned, the entire current value of
text-mode hook gets saved, not just the part mentioned in the Options
Menu. This could easily be inappropriate. All one can do is hope for
the better.
2. The following options get saved to the custom-set-variables form,
no matter how they got their value:
line-number-mode column-number-mode cua-mode show-paren-mode
transient-mark-mode global-font-lock-mode blink-cursor-mode
3. Other options never get saved.
I believe that we might have to clean this situation up after the
release, as part of making changes and bug fixes to Custom.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-03-20 23:10 UTC|newest]
Thread overview: 49+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2005-08-23 8:45 Baloff
2005-08-23 8:47 ` Sébastien Kirche
2005-08-24 16:58 ` Baloff
2005-08-25 0:40 ` Sean Sieger
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=200503202310.j2KNAmk09163@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--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 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.