unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: customize-mark-as-set for M-x foo-mode
Date: Tue, 20 Aug 2002 18:12:21 -0600 (MDT)	[thread overview]
Message-ID: <200208210012.g7L0CLQ10068@wijiji.santafe.edu> (raw)
In-Reply-To: <200208192055.g7JKttB15245@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

    I see that all the minor-mode-like things in the menu-bar
    do (customize-mark-as-set 'foo).  I also saw Per's comment
    that this should only be done when the command is executed
    interactively.

    Is there any reason why it's only executed when run from the
    menu-bar rather than from M-x ?

It might be the right thing to do, and I was thinking about it,
but it calls for a lot of thought.

For one thing, there are only a few modes you can control with the
menu bar, but there are dozens, maybe hundreds, you can control
with commands.  Should all of them update your .emacs file?
Maybe they should, but that is a lot of change.

Users have written plenty of such minor mode commands.
Should they all update .emacs too?  I hesitate to think so.

Maybe it would be better if none of these commands updated .emacs
itself, and instead there were another command in the Options menu to
save the options that you can (or that you have) set with the Options
menu.

  reply	other threads:[~2002-08-21  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 20:55 customize-mark-as-set for M-x foo-mode Stefan Monnier
2002-08-21  0:12 ` Richard Stallman [this message]
2002-08-21 15:29   ` Stefan Monnier
2002-08-22  1:57     ` Richard Stallman
2002-08-22 15:23       ` Stefan Monnier
2002-08-26 12:22     ` Per Abrahamsen
2002-08-27 19:05       ` Richard Stallman
2002-08-28  0:03         ` Stefan Monnier
2002-08-28 23:32           ` 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=200208210012.g7L0CLQ10068@wijiji.santafe.edu \
    --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).