From: martin rudalics <rudalics@gmx.at>
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: Fri, 30 Nov 2018 18:47:30 +0100 [thread overview]
Message-ID: <5C0177B2.4030803@gmx.at> (raw)
In-Reply-To: <877eguqz7k.fsf@metalevel.at>
> Perfect! This is what I need also for current-window-configuration!
> Also, could this be made the default? Or is there some advantage in
> using markers instead of the actual positions that can be restored?
First of all we need a "reasonable" use case. The only purpose of a
form like
(let ((str (with-current-buffer buf (buffer-string))))
(with-current-buffer buf
(erase-buffer)
(insert str)))
is to annihilate all marker positions in buf and I have yet to
understand why that could be useful. I'm sure you have something more
reasonable in mind. Once we have such a use case we can decide how to
best support it.
AFAICT Emacs' window configurations use window start and point markers
ever since. And while they interfere with reverting buffers (see
Bug#33458 for a discussion) turning them into pure positions would
break far too many things as to make that the default.
We could store - in configurations and states - both, markers and
their corresponding pure positions. Then if, when restoring a
configuration or state, a marker's position has dropped to 1 while the
corresponding saved pure position is > 1, use the the pure position
instead. This should automatically fix your case and not violate any
others. Juri what do you think?
martin
next prev parent reply other threads:[~2018-11-30 17:47 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
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 [this message]
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=5C0177B2.4030803@gmx.at \
--to=rudalics@gmx.at \
--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).