From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Rolf Ade <rolf@pointsman.de>, emacs-devel@gnu.org
Subject: Re: goto-line-history should not be buffer local.
Date: Thu, 18 Feb 2021 12:04:13 +0100 [thread overview]
Message-ID: <871rddtz6a.fsf@gmail.com> (raw)
In-Reply-To: <YC5EtpjSJM2vtAmJ@ACM> (Alan Mackenzie's message of "Thu, 18 Feb 2021 10:43:02 +0000")
Alan Mackenzie <acm@muc.de> writes:
> A third case, which is what got on my nerves last weekend, is when you
> are repeatedly killing a buffer and loading the same file again, so as
> to clear caches, and so on. You want to go to the same place at each
> new loading, so as to do testing.
Out of curiosity, in this specific case, wouldn't revert-buffer (now
conveniently bound to C-x x g) accomplish the same thing? (Clear
caches, while preserving the buffer-local history)
(Not suggesting that this invalidates your use-cases; just trying to
make sure I understand this one)
> I'm curious as to why somebody would want buffer local goto-line
> history. How often does one repeat the same goto-line in the same
> buffer, and how does a buffer local history help?
🤷 I guess someone could use that buffer-local history as a manually
curated version of the mark ring?
next prev parent reply other threads:[~2021-02-18 11:04 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
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 [this message]
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=871rddtz6a.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rolf@pointsman.de \
/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).