From: jimka <jimka@rdrop.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs shell cursor movement is broken in 22.1
Date: Sun, 16 Mar 2008 09:03:22 -0700 (PDT) [thread overview]
Message-ID: <c5c622c9-1a54-485b-9231-ee7045cf5320@x30g2000hsd.googlegroups.com> (raw)
In-Reply-To: mailman.8981.1205682606.18990.help-gnu-emacs@gnu.org
On Mar 16, 4:49 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
>
> Why do you useshellmechanisms? GNU Emacs has more efficient ways to
> retrieve an elderlyshellcommand ... (comint-previous-matching-input
> or M-r for example)
>
>
> Pete
>
yes it is always the case with emacs that there is a more
efficient way in terms of fewer keystokes. but i think the
question of how to most efficiently do a job-X in emacs
is an independent question from why did the full-screen-editing
features of the emacs shell regress. Don't you agree?
By the way i do often use C-r to find the previous comand which
matches some pattern and either press enter twice to
execute it again, or press enter to leave the search mode,
then edit the command and enter it again. C-r has a great advantage
over M-r because it lets me see the context in which something
happened
and also lets me match things that were not shell commands
at all but might look like shell commands.
-jim
next prev parent reply other threads:[~2008-03-16 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 20:44 emacs shell cursor movement is broken in 22.1 jimka
2008-03-15 2:41 ` wainstead
2008-03-15 15:01 ` jimka
2008-03-26 20:43 ` wainstead
2008-03-26 20:45 ` wainstead
2008-03-16 0:42 ` Jason Rumney
2008-03-16 15:31 ` jimka
2008-03-16 15:49 ` Peter Dyballa
[not found] ` <mailman.8981.1205682606.18990.help-gnu-emacs@gnu.org>
2008-03-16 16:03 ` jimka [this message]
2008-03-16 16:59 ` Drew Adams
[not found] ` <mailman.8984.1205686774.18990.help-gnu-emacs@gnu.org>
2008-03-16 17:51 ` jimka
2008-03-16 19:16 ` Drew Adams
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=c5c622c9-1a54-485b-9231-ee7045cf5320@x30g2000hsd.googlegroups.com \
--to=jimka@rdrop.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.
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).