emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: master fbc9c59: Make goto-line-history buffer local only when so cus


From: Alan Mackenzie
Subject: Re: master fbc9c59: Make goto-line-history buffer local only when so customized
Date: Fri, 26 Feb 2021 13:01:46 +0000

Hello, Basil.

On Fri, Feb 26, 2021 at 12:19:14 +0000, Basil L. Contovounesios wrote:
> acm@muc.de (Alan Mackenzie) writes:

> > branch: master
> > commit fbc9c59b9eb02d49f426341ee32334784d224ce4
> > Author: Alan Mackenzie <acm@muc.de>
> > Commit: Alan Mackenzie <acm@muc.de>

> >     Make goto-line-history buffer local only when so customized

> >     * lisp/simple.el (goto-line-history-local): New customizable option.
> >     (goto-line-history): Define this simply with defvar, not defvar-local.
> >     (goto-line-read-args): Handle goto-line-history-local, and changes to 
> > it.

> >     * doc/emacs/basic.texi (Moving Point): Add a paragraph about
> >     goto-line-history-local.

> >     * etc/NEWS: Add an item under "Editing Changes in Emacs 28.1".

> [...]

> > diff --git a/etc/NEWS b/etc/NEWS
> > index b96bcd9..7665d47 100644
> > --- a/etc/NEWS
> > +++ b/etc/NEWS
> > @@ -345,6 +345,11 @@ trying to be non-destructive.
> >  This command opens a new buffer called "*Memory Report*" and gives a
> >  summary of where Emacs is using memory currently.

> > ++++
> > +** The history list for the 'goto-line' command is now a single list
> > +for all buffers by default.  You can configure a separate list for
> > +each buffer by customizing the user option 'goto-line-history-local'.

> I think this contradicts a preceding entry:

> ** Input history for 'goto-line' is now local to every buffer.
> Each buffer will keep a separate history of line numbers used with
> 'goto-line'.  This should help making faster the process of finding
> line numbers that were previously jumped to.

Well, I think "contradict" is not quite the right word.  Whether the list
is buffer local or not is now customisable, which it wasn't before.  The
default is somewhat arbitrary, as it always is in these things, with some
people proclaiming a particular setting "obviously" should be the
default, others saying the opposite is "obvious".  That the list, before
that previous patch, wasn't buffer local points to the current default.

Or, have I misunderstood what you're saying?

> Thanks,

> -- 
> Basil

-- 
Alan Mackenzie (Nuremberg, Germany).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]