From: Markus Triska <triska@metalevel.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33532@debbugs.gnu.org
Subject: bug#33532: 26.1; set-window-configuration does not restore display start
Date: Wed, 28 Nov 2018 18:13:57 +0100 [thread overview]
Message-ID: <877egxyvje.fsf@metalevel.at> (raw)
In-Reply-To: <87efb62mt2.fsf@metalevel.at>
Eli Zaretskii <eliz@gnu.org> writes:
> How important is the use case of replacing buffer text with identical
> text? Because replacing with a different text will make preserving
> window-start position based on its numerical value not really a
> sensible thing, would it? It could even be impossible, e.g. if the
> same position happens to be in the middle of a sequence of composed
> characters.
Please consider a use case that is described in the Emacs manual:
In order to store a window configuration on disk and
read it back in another Emacs session ...
In such use cases, I want to restore the exact same text in all buffers,
and then restore the window configuration, including display starts.
In fact, the snippet illustrates an even simpler situation: It stores
the configuration in a variable, and the session keeps running. I would
like to obtain the configuration, then close all buffers, and later
restore their contents (for example, from files), and then use
set-window-configuration to restore the original window configuration,
including all window-starts.
Could set-window-configuration be generalized to reliably restore the
window-starts also in such cases? If not, please consider adjusting the
documentation to make clear what this actually guarantees. In
particular, when are window-starts reliably restored, and when not?
Thank you and all the best,
Markus
next prev parent reply other threads:[~2018-11-28 17:13 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 [this message]
2018-11-28 17:41 ` Eli Zaretskii
2018-11-28 17:58 ` Markus Triska
2018-11-28 18:29 ` Eli Zaretskii
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=877egxyvje.fsf@metalevel.at \
--to=triska@metalevel.at \
--cc=33532@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).