unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: master fbc9c59: Make goto-line-history buffer local only when so customized
Date: Sat, 27 Feb 2021 14:27:39 +0000	[thread overview]
Message-ID: <87lfb937s4.fsf@tcd.ie> (raw)
In-Reply-To: <YDj5QkgXuQaG11CZ@ACM> (Alan Mackenzie's message of "Fri, 26 Feb 2021 13:36:02 +0000")

Alan Mackenzie <acm@muc.de> writes:

> Yes, I had misunderstood, sorry.  I was under the mistaken impression
> that the previous change to the input history was in Emacs 27.  So, yes,
> you're correct, the two entries in NEWS do contradict eachother, and
> need merging into a single entry.
>
> I don't have time to do this today, I'll try and do it over the weekend.

Thanks.

>> This part of (info "(elisp) Minibuffer History") also needs updating:
>
>>  -- Variable: goto-line-history
>>      A history list for arguments to ‘goto-line’.  This variable is
>>      buffer local.
>
> Hmm.  OK.  But what's this variable doing in the elisp manual, as
> opposed to the emacs manual?  It's purely a user convenience.

I think it's there because (info "(elisp) Minibuffer History") already
lists several built-in history variables for standard user commands.

And (info "(emacs) Moving Point") already explains that goto-line has
its own history variable, and links to the Elisp manual, so I don't see
any problem, or how a history variable constitutes a user convenience.

But I also have no strong opinions on whether or how this history
variable should be documented, so feel free to change it as you or
others see fit.

-- 
Basil



  reply	other threads:[~2021-02-27 14:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210217212130.32410.14813@vcs0.savannah.gnu.org>
     [not found] ` <20210217212132.0B17F20DFB@vcs0.savannah.gnu.org>
2021-02-26 12:19   ` master fbc9c59: Make goto-line-history buffer local only when so customized Basil L. Contovounesios
2021-02-26 13:01     ` Alan Mackenzie
2021-02-26 13:15       ` Basil L. Contovounesios
2021-02-26 13:36         ` Alan Mackenzie
2021-02-27 14:27           ` Basil L. Contovounesios [this message]
2021-02-28 21:33             ` Alan Mackenzie
2021-02-28 21:53               ` Basil L. Contovounesios

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=87lfb937s4.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.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).