all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: repeat the last single shell command
Date: Thu, 18 Jul 2013 15:07:43 -0400	[thread overview]
Message-ID: <barmar-A8F9B3.15074318072013@news.eternal-september.org> (raw)
In-Reply-To: mailman.1343.1374163702.12400.help-gnu-emacs@gnu.org

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

In article <mailman.1343.1374163702.12400.help-gnu-emacs@gnu.org>,
 Yuri Khan <yuri.v.khan@gmail.com> wrote:

> On Thu, Jul 18, 2013 at 9:18 PM, Tassilo Horn <tsdh@gnu.org> wrote:
> 
> > That ties it to `shell-command'.  You could bind the other version also
> > in `minibuffer-local-map', and then `M-: !' would reevaluate the last
> > lisp expression, `M-! !' would reexecute the last shell command, `M-x !'
> > would execute the last complex command, `C-x C-f !'  would find the last
> > found file, `C-x b !' would switch to the last switched to buffer, etc.
> 
> That kind of misses the point, which for M-! ! is the fact that it’s
> easy to type — because of finger position caching. (I’d maybe even go
> as far as making it M-! M-!.) After M-: or M-x, ! is not in the cache.

M-! M-! makes quite a bit of sense, and avoids the problem someone else 
mentioned about making it hard to use ! in a command. I could see 
generalizing this: M-x M-x should recall the last extended command, M-: 
M-: should recall the last eval-expression, etc.

This assumes you're typing the commands with a real Meta key, since it's 
easier to keep your finger on it while you repeat the character. If 
you're using an ESC prefix to emulate Meta, ESC ! ! would be more 
intuitive, I think.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


  parent reply	other threads:[~2013-07-18 19:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  9:00 repeat the last single shell command Luca Ferrari
     [not found] ` <CAKcmqqyD8e2bX99NHMKG0h+fdF=U66mBsJ-W=4ygtmvJgNGaGA@mail.gmail.com>
2013-07-18  9:55   ` Luca Ferrari
2013-07-18 11:35     ` Suvayu Ali
2013-07-18 12:34       ` Luca Ferrari
2013-07-18 12:42     ` Nicolas Richard
2013-07-18 13:24       ` Tassilo Horn
2013-07-18 13:52         ` Nicolas Richard
2013-07-18 14:18           ` Tassilo Horn
2013-07-18 16:08             ` Yuri Khan
     [not found]             ` <mailman.1343.1374163702.12400.help-gnu-emacs@gnu.org>
2013-07-18 19:07               ` Barry Margolin [this message]
     [not found]       ` <mailman.1333.1374153910.12400.help-gnu-emacs@gnu.org>
2013-07-18 14:45         ` Barry Margolin
2013-07-18 10:33 ` Peter Dyballa
2013-07-18 13:11 ` Tassilo Horn
2013-07-18 14:01   ` Luca Ferrari
2013-07-18 14:12   ` Nicolas Richard
2013-07-18 14:22     ` Tassilo Horn

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=barmar-A8F9B3.15074318072013@news.eternal-september.org \
    --to=barmar@alum.mit.edu \
    --cc=help-gnu-emacs@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 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.