unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Federico Tedin <federicotedin@gmail.com>
Cc: larsi@gnus.org, 38282@debbugs.gnu.org
Subject: bug#38282: 26.3; goto-line should not share input history with other commands
Date: Sat, 14 Dec 2019 13:44:50 +0200	[thread overview]
Message-ID: <837e2z6si5.fsf@gnu.org> (raw)
In-Reply-To: <87tv6d3xvs.fsf@gmail.com> (message from Federico Tedin on Fri, 06 Dec 2019 23:14:15 +0100)

> From: Federico Tedin <federicotedin@gmail.com>
> Date: Fri, 06 Dec 2019 23:14:15 +0100
> Cc: 38282@debbugs.gnu.org
> 
> > I think it makes sense for read-number to use its own history variable,
> > but it should not be buffer local.  Most inputs are not naturally buffer
> > local.
> 
> No problem - I've added an input history variable for `read-number', and
> a buffer-local one for `goto-line'. I'm attaching a patch with my
> changes.

Thanks, I think this variable should be mentioned in the ELisp manual
(in the "Minibuffer History" node) and in NEWS.





  reply	other threads:[~2019-12-14 11:44 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
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 [this message]
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=837e2z6si5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).