From: Drew Adams <drew.adams@oracle.com>
To: Josh <josh@foxtail.org>, Juanma Barranquero <lekktu@gmail.com>
Cc: 14964@debbugs.gnu.org
Subject: bug#14964: 24.3.50; doc of `compare-window-configurations'
Date: Sun, 28 Jul 2013 13:33:38 -0700 (PDT) [thread overview]
Message-ID: <a98a087c-5e1c-4a60-adc2-d436ca64055b@default> (raw)
In-Reply-To: <CANdFEAHLsu_tZhWXc9hqTOiNhaM0KdEmLKJNYtXMHi9D3WLB0g@mail.gmail.com>
> https://github.com/tlh/workgroups.el
Yes, it is good to point to that, as another example of readable window
configurations.
You mentioned frame configurations too, but working groups are not,
according to what I read in the doc and see in the code, frame
configurations. Rather, a workgroup is a set of window configurations
for a single frame. From the doc:
Q: What's the difference between a "window configuration", a "wconfig"
and a "workgroup"?
A: A "window configuration" is Emacs' opaque internal representation of
most of the state of one frame. A "wconfig" is Workgroups' independent,
translucent window configuration object. And a "workgroup" is a named
set of multiple wconfigs (one base config, and then a working config
for each frame).
So yes, this could inform what we do wrt Emacs window configurations.
It is also an example of the kinds of things that a library or a user
might want to do with persistent window configurations. And it is another
argument for having a standard, transparent, readable window-configuration
structure (whatever form the implementation might take).
next prev parent reply other threads:[~2013-07-28 20:33 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
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 [this message]
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=a98a087c-5e1c-4a60-adc2-d436ca64055b@default \
--to=drew.adams@oracle.com \
--cc=14964@debbugs.gnu.org \
--cc=josh@foxtail.org \
--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).