From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>, martin rudalics <rudalics@gmx.at>
Cc: adam@alphapapa.net, 64911@debbugs.gnu.org
Subject: bug#64911: 30.0.50; switch-to-buffer-preserve-window-point not respected by switch-to-(next|prev)-buffer
Date: Fri, 28 Jul 2023 10:21:12 +0300 [thread overview]
Message-ID: <83sf98jyc7.fsf@gnu.org> (raw)
In-Reply-To: <ea158bb2324397e0a34236f975d083b0@webmail.orcon.net.nz> (message from Phil Sainty on Fri, 28 Jul 2023 17:24:36 +1200)
> Cc: Adam Porter <adam@alphapapa.net>
> Date: Fri, 28 Jul 2023 17:24:36 +1200
> From: Phil Sainty <psainty@orcon.net.nz>
>
> The `switch-to-buffer-preserve-window-point' variable determines
> whether the (BUFFER WINDOW-START POS) data returned by
> `window-prev-buffers' will be used by `switch-to-buffer' to set
> the window's start and point positions.
>
> I think this variable should additionally be respected by both:
>
> - `switch-to-prev-buffer'
> - `switch-to-next-buffer'
>
> (If not others? These are the cases I'm presently aware of.)
Please provide a significant rationale for this change in behavior.
This option has proved problematic in quite a few cases since it was
introduced: see its uses in the Emacs tree as the evidence of the
subtle issues it introduces. So I'm not excited with making it affect
even more use cases. We need a sound rationale for such a change (and
no, "consistency" is not a sound rationale in my book), and we need to
try to audit all the calls to these functions in the tree to
understand and anticipate the impacts.
> In practice this is a problem because the position stored in the
> `window-prev-buffers' data is a marker (or at least that is the case
> in the scenario I am dealing with), and the buffer in question is
> periodically erased and regenerated. Erasing the buffer causes all
> its markers to be moved to position 1, so the end result is that the
> user loses their place. (The buffer contents are rebuilt, but the
> new content is typically similar if not identical to the old content,
> and so maintaining the original position is desirable).
This sounds like quite a unique use case to justify a global behavior
change of 2 commands. Can't you achieve what you need by other means?
Stashing the value of point or window-point somewhere and then
restoring it doesn't sound too complicated to me.
Adding martin, in case he has comments and suggestions.
next prev parent reply other threads:[~2023-07-28 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 5:24 bug#64911: 30.0.50; switch-to-buffer-preserve-window-point not respected by switch-to-(next|prev)-buffer Phil Sainty
[not found] ` <handler.64911.B.169052190417878.ack@debbugs.gnu.org>
2023-07-28 7:11 ` Phil Sainty
2023-07-28 11:04 ` Eli Zaretskii
2023-07-28 7:21 ` Eli Zaretskii [this message]
2023-07-29 8:08 ` martin rudalics
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=83sf98jyc7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64911@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=psainty@orcon.net.nz \
--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).