From: Eli Zaretskii <eliz@gnu.org>
To: Markus Triska <triska@metalevel.at>
Cc: 34038@debbugs.gnu.org, acm@muc.de
Subject: bug#34038: 26.1; set-window-start sometimes fails to set window start
Date: Fri, 29 Mar 2019 11:29:43 +0300 [thread overview]
Message-ID: <83d0majd6w.fsf@gnu.org> (raw)
In-Reply-To: <87sgv640c6.fsf@metalevel.at> (message from Markus Triska on Fri, 29 Mar 2019 08:16:25 +0100)
> From: Markus Triska <triska@metalevel.at>
> Cc: rudalics@gmx.at, acm@muc.de, 34038@debbugs.gnu.org
> Date: Fri, 29 Mar 2019 08:16:25 +0100
>
> The key issue seems to be that point must be set correctly: If point is
> at a position that is known to be displayable with a given window-start,
> then if point is again set to that position, set-window-start will also
> reliably set window-start to that start. Is this correct?
Yes. In fact, that's how set-window-start was intended to work to
begin with: for applications that put point at certain location, and
also want to control where the window display will start on next
redisplay. Scrolling commands behave that way, for example.
> Personally, I would appreciate some comment regarding such a guarantee,
> or the assumptions, in the documentation of set-window-start.
OK, I will add something to that effect, thanks for pointing this out.
next prev parent reply other threads:[~2019-03-29 8:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 19:57 bug#34038: 26.1; set-window-start sometimes fails to set window start Markus Triska
2019-01-11 7:03 ` Eli Zaretskii
2019-01-11 12:20 ` Markus Triska
2019-01-11 13:36 ` Eli Zaretskii
2019-01-11 14:31 ` Markus Triska
2019-01-11 15:10 ` martin rudalics
2019-01-11 17:45 ` Markus Triska
2019-01-11 19:07 ` Eli Zaretskii
2019-01-12 8:12 ` martin rudalics
2019-01-12 13:25 ` Markus Triska
2019-01-12 13:53 ` Eli Zaretskii
2019-01-12 14:12 ` martin rudalics
2019-01-12 19:08 ` Markus Triska
2019-01-12 20:28 ` Eli Zaretskii
2019-01-11 21:23 ` Alan Mackenzie
2019-01-12 8:13 ` martin rudalics
2019-01-12 18:22 ` Alan Mackenzie
2019-01-12 20:29 ` Eli Zaretskii
2019-01-12 20:42 ` Alan Mackenzie
2019-01-13 3:30 ` Eli Zaretskii
2019-01-13 7:32 ` Markus Triska
2019-01-13 8:40 ` martin rudalics
2019-01-13 11:32 ` Eli Zaretskii
2019-01-13 13:40 ` martin rudalics
2019-01-13 15:21 ` Eli Zaretskii
2019-03-24 10:35 ` Markus Triska
2019-03-24 17:28 ` Eli Zaretskii
2019-03-24 19:56 ` Markus Triska
2019-03-28 16:21 ` Eli Zaretskii
2019-03-29 7:16 ` Markus Triska
2019-03-29 8:29 ` Eli Zaretskii [this message]
2019-04-06 8:23 ` Eli Zaretskii
[not found] <<m2ftu05lqv.fsf@metalevel.at>
[not found] ` <<83sgxzhe04.fsf@gnu.org>
2019-01-11 16:37 ` Drew Adams
2019-01-11 16:49 ` Eli Zaretskii
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=83d0majd6w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34038@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=triska@metalevel.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).