unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 5039@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#5039: 23.1.50; Info-index and Info-search should share the same history
Date: Sat, 02 Nov 2019 06:13:08 +0100	[thread overview]
Message-ID: <875zk2j1y3.fsf@marxist.se> (raw)
In-Reply-To: <87pnj08lcx.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 13 Oct 2019 22:02:38 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Juri Linkov <juri@jurta.org> writes:
>
>>> Info-index and Info-search should share the same
>>> minbuffer previous-history-element etc. history.
>>>
>>> As it is often that if the first finds nothing, we want to try the same
>>> string with the second.
>>
>> I second that.  All related commands should share the same history,
>> e.g. `Info-index', `C-h f', `C-h v', etc.
>
> They all seem to share the same history (the global one) except
> Info-search, which takes a regexp and has its own history.
>
> I do think Dan's request makes sense (i.e., trying Info-index and then
> Info-search is probably common), but since one is a string and the other
> a regexp, do we want to get rid of the separate history for the latter?

My vote would be to keep the separate histories, since the type is
different.  It would be confusing to find regexps in the history when
searching for strings.

Perhaps we could, as a special case, make Info-index pull in the first
item from Info-search on the first invocation of M-p, but I don't know
if it's worth the effort.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-11-02  5:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 19:05 bug#5039: 23.1.50; Info-index and Info-search should share the same history jidanni
2009-11-25 21:27 ` Juri Linkov
2019-10-13 20:02   ` Lars Ingebrigtsen
2019-11-02  5:13     ` Stefan Kangas [this message]
2019-11-02 15:02       ` Lars Ingebrigtsen
2019-11-02 15:19       ` 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=875zk2j1y3.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=5039@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.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).