From: Alan Mackenzie <acm@muc.de>
To: Juri Linkov <juri@linkov.net>
Cc: "Richard Copley" <rcopley@gmail.com>,
"martin rudalics" <rudalics@gmx.at>,
"Óscar Fuentes" <ofv@wanadoo.es>,
"Emacs Development" <emacs-devel@gnu.org>
Subject: Re: goto-line-history should not be buffer local.
Date: Tue, 16 Feb 2021 20:57:53 +0000 [thread overview]
Message-ID: <YCwx0eSqEeBz2xcW@ACM> (raw)
In-Reply-To: <875z2s3s9b.fsf@mail.linkov.net>
Hello, Juri.
On Tue, Feb 16, 2021 at 19:13:36 +0200, Juri Linkov wrote:
> > -(defvar-local goto-line-history nil
> > +(defcustom goto-line-history-local nil
> > + "If this option is nil, `goto-line-history' is shared between all buffers.
> > +if it is non-nil, each buffer has its own value of this history list.
> > +
> > +Note that on changing from non-nil to nil, the former contents of
> > +`goto-line-history' for each buffer are discarded on use of
> > +`goto-line' in that buffer."
> > + :group 'editing
> > + :type 'boolean
> > + :safe #'booleanp
> > + :version "28.1")
> > Anybody have any objections to this?
> This is not an objection, just sharing a tip that to make
> Isearch history buffer-local like it's in web browsers,
> where each web page tab uses own local search history,
> is possible with a small code snippet:
> (make-variable-buffer-local 'search-ring)
> (make-variable-buffer-local 'regexp-search-ring)
> OTOH, with using defcustom it's easier to customize this, indeed.
The point about the approach I've taken is that once a variable has
undergone make-variable-buffer-local, it cannot be changed back to a
non-local variable, except by restarting Emacs (I'm not sure whether or
not this is a design bug). So I've avoided the use of that primitive.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-02-16 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 19:18 goto-line-history should not be buffer local Alan Mackenzie
2021-02-14 23:08 ` Óscar Fuentes
2021-02-14 23:31 ` Richard Copley
2021-02-15 8:17 ` martin rudalics
2021-02-15 21:12 ` Alan Mackenzie
2021-02-16 11:46 ` Lars Ingebrigtsen
2021-02-16 17:13 ` Juri Linkov
2021-02-16 20:57 ` Alan Mackenzie [this message]
2021-02-16 22:52 ` Matt Armstrong
2021-02-16 22:56 ` Lars Ingebrigtsen
2021-02-18 0:26 ` Rolf Ade
2021-02-18 10:43 ` Alan Mackenzie
2021-02-18 11:04 ` Kévin Le Gouguec
2021-02-18 11:38 ` Rolf Ade
2021-02-18 10:53 ` Philip Kaludercic
2021-02-18 11:02 ` Andreas Schwab
2021-02-16 22:56 ` Stefan Monnier
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=YCwx0eSqEeBz2xcW@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=ofv@wanadoo.es \
--cc=rcopley@gmail.com \
--cc=rudalics@gmx.at \
/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).