From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: goto-line-history should not be buffer local.
Date: Sun, 14 Feb 2021 19:18:58 +0000 [thread overview]
Message-ID: <YCl3ooro+tdtjNdG@ACM> (raw)
Hello, Emacs.
Why is goto-line-history buffer local? This seems to me to be a step
backwards, for precisely the reason that making search history buffer
local would be a bad thing. This was a recent change, at the end of
January.
In my personal use, I sometimes type M-g M-g in the wrong buffer, which
disrupts my flow of thought in that buffer. That's unavoidable. But
now I have the additional inconvenience of having to type in that line
number in full a second time, having gone to the proper buffer. That's
not good.
Also I frequently want to go to the same line repeatedly in the same
file. I mean here file, not buffer. I kill the buffer and reload from
"disk" to ensure that caches are cleared, and suchlike, during testing.
Here, again, I've got to remember that line number and type it in again
in full. That's not good either.
Indeed, I'm not sure whether having a buffer local history is better
than having no history at all. Who wants to go to the same line
repeatedly in the same buffer? OK, others may do, but I don't see the
compelling need.
So, could we have this history variable made global again, please?
--
Alan Mackenzie (Nuremberg, Germany).
next reply other threads:[~2021-02-14 19:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 19:18 Alan Mackenzie [this message]
2021-02-14 23:08 ` goto-line-history should not be buffer local Ó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
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=YCl3ooro+tdtjNdG@ACM \
--to=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).