unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6980@debbugs.gnu.org
Subject: bug#6980: Could goto-char please have its own history list?
Date: Wed, 17 Feb 2021 10:51:08 +0200	[thread overview]
Message-ID: <875z2rf56r.fsf@linkov.net> (raw)
In-Reply-To: <878vr1rqpc.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 10 Aug 2011 22:50:39 +0300")

>> I can't see no reason its history should be mixed by something else.
>> (More than devel historic reasons ;-)
>
> It makes sense to share the same history that contains only numeric
> values between all commands that use `read-number', like
> e.g. `goto-line' and `goto-char' (with some changes), because
> non-numeric values (added to the history from other commands)
> are useless for such number-reading commands.

Matt reminded about this request in
https://lists.gnu.org/archive/html/emacs-devel/2021-02/msg01270.html

Now `read-number' has own history in `read-number-history' added a year ago
in bug#38282.  The same commit 7c5d6a2afc6 also added `goto-line-history'
for `goto-line'.

So this request could be closed unless there is still a need to add
`goto-char-history' for `goto-char' too.  I'm not sure if
`read-number-history' is sufficient already, or own history should be added
to every number-reading command like `move-to-column', etc.





  parent reply	other threads:[~2021-02-17  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 22:24 bug#6980: Could goto-char please have its own history list? Lennart Borgman
2011-08-10 19:50 ` Juri Linkov
2011-08-10 21:41   ` Drew Adams
2011-08-18 11:52     ` Juri Linkov
2011-08-18 12:27       ` Lennart Borgman
2021-02-17  8:51   ` Juri Linkov [this message]
2021-07-18 20:22     ` Lars Ingebrigtsen

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=875z2rf56r.fsf@linkov.net \
    --to=juri@jurta.org \
    --cc=6980@debbugs.gnu.org \
    --cc=lennart.borgman@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).