all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 6980@debbugs.gnu.org
Subject: bug#6980: Could goto-char please have its own history list?
Date: Thu, 18 Aug 2011 14:52:20 +0300	[thread overview]
Message-ID: <87sjoz543b.fsf@mail.jurta.org> (raw)
In-Reply-To: <89731AF8DD9241E7807DCEED9672DC4B@us.oracle.com> (Drew Adams's message of "Wed, 10 Aug 2011 14:41:51 -0700")

>> > 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.
>
> I don't have much of an opinion about the suggestion.
> There are always pros & cons to making a history more or less specific.
>
> But I'll point out that just because non-numeric histories are inappropriate for
> numeric input does not mean that the same numeric history should be used for all
> numeric inputs.

Yes, not all number-reading commands should share the numeric history.

For instance, version-control commands that read a revision number
can also accept non-numeric values like "submit:".  So every case
should be carefully considered on its own.





  reply	other threads:[~2011-08-18 11:52 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 [this message]
2011-08-18 12:27       ` Lennart Borgman
2021-02-17  8:51   ` Juri Linkov
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjoz543b.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=6980@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.