From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Gilaras Drakeson <gilaras@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: space, M-x
Date: Mon, 10 Nov 2008 16:43:36 -0500 [thread overview]
Message-ID: <jwvej1jpdx9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86fxlz8q85.fsf@comm.utoronto.ca> (Gilaras Drakeson's message of "Mon, 10 Nov 2008 12:07:06 -0500")
> One is the ability to enter the arguments "naturally", the way you use a
> shell. It is more comfortable to see the whole command (with arguments)
> on the same line/in the same area. Sometimes the user wants to go back
> and edit previous arguments, or even the command name.
> The other is to have the command and its arguments in the history.
> Imagine that you want to (do-thing arg1-1 arg2), then (do-thing arg1-2
> arg2), (do-thing arg1-3 arg2), etc. Currently doing this can be a
> hassle, unless you use eval-expression in which case you lose the other
> benefits of M-x, e.g., hand-crafted tab completion. It would be handier
> if you could type "replace-regex<Up>" and see the arguments to your
> previous invocations of replace-regex.
I see what you mean. repeat-complex-command may be a way to get some of
what you want. Not that it does just what you want, but I think that
getting really what you want is going to require a lot of work.
Stefan
prev parent reply other threads:[~2008-11-10 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 18:49 space, M-x Gilaras Drakeson
2008-11-10 1:39 ` Stefan Monnier
2008-11-10 17:07 ` Gilaras Drakeson
2008-11-10 17:47 ` Jim Blandy
2008-11-14 3:19 ` Stephen J. Turnbull
2008-11-14 18:58 ` Jim Blandy
2008-11-15 8:39 ` Stephen J. Turnbull
2008-11-15 19:30 ` Stefan Monnier
2008-11-10 21:43 ` Stefan Monnier [this message]
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=jwvej1jpdx9.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=gilaras@gmail.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 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).