From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 35860@debbugs.gnu.org
Subject: bug#35860: Delayed window positioning after buffer display
Date: Thu, 23 May 2019 07:34:28 +0300 [thread overview]
Message-ID: <83ef4p7prf.fsf@gnu.org> (raw)
In-Reply-To: <87o93ucjsi.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 22 May 2019 23:32:13 +0300)
> From: Juri Linkov <juri@linkov.net>
> Date: Wed, 22 May 2019 23:32:13 +0300
>
> There are commands that set point while the buffer is not displayed,
> and after displaying the buffer point remains at an old position,
> not where it was moved while the buffer was undisplayed.
That's a feature, isn't it? See switch-to-buffer-preserve-window-point.
> One solution is to generalize the variable 'help-window-point-marker'
> currently described as:
>
> ;; `help-window-point-marker' is a marker you can move to a valid
> ;; position of the buffer shown in the help window in order to override
> ;; the standard positioning mechanism (`point-min') chosen by
> ;; `with-output-to-temp-buffer' and `with-temp-buffer-window'.
> ;; `with-help-window' has this point nowhere before exiting. Currently
> ;; used by `view-lossage' to assert that the last keystrokes are always
> ;; visible.
> (defvar help-window-point-marker (make-marker)
> "Marker to override default `window-point' in help windows.")
Why not bind switch-to-buffer-preserve-window-point to nil instead?
next prev parent reply other threads:[~2019-05-23 4:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 20:32 bug#35860: Delayed window positioning after buffer display Juri Linkov
2019-05-23 4:34 ` Eli Zaretskii [this message]
2019-05-23 20:56 ` Juri Linkov
2019-05-24 6:32 ` Eli Zaretskii
2019-05-24 18:34 ` Juri Linkov
2019-05-25 7:58 ` martin rudalics
2019-05-27 19:49 ` Juri Linkov
2019-06-11 20:53 ` Juri Linkov
2019-06-13 8:44 ` martin rudalics
2019-06-13 20:24 ` Juri Linkov
2019-06-14 19:14 ` Juri Linkov
2019-06-15 8:17 ` martin rudalics
2019-06-15 22:44 ` Juri Linkov
2019-06-16 8:16 ` martin rudalics
2019-06-16 19:32 ` Juri Linkov
2019-06-17 8:23 ` martin rudalics
2019-06-17 20:33 ` Juri Linkov
2019-06-18 8:19 ` martin rudalics
2019-06-18 21:02 ` Juri Linkov
2019-06-19 9:14 ` martin rudalics
2019-06-19 21:34 ` Juri Linkov
2019-06-20 7:41 ` martin rudalics
2019-06-15 8:17 ` 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=83ef4p7prf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35860@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).