unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Marco Wahl <marcowahlsoft@gmail.com>,
	"60960@debbugs.gnu.org" <60960@debbugs.gnu.org>
Subject: bug#60960: 30.0.50; Keybinding for Info-search-next in info-mode
Date: Fri, 20 Jan 2023 17:26:53 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488B86EB3F8B5AE5E369199F3C59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CALGqPpbdmJAnfkTEn1evcB93EoN_arP2VUNEEeSY=EqdnOEi1Q@mail.gmail.com>

> AFAICS there is no keybinding for function Info-search-next in
> info-mode. This is the suggestion to add a respective binding.
> BTW I use the binding (define-key Info-mode-map (kbd "a")
> #'Info-search-next).

FWIW, in `info+.el' I bind `a' to `info-apropos'.

> Without this setting one could achive the same effect by pressing key "s"
> followed by RET which I find tiring compared to pressing just one key.

Any user can of course bind `Info-search-next'
to a key.

But I wonder how many users even use `s' these
days - as opposed to `C-M-s'.  Is there a
particular use case for it?  I may have just
forgotten that.

I can see how it might be convenient to have
different regexps remembered for `s' and `C-M-s',
so I guess that's one use case for having and
using both commands.  (And in that case, sure,
maybe bind `*-next*' - that definitely would
improve the use of `s'.)

That's possible because there are separate
histories, `Info-search-history' and
`regexp-search-ring'.

On the other hand, it might be good to have an
option that lets `Info-search' add its regexp
to `regexp-search-ring'.  Or vice versa: let
`Info-search' retrieve values from
`regexp-search-ring'.  Or both possibilities.

One way or another, there's some "overlap"
between isearching with `C-M-s' and the
nonincremental searching of `Info-search'.
And some room maybe for leveraging that - the
fact that there are two regexp histories and
two ways to search (incremental or not).

(BTW - seems like `Info-search' would be better
named `Info-regexp-search' or, following
`nonincremental-re-search-forward', something
like `Info-nonincremental-regexp-search'.)

  reply	other threads:[~2023-01-20 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 10:25 bug#60960: 30.0.50; Keybinding for Info-search-next in info-mode Marco Wahl
2023-01-20 17:26 ` Drew Adams [this message]
2023-01-22 18:32   ` Marco Wahl
2023-01-26  7:44     ` Eli Zaretskii

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=SJ0PR10MB5488B86EB3F8B5AE5E369199F3C59@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=60960@debbugs.gnu.org \
    --cc=marcowahlsoft@gmail.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).