unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3746@emacsbugs.donarmstrong.com, 'Dan Nicolaescu' <dann@ics.uci.edu>
Subject: bug#3746: M-r in comint mode should use isearch
Date: Thu, 09 Jul 2009 02:27:45 +0300	[thread overview]
Message-ID: <87zlbf1kr0.fsf@mail.jurta.org> (raw)
In-Reply-To: <30EDDB5AC92A422E87D113B0A49C500E@us.oracle.com> (Drew Adams's message of "Tue, 7 Jul 2009 22:53:29 -0700")

> The general objection is rather Occam's razor: _Why_ add such complexity?
> What is gained? Occasionally the added convenience of having a single key
> to use makes a DWIM command worth it. But usually not.

This case is an exception.

C-r is the most frequent key I use in bash running in xterm because
it is very convenient to search for old commands in the shell history.
I suppose the same is true for other users.

Using a different key in Emacs for the same functionality
will cause too much trouble.  Just imagine when you have a habit
typing C-r to search on the shell history, typing it in the Emacs
shell buffer will not do what you mean.  This recalls that
Emacs has a different key M-r.  Then switching back to xterm
and typing M-r: Ahh, that M-r is valid only in Emacs,
but in xterm it is C-r.  Arrrgh!

I think having two different keys for the same functionality
(C-r and M-r for Isearch on the history) is worse than having
the same key for different contexts (the shell prompt or the
rest of the shell buffer).

-- 
Juri Linkov
http://www.jurta.org/emacs/





  reply	other threads:[~2009-07-08 23:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ocmknicw.fsf@mail.jurta.org>
2009-07-03 13:26 ` bug#3746: M-r in comint mode should use isearch Dan Nicolaescu
2009-07-03 23:36   ` Juri Linkov
2009-07-05 15:03     ` Dan Nicolaescu
2009-07-07  0:09       ` Juri Linkov
2009-07-07  1:21         ` Dan Nicolaescu
2009-07-08  0:45           ` Juri Linkov
2009-07-08  5:53             ` Drew Adams
2009-07-08 23:27               ` Juri Linkov [this message]
2009-07-08 23:42                 ` Lennart Borgman
2009-07-09 15:01                 ` Drew Adams
2009-07-09 22:16                   ` Juri Linkov
2009-07-09 22:32                     ` Drew Adams
2009-07-09 23:05                       ` Juri Linkov
2009-07-09 23:15                         ` Drew Adams
2009-07-08 23:49             ` Dan Nicolaescu
2009-07-09 22:19               ` Juri Linkov
2009-11-19 17:30                 ` Juri Linkov
2009-11-19 21:12                   ` Stefan Monnier
2009-11-20  9:28                     ` Juri Linkov
2009-11-23 20:39                     ` Juri Linkov
2009-11-30 16:30   ` bug#3746: marked as done (M-r in comint mode should use isearch) Emacs bug Tracking System

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=87zlbf1kr0.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=3746@emacsbugs.donarmstrong.com \
    --cc=dann@ics.uci.edu \
    --cc=drew.adams@oracle.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).