From: Eli Zaretskii <eliz@gnu.org>
To: Markus Triska <triska@metalevel.at>
Cc: 33532@debbugs.gnu.org
Subject: bug#33532: 26.1; set-window-configuration does not restore display start
Date: Wed, 28 Nov 2018 20:29:59 +0200 [thread overview]
Message-ID: <83pnupdpi0.fsf@gnu.org> (raw)
In-Reply-To: <87efb56q49.fsf@metalevel.at> (message from Markus Triska on Wed, 28 Nov 2018 18:58:30 +0100)
> From: Markus Triska <triska@metalevel.at>
> Cc: 33532@debbugs.gnu.org
> Date: Wed, 28 Nov 2018 18:58:30 +0100
>
> In my opinion, one way to do it is to have current-window-configuration
> store the window-start internally as an integer (instead of a marker),
> denoting the position of the display start.
>
> Then, set-window-configuration could set the window-start to that
> position.
How is this useful if the text has changed? You are just starting
display from some random position, don't you?
> Would that work?
Not in general, no.
> At least that is how I currently work around the issue.
I don't think this could be a general solution. But I'll let others
chime in and comment on this.
next prev parent reply other threads:[~2018-11-28 18:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 22:11 bug#33532: 26.1; set-window-configuration does not restore display start Markus Triska
2018-11-28 6:41 ` Eli Zaretskii
2018-11-28 17:13 ` Markus Triska
2018-11-28 17:41 ` Eli Zaretskii
2018-11-28 17:58 ` Markus Triska
2018-11-28 18:29 ` Eli Zaretskii [this message]
2018-11-29 8:31 ` martin rudalics
2018-11-29 18:09 ` Markus Triska
2018-11-29 19:11 ` martin rudalics
2018-11-30 16:58 ` Markus Triska
2018-11-30 17:47 ` martin rudalics
2018-12-01 22:52 ` Juri Linkov
2018-12-02 8:34 ` martin rudalics
2018-12-03 0:52 ` Juri Linkov
2018-12-03 7:45 ` martin rudalics
2018-12-03 22:59 ` Juri Linkov
2018-12-04 6:41 ` Eli Zaretskii
2018-12-04 21:44 ` Juri Linkov
2018-12-04 8:33 ` martin rudalics
2018-12-04 21:47 ` Juri Linkov
2018-12-05 9:16 ` martin rudalics
2018-12-06 0:09 ` Juri Linkov
2018-12-06 9:09 ` martin rudalics
2018-12-06 23:38 ` Juri Linkov
2018-12-25 21:49 ` Juri Linkov
2018-11-30 19:20 ` 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=83pnupdpi0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33532@debbugs.gnu.org \
--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).