From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: Juanma Barranquero <lekktu@gmail.com>, 14964@debbugs.gnu.org
Subject: bug#14964: 24.3.50; doc of `compare-window-configurations'
Date: Mon, 29 Jul 2013 09:55:33 +0200 [thread overview]
Message-ID: <51F61FF5.30500@gmx.at> (raw)
In-Reply-To: <d08003f1-2488-4ac6-9f3d-e3e69174b460@default>
> E.g. (current-frame-configuration t) would return a writable & readable
> frame configuration.
With configurations you store and restore window positions and sizes in
situ. That is, you overwrite (in C) the members of the window structure
and rely on the fact that a configuration is an immutable memory object
to obtain correct bahavior. A function like `set-window-configuration'
does not check whether the object it restores is correct in some sense
or has been manipulated after it has been stored. It relies on your
hardware to do that. `window-state-put' OTOH is pretty failsafe in this
regard because it restores windows via the Lisp split and resize
operations.
> But the point is to have a standard structure that code can use and
> manipulate.
That would be clearly fatal as explained above. Changing anything in a
frame configuration is strictly forbidden.
martin
next prev parent reply other threads:[~2013-07-29 7:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 3:14 bug#14964: 24.3.50; doc of `compare-window-configurations' Drew Adams
2013-07-27 8:18 ` martin rudalics
2013-07-27 19:39 ` Drew Adams
2013-07-28 8:40 ` martin rudalics
2013-07-28 14:49 ` Drew Adams
2013-07-28 16:57 ` Juanma Barranquero
2013-07-28 18:56 ` Drew Adams
2013-07-29 2:14 ` Juanma Barranquero
2013-07-29 23:56 ` Drew Adams
2013-07-30 1:05 ` Juanma Barranquero
2013-07-30 9:13 ` martin rudalics
2013-07-29 7:55 ` martin rudalics [this message]
2013-07-29 23:53 ` Drew Adams
2013-07-30 0:18 ` Juanma Barranquero
2013-07-30 9:13 ` martin rudalics
2013-07-30 14:17 ` Stefan Monnier
2013-07-28 19:53 ` Josh
2013-07-28 20:33 ` Drew Adams
2013-07-29 7:54 ` martin rudalics
2022-04-21 13:42 ` Lars Ingebrigtsen
2022-05-20 2:23 ` Lars Ingebrigtsen
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=51F61FF5.30500@gmx.at \
--to=rudalics@gmx.at \
--cc=14964@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=lekktu@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 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).