From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Re: Save Options vs. default-input-method
Date: Thu, 07 Feb 2002 17:50:47 +0100 [thread overview]
Message-ID: <rju1sts0bc.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <200202071457.g17Ev6P04620@aztec.santafe.edu> (Richard Stallman's message of "Thu, 7 Feb 2002 07:57:06 -0700 (MST)")
Richard Stallman <rms@gnu.org> writes:
> I think we are having a miscommunication. You argued that it is wrong
> to use custom-save-all for the options menu. I said your argument was
> convincing and I agree. Then you went ahead and rewrote the options
> menu to use custom-save-all.
I argued against customize-save-variable, there isn't any way around
custom-save-all. Despite it name, it doesn't save all, only those
options that have explicitly been marked for saving.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-07 16:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3665k6ayy.fsf@Janik.cz>
[not found] ` <200201302237.g0UMb1d24844@aztec.santafe.edu>
[not found] ` <m3sn8jbzs6.fsf@Janik.cz>
[not found] ` <200202040927.g149RUF02434@aztec.santafe.edu>
[not found] ` <m3ofj5fs5i.fsf@Janik.cz>
[not found] ` <rjbsf57anr.fsf@ssv2.dina.kvl.dk>
[not found] ` <200202051248.g15CmDb02207@aztec.santafe.edu>
[not found] ` <rju1svzxxx.fsf@ssv2.dina.kvl.dk>
2002-02-07 14:57 ` [PATCH] Re: Save Options vs. default-input-method Richard Stallman
2002-02-07 17:41 ` Per Abrahamsen
2002-02-07 21:15 ` Pavel Janík
2002-02-08 7:50 ` Per Abrahamsen
2002-02-07 14:57 ` Richard Stallman
2002-02-07 16:50 ` Per Abrahamsen [this message]
2002-02-08 23:23 ` Richard Stallman
[not found] ` <rjpu3jzwyd.fsf_-_@ssv2.dina.kvl.dk>
2002-02-07 14:57 ` [PATCH] text-mode-hook-identify should be part of the standard value for text-mode-hook Richard Stallman
2002-02-07 16:27 ` Per Abrahamsen
2002-02-08 23:23 ` Richard Stallman
2002-02-09 11:38 ` Per Abrahamsen
2002-02-11 2:08 ` Richard Stallman
2002-02-13 18:04 ` ShengHuo ZHU
[not found] ` <rjlme7zwja.fsf@ssv2.dina.kvl.dk>
2002-02-07 14:57 ` [PATCH] Re: Save Options vs. default-input-method Richard Stallman
2002-02-07 16:31 ` Per Abrahamsen
[not found] ` <200202100517.g1A5Hoe06105@aztec.santafe.edu>
[not found] ` <rjlme17mhm.fsf@ssv2.dina.kvl.dk>
[not found] ` <200202110209.g1B29mh06648@aztec.santafe.edu>
2002-02-11 17:15 ` Per Abrahamsen
2002-02-12 9:56 ` Per Abrahamsen
2002-02-13 15:38 ` Richard Stallman
2002-02-12 15:23 ` Richard Stallman
2002-02-12 16:39 ` Per Abrahamsen
2002-02-12 15:23 ` Richard Stallman
2002-02-12 16:24 ` Per Abrahamsen
2002-02-14 3:11 ` Richard Stallman
2002-02-14 9:34 ` Per Abrahamsen
2002-02-15 10:36 ` Richard Stallman
2002-02-17 10:31 ` Per Abrahamsen
2002-02-17 22:50 ` Richard Stallman
2002-02-19 10:31 ` 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
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=rju1sts0bc.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--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).