unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: Defaults for set-variable
Date: Wed, 09 Nov 2005 14:17:43 +0100	[thread overview]
Message-ID: <m31x1qkljc.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87lkzychhv.fsf@jurta.org> (Juri Linkov's message of "Wed, 09 Nov 2005 11:34:22 +0200")

Juri Linkov <juri@jurta.org> writes:

>>      > I see only one way to avoid this inconsistency - to have two
>>      > commands: `set-variable' for setting variables, and
>>      > `set-user-option' for setting user options.
>>
>>     Why not `C-u M-x set-variable' to set any variable (not just user
>>     options), just like `C-u M-x apropos-variable' shows all variables.
>>
>> I would have proposed that long ago, but `C-u' is already defined to
>> set the variable buffer locally.
>
> `C-u C-u M-x set-variable'?

And `C-u C-u C-u M-x set-variable' 
is used to set the buffer-local value of any variable... 

1/2 :-)


I would rather reserve C-u M-x set-variable for set any
variable, and make a new command

  M-x set-variable-buffer-local

to set the buffer local value.  It would also have a C-u prefix to
allow setting any variable.


However, if we _don't_ change this, I think it would make a lot
of sense if C-u M-x set-variable changed to prompt from
"Set variable" to "Set variable in <buffer>".


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2005-11-09 13:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 15:35 Defaults for set-variable Juri Linkov
2005-10-17 21:58 ` Richard M. Stallman
2005-10-19 15:43   ` Juri Linkov
2005-10-20  4:54     ` Richard M. Stallman
2005-10-31 19:22 ` Drew Adams
2005-10-31 21:20   ` Miles Bader
2005-10-31 22:15     ` Drew Adams
2005-10-31 23:17       ` Miles Bader
2005-11-01  0:49         ` Drew Adams
2005-11-01  2:00           ` Miles Bader
2005-11-01 11:29         ` Kim F. Storm
2005-11-01  9:15   ` Juri Linkov
2005-11-01 13:35     ` David Kastrup
2005-11-01 14:05       ` Miles Bader
2005-11-02 10:27     ` Richard M. Stallman
2005-11-02 16:22       ` Drew Adams
2005-11-02 20:41         ` Sascha Wilde
2005-11-03  7:52           ` Juri Linkov
2005-11-03  8:53             ` Sascha Wilde
2005-11-03 16:08               ` Drew Adams
2005-11-04  1:46                 ` Miles Bader
2005-11-04 12:07                   ` Juri Linkov
2005-11-04 12:35                     ` David Kastrup
2005-11-05  9:44                       ` Juri Linkov
2005-11-08 19:45                         ` Kevin Rodgers
2005-11-08 22:05                           ` Drew Adams
2005-11-09  9:34                             ` Juri Linkov
2005-11-09 13:17                               ` Kim F. Storm [this message]
2005-11-09 17:54                                 ` Juri Linkov
2005-11-10  2:09                               ` Richard M. Stallman
2005-11-03 13:51         ` Richard M. 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=m31x1qkljc.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.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 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).