From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 38282@debbugs.gnu.org, Federico Tedin <federicotedin@gmail.com>
Subject: bug#38282: 26.3; goto-line should not share input history with other commands
Date: Thu, 21 Nov 2019 15:41:44 +0100 [thread overview]
Message-ID: <m28so9i95j.fsf@gmail.com> (raw)
In-Reply-To: <871ru1z6ax.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 21 Nov 2019 14:51:18 +0100")
>>>>> On Thu, 21 Nov 2019 14:51:18 +0100, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Federico Tedin <federicotedin@gmail.com> writes:
>> When using goto-line (M-g M-g), I usually tend to jump to lines which I
>> have jumped to in the past. Because goto-line shares input history with
>> other commands (like `read-from-minibuffer'), sometimes these numbers
>> get buried among strings that I have entered for other commands. I think
>> it would make sense to give goto-line a separate input history to make
>> finding past lines easier.
Lars> Yes, the Emacs behaviour here has annoyed me, too.
Lars> `goto-line' basically just calls `read-number' (which calls
Lars> `read-from-minibuffer' with the "default" nil history) -- I wonder
Lars> whether it would make sense to have a separate history for `read-number'
Lars> so that all numbers that are read share a history? Or is that too
Lars> drastic?
If debbugs-gnu-bugs et al uses read-number, Iʼm all in favour.
Robert
next prev parent reply other threads:[~2019-11-21 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 21:48 bug#38282: 26.3; goto-line should not share input history with other commands Federico Tedin
2019-11-21 13:51 ` Lars Ingebrigtsen
2019-11-21 14:41 ` Robert Pluim [this message]
2019-11-21 15:20 ` Michael Albinus
2019-11-21 17:51 ` Lars Ingebrigtsen
2019-11-21 18:43 ` Federico Tedin
2019-11-21 22:06 ` Federico Tedin
2019-11-22 7:35 ` Eli Zaretskii
2019-11-22 12:09 ` Lars Ingebrigtsen
2019-11-23 17:05 ` Federico Tedin
2019-11-27 11:48 ` Lars Ingebrigtsen
2019-12-06 22:14 ` Federico Tedin
2019-12-14 11:44 ` Eli Zaretskii
2019-12-17 21:19 ` Federico Tedin
2019-12-24 16:39 ` Lars Ingebrigtsen
2019-12-24 23:21 ` Federico Tedin
2019-11-22 7:57 ` Michael Albinus
2019-11-22 8:40 ` Robert Pluim
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=m28so9i95j.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=38282@debbugs.gnu.org \
--cc=federicotedin@gmail.com \
--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).