From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juri Linkov <juri@jurta.org>,
Chong Yidong <cyd@stupidchicken.com>,
Emacs-Devel devel <emacs-devel@gnu.org>,
Drew Adams <drew.adams@oracle.com>,
Deniz Dogan <deniz.a.m.dogan@gmail.com>
Subject: Re: [PATCH] (Or "question"...) isearch-kill-found
Date: Tue, 1 Jun 2010 21:15:05 +0200 [thread overview]
Message-ID: <AANLkTim-U0luIOtM9Z_lxcaHirKuBq7UkaNAsPjpznqh@mail.gmail.com> (raw)
In-Reply-To: <jwvbpbulgqz.fsf-monnier+emacs@gnu.org>
On Tue, Jun 1, 2010 at 9:03 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>>>> > Why is not having a key to toggle the variable better?
>>>>> Because keys are in very short supply.
>>>> Not really, for a keymap such as isearch.
>>> Huh? Please suggest free key-bindings, then. Since keys not bound in
>>> isearch-mode-map lead to exiting isearch and running the corresponding
>>> command in the global map, isearch-mode-map is basically just as full as
>>> the global map.
>> I made another suggestion, reuse C-M-h.
>> It will not interfere with the global command in a bad manner I
>> believe. You just have to do it twice in case you want the global
>> binding. I believe it will be easy getting used to it - as long as the
>> region is visible...
>
> Your choice of C-M-h, which has no particular mnemonic or logical
> connection to the functionality you suggest,
Maybe my mnemonics and fuzzy logic are a bit wider then... ;-)
I suggested a key binding that marks something (it is normally
mark-defun) since we (at least I) wanted something to mark the matched
region.
> together with the
> argumentation about how its impact would be bearable, is a vivid proof
> of my argument: keys are in very short supply.
This conclusion is maybe a bit circular since it is the assumption I
started with ;-)
next prev parent reply other threads:[~2010-06-01 19:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 12:37 [PATCH] (Or "question"...) isearch-kill-found Deniz Dogan
2010-05-30 14:05 ` Johan Bockgård
2010-05-30 14:11 ` Deniz Dogan
2010-05-30 15:25 ` Drew Adams
2010-05-30 22:19 ` Christoph
2010-05-30 22:40 ` Lennart Borgman
2010-05-31 0:28 ` Drew Adams
2010-05-31 3:30 ` Michael Welsh Duggan
2010-05-31 15:32 ` Lennart Borgman
2010-05-31 0:48 ` Drew Adams
2010-05-30 18:36 ` Juri Linkov
2010-05-31 14:24 ` Chong Yidong
2010-05-31 15:38 ` Lennart Borgman
2010-05-31 15:54 ` Stefan Monnier
2010-05-31 16:50 ` Lennart Borgman
2010-05-31 19:14 ` Drew Adams
2010-05-31 19:50 ` Stefan Monnier
2010-05-31 20:04 ` Drew Adams
2010-06-01 3:10 ` Stefan Monnier
2010-06-01 4:43 ` Drew Adams
2010-06-01 12:56 ` Stefan Monnier
2010-06-01 13:55 ` Lennart Borgman
2010-06-01 19:03 ` Stefan Monnier
2010-06-01 19:15 ` Lennart Borgman [this message]
2010-06-01 21:03 ` Richard Stallman
2010-05-31 20:14 ` Juri Linkov
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=AANLkTim-U0luIOtM9Z_lxcaHirKuBq7UkaNAsPjpznqh@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
/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).