From: cplum987@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: editing previous command in the *shell* buffer
Date: Tue, 28 Apr 2015 21:22:33 -0700 (PDT) [thread overview]
Message-ID: <a59a4ad7-262d-429e-a5f3-1c61e01d71cd@googlegroups.com> (raw)
In-Reply-To: <mailman.1854.1430266854.904.help-gnu-emacs@gnu.org>
On Tuesday, April 28, 2015 at 5:20:56 PM UTC-7, Robert Thorpe wrote:
>
> > M-r seems to be a step in the right direction. However, you don't know
> > what command line it will grab until after you press <RET>. As an
> > example, I just tried "M-r cd<RET>". It found a command with "CD" in
> > the middle of it. I wanted the one that started with "cd".
>
> It's a regex as Barry Margolin mentioned, that's one way to narrow
> things down. Another is to search further. M-r initiates a backwards
> regex isearch of history. When you meet a match C-r will continue the
> search back to the next match. (Typing M-r again switches from regex
> search to normal search).
I couldn't get M-r followed by C-r to work as you described. C-r reverts back to searching the previous pattern I searched with C-r, not the pattern I just searched with M-r.
However, I did not know that after doing the first M-r search, I could just repeatedly do "M-r <RET>" to search for previous occurrences. Still a bit awkward compared to just having to do M-p on xemacs, but at least is another step closer.
next prev parent reply other threads:[~2015-04-29 4:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 23:06 editing previous command in the *shell* buffer cplum987
2015-04-28 14:18 ` Doug Lewan
2015-04-28 17:10 ` HASM
2015-04-28 19:39 ` cplum987
2015-04-28 21:29 ` Barry Margolin
2015-04-29 0:20 ` Robert Thorpe
[not found] ` <mailman.1854.1430266854.904.help-gnu-emacs@gnu.org>
2015-04-29 4:22 ` cplum987 [this message]
[not found] ` <mailman.1792.1430230730.904.help-gnu-emacs@gnu.org>
2015-04-28 19:23 ` cplum987
2015-04-29 11:57 ` Steve Perry
2015-04-29 20:14 ` cplum987
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=a59a4ad7-262d-429e-a5f3-1c61e01d71cd@googlegroups.com \
--to=cplum987@gmail.com \
--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.