From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Bach <phaebz@gmail.com>, 10348@debbugs.gnu.org
Subject: bug#10348: 24.0.92; Save and load window states
Date: Mon, 26 Dec 2011 19:25:15 +0100 [thread overview]
Message-ID: <4EF8BC0B.6020805@gmx.at> (raw)
In-Reply-To: <4EF8557A.3020001@gmx.at>
Looking into this I noticed the following: There's already a variable
`window-state-ignored-parameters'. But it's broken since
`window-state-get-1' doesn't copy the parameter (so it behaves just like
`current-window-configuration') and it doesn't affect the `clone-of'
parameter. So I'm afraid that we might need two variables say
`window-state-saved-parameters' and `window-state-ignored-parameters'.
The former would explicitly name the parameters that have to be
preserved accross window configuration changes. The latter would be
responsible for not writing out parameters to disk.
The semantics of `window-state-saved-parameters' across a
`save-window-excursion' would then be as follows:
(1) If a parameter is a member of `window-state-saved-parameters'
`current-window-configuration' makes a copy of its value in the
window_parameters slot of saved_window.
(2) For each window, `set-window-configuration' clears out any non-nil
value of a parameter in `window-state-saved-parameters'. Thereafter
it does a `set-window-parameter' for all entries it finds in the
window_parameters slot of that window's saved_window entry.
This approach is inconsistent if `window-state-saved-parameters' changes
within the body of the `save-window-excursion'.
martin
next prev parent reply other threads:[~2011-12-26 18:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 20:41 bug#10348: 24.0.92; Save and load window states Michael Bach
2011-12-22 17:04 ` martin rudalics
2011-12-22 17:14 ` Drew Adams
2011-12-22 21:57 ` Juri Linkov
2011-12-22 22:57 ` Juanma Barranquero
2011-12-22 23:34 ` Juri Linkov
2011-12-23 10:30 ` martin rudalics
2011-12-23 15:10 ` Drew Adams
2011-12-24 19:04 ` Juri Linkov
2011-12-23 10:30 ` martin rudalics
2011-12-23 1:03 ` Stefan Monnier
2011-12-23 10:31 ` martin rudalics
2011-12-23 11:30 ` Michael Bach
2011-12-23 21:14 ` Juri Linkov
2011-12-24 9:26 ` martin rudalics
2011-12-24 19:08 ` Juri Linkov
2011-12-25 13:57 ` martin rudalics
2011-12-24 0:07 ` Stefan Monnier
2011-12-24 9:27 ` martin rudalics
2011-12-25 11:00 ` Stefan Monnier
2011-12-25 13:58 ` martin rudalics
2011-12-25 21:36 ` Juri Linkov
2011-12-26 11:07 ` martin rudalics
2011-12-26 0:22 ` Stefan Monnier
2011-12-26 11:07 ` martin rudalics
2011-12-26 18:25 ` martin rudalics [this message]
2011-12-27 23:23 ` Stefan Monnier
2011-12-28 15:57 ` martin rudalics
2011-12-28 23:09 ` Stefan Monnier
2011-12-29 11:39 ` martin rudalics
2012-01-16 9:42 ` martin rudalics
2011-12-28 9:50 ` martin rudalics
2011-12-24 19:17 ` Juri Linkov
2012-01-16 9:43 ` martin rudalics
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=4EF8BC0B.6020805@gmx.at \
--to=rudalics@gmx.at \
--cc=10348@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=phaebz@gmail.com \
/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.