unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 11482@debbugs.gnu.org
Subject: bug#11482: 24.0.96; Keep `M-s' as a prefix key for search (conflict with Gnus)
Date: Tue, 15 May 2012 13:27:17 -0700	[thread overview]
Message-ID: <E87D83206F20430886CDE619EA7A72F0@us.oracle.com> (raw)
In-Reply-To: <873971gqxa.fsf@mail.jurta.org>

> > But if Gnus binds `M-s' to a command, that conflicts with 
> > the general use of `M-s' as a prefix key (for search).
> > That is the bug: Gnus should not bind `M-s' to a command.
> > `M-s' should remain a prefix key (for search).
> 
> Gnus could bind `gnus-summary-search-article-forward' to `M-s M-s'.
> It is still easy to type.

Obviously not what I was hoping for, since, as I say, Icicles uses `M-s M-s' as
a prefix key for all of its many (Icicles) search commands.

But it does satisfy the bug report, at least: it does not make `M-s' a simple
command binding.






  reply	other threads:[~2012-05-15 20:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 19:05 bug#11482: 24.0.96; Keep `M-s' as a prefix key for search (conflict with Gnus) Drew Adams
2012-05-15 19:55 ` Juri Linkov
2012-05-15 20:27   ` Drew Adams [this message]
2012-05-17  0:14     ` Juri Linkov
2012-05-17  4:44       ` Drew Adams
2012-05-17 15:23         ` Drew Adams
2014-02-09  4:09 ` Lars Ingebrigtsen
2014-02-10 22:51   ` Drew Adams
2014-02-12 14:16   ` Michael Heerdegen
2016-02-07  7:05     ` Lars Ingebrigtsen
2016-02-07  8:03       ` Drew Adams
2016-02-07 16:47         ` John Wiegley
2016-02-08  1:34           ` Lars Ingebrigtsen
2016-02-20  6:22             ` John Wiegley
2016-02-20  7:50               ` Lars Ingebrigtsen
2016-02-20  8:03                 ` John Wiegley
2016-02-20 16:40                   ` Drew Adams
2016-02-20 19:28                     ` John Wiegley
2016-02-20 20:20                       ` Drew Adams
2016-02-20 20:43                         ` John Wiegley
2016-02-20 20:41                 ` Glenn Morris

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=E87D83206F20430886CDE619EA7A72F0@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=11482@debbugs.gnu.org \
    --cc=juri@jurta.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 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).