From: Markus Triska <triska@metalevel.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 34038@debbugs.gnu.org
Subject: bug#34038: 26.1; set-window-start sometimes fails to set window start
Date: Sat, 12 Jan 2019 14:25:57 +0100 [thread overview]
Message-ID: <87fttydn2y.fsf@metalevel.at> (raw)
In-Reply-To: <5C39A17B.8030204@gmx.at> (martin rudalics's message of "Sat, 12 Jan 2019 09:12:43 +0100")
martin rudalics <rudalics@gmx.at> writes:
> All we need to know for why this happens would be the exact sequence
> of (window) point and window start settting operations performed by
> that application.
The actual application performs actions that are quite involved, so I
try to break it down to simpler cases that need fewer operations.
For example, please try the following snippet:
(progn
(goto-char (point-max))
(insert "\n")
(dotimes (x (window-height))
(insert (format "%s\n" x)))
(let ((b (buffer-string))
(p (point)))
(redisplay)
(set-window-start nil p)
(let ((wp (window-point)))
(read-key "Step 1. Please press a key to continue.")
(dotimes (x (round (/ (window-height) 2)))
(insert (format "more lines ... %s\n" x)))
(read-key "Step 2. Please press a key to continue.")
(erase-buffer)
(insert b)
(set-window-point nil wp)
(set-window-start nil p))))
In this snippet, I try to restore the exact same configuration that you
see when "Step 1 ..." is displayed, i.e., window-start is set so that
point is on the very first line, which is blank. When you press a key at
this point, then a few more lines of text are inserted. Then, please
press another key when "Step 2 ..." is displayed.
What I observe after these forms is that point is unexpectedly placed
vertically centered in the window instead of at the topmost line.
Please note that I am now using set-window-point, and also
set-window-start with third argument (implicitly) nil. I get the exact
same result when I use t for the third argument of set-window-start.
Can you reproduce this? Is there a way to reliably restore this?
Thank you and all the best!
Markus
next prev parent reply other threads:[~2019-01-12 13:25 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fttydn2y.fsf@metalevel.at \
--to=triska@metalevel.at \
--cc=34038@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.