From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 35860@debbugs.gnu.org
Subject: bug#35860: Delayed window positioning after buffer display
Date: Thu, 13 Jun 2019 23:24:52 +0300 [thread overview]
Message-ID: <878su5i67f.fsf@mail.linkov.net> (raw)
In-Reply-To: <df37e41d-b5e8-2f19-2761-f8df90107aa0@gmx.at> (martin rudalics's message of "Thu, 13 Jun 2019 10:44:28 +0200")
> OK. But
>
> -;; (4) A marker (`help-window-point-marker') to move point in the help
> +;; (4) A marker (`window-point') to move point in the help
> ;; window to an arbitrary buffer position.
>
> sounds irritating IMHO. If it's used for help windows only, then why
> rename it? Otherwise, we should at least leave the '-marker' postfix
> and provide some additional identification so maybe use something like
> 'temp-buffer-window-point-marker'
It's generalized now to be used not only for help windows.
The '-marker' postfix is not needed because it can be either
marker or integer, i.e. any value that set-window-point accepts
for its POSITION argument.
next prev parent reply other threads:[~2019-06-13 20:24 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878su5i67f.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=35860@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.