all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: rms@gnu.org
Cc: Bill Wohler <wohler@newt.com>, emacs-devel@gnu.org
Subject: Re: Menu commands to M-x history?
Date: Wed, 22 Jul 2009 04:18:52 +0200	[thread overview]
Message-ID: <e01d8a50907211918k108fe895td004f55954f1136b@mail.gmail.com> (raw)
In-Reply-To: <E1MTQrZ-0002oG-Cc@fencepost.gnu.org>

On Wed, Jul 22, 2009 at 3:43 AM, Richard Stallman<rms@gnu.org> wrote:
>    > Menu commands are all commands that can be started from M-x.  I think
>    > they should be added to M-x history.
>
>    This seems like a good idea. Whether a command is run with M-x, a menu
>    item, or a button, the semantics should be identical.
>
> The only "M-x history" in Emacs is the history list used for reading
> the argument of M-x.  That should only be used for arguments that you
> enter in the M-x command.
>
> Keyboard keys also run commands that you could run with M-x, but
> putting their names in the M-x history list would not be consistent or
> useful.


It would not be useful to put commands run by keyboard keys in the
history of course since the user already knows a good way to start the
command. I therefore did not suggest that. Sorry if you misunderstod
me.

Regarding the consistency I do not mind. We do similar things in other
parts of Emacs. On this level, ie UI, the usefulness is more
important, at least to my understanding. And the history list is only
for usefulness, it's target is the user. Not the developer.


> It is the same for menu-run commands.


No. For menu-run commands the user may need some help. One of the
reasons for using menus is that you do not know the command name.

Putting the commands in the history makes it easier to remember.
Consider the case that a user used a menu command and then a while
later want to do the same thing again. Then having the command in the
history would be useful (both to new and old users, actually).

However what I wonder is if other find such a feature useful. It is
not tremendously important, but small things adds together.


> There is also command-history, which gets all commands
> that read an argument from the terminal, whether or not they
> were run from a menu.


Yes, but that is not very helpful here, or?




  parent reply	other threads:[~2009-07-22  2:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 23:05 Menu commands to M-x history? Lennart Borgman
2009-07-21  3:44 ` Bill Wohler
2009-07-22  1:43   ` Richard Stallman
2009-07-22  2:03     ` Drew Adams
2009-07-22  2:18     ` Lennart Borgman [this message]
2009-07-22  4:15     ` Bill Wohler
2009-07-22 18:34       ` Mathias Dahl
2009-07-27  1:47         ` Drew Adams
2009-07-27  9:51           ` Lennart Borgman
2009-07-27 15:48             ` Drew Adams
2009-07-27 15:59               ` Lennart Borgman
2009-07-27 16:21                 ` Drew Adams
2009-07-27 16:39                   ` Lennart Borgman
2009-07-27 18:57                     ` Drew Adams
2009-07-27 19:22                       ` Lennart Borgman
2009-07-27 20:26                         ` Drew Adams
2009-07-27 20:53                           ` Lennart Borgman
2009-07-27 21:16                             ` Drew Adams
2009-07-27 21:34                               ` Lennart Borgman
2009-07-27 21:47                                 ` Drew Adams
2009-08-01 20:20                                   ` Drew Adams
2009-08-04 17:23                                     ` Stefan Monnier
2009-07-27 22:00                 ` Mathias Dahl
2009-07-21 15:31 ` Stefan Monnier
2009-07-21 17:43   ` Lennart Borgman
2009-08-03 21:51   ` Lennart Borgman
2009-08-04 17:31     ` Sillyness (was: Menu commands to M-x history?) Stefan Monnier

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=e01d8a50907211918k108fe895td004f55954f1136b@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=wohler@newt.com \
    /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.