From: Markus Triska <triska@metalevel.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34038@debbugs.gnu.org
Subject: bug#34038: 26.1; set-window-start sometimes fails to set window start
Date: Fri, 11 Jan 2019 15:31:55 +0100 [thread overview]
Message-ID: <8736pz8dus.fsf@metalevel.at> (raw)
In-Reply-To: <83d0p3gvua.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Jan 2019 15:36:13 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> IOW, if there's a contradiction between the requested window-start and
> showing point, the latter always wins in Emacs.
OK! However, in the snippet I posted, there appears to be no such
contradiction, because the window-start can be set to the intended
position while point is also displayed. This is illustrated before you
press a key when you run the snippet, and after you press a key, I would
like to reliably restore the exact same display situation as before.
>
> How can you expect Emacs to do something like that? It cannot
> possibly do something that will leave point not displayed, can it?
I agree. However, that is not what I was requesting. What I need for my
use case is to reliably restore a configuration that I know is possible
to display on the grounds that it has already been displayed before. Is
there any way to do this, or could this please be provided?
Thank you and all the best,
Markus
next prev parent reply other threads:[~2019-01-11 14:31 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 [this message]
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
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=8736pz8dus.fsf@metalevel.at \
--to=triska@metalevel.at \
--cc=34038@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).