From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Arash Cue <eg5cue@gmail.com>, 17589@debbugs.gnu.org
Subject: bug#17589: 24.3.91; lisp/frameset.el
Date: Fri, 30 May 2014 04:17:44 +0200 [thread overview]
Message-ID: <CAAeL0SQQ2EvegHar_pvhXnc2xvwvPo=jo=Y8fOMtc2w1RCG37A@mail.gmail.com> (raw)
In-Reply-To: <jwvvbsqm50h.fsf-monnier+emacsbugs@gnu.org>
On Wed, May 28, 2014 at 3:05 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> Right, that would be the idea.
I think the current interfaces (window-state-get|put and
frameset-save|restore, with an optional WRITABLE or IN-SESSION arg)
are way preferable. Seems messy to introduce frameset-writable (or
whatever) when the framesets are intended to be writable and the
in-memory-only case is just an exception.
> One way to make it less ugly is to fold the "make it writable" thingy
> directly into the print code.
The difference between a "writable frameset" and a non-writable one is
not a matter of how to print some values, in the sense that you can
decide how to write it just by looking at the value. Some you have to
save in specific ways to be able to restore them.
J
next prev parent reply other threads:[~2014-05-30 2:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 20:49 bug#17589: 24.3.91; lisp/frameset.el eg5cue
2014-05-26 17:18 ` Juanma Barranquero
2014-05-26 17:49 ` Arash Cue
2014-05-26 19:04 ` Juanma Barranquero
2014-05-26 20:32 ` Stefan Monnier
2014-05-26 20:42 ` Juanma Barranquero
2014-05-27 7:34 ` martin rudalics
2014-05-27 8:32 ` Juanma Barranquero
2014-05-27 9:13 ` martin rudalics
2014-05-27 9:40 ` Juanma Barranquero
2014-05-27 10:08 ` martin rudalics
2014-05-27 10:53 ` Juanma Barranquero
2014-05-27 13:09 ` martin rudalics
2014-05-27 13:11 ` Juanma Barranquero
2014-05-27 13:30 ` Stefan Monnier
2014-05-27 16:45 ` Arash Cue
2014-05-27 17:14 ` martin rudalics
2014-05-27 22:34 ` Juanma Barranquero
2014-05-28 0:16 ` Arash Cue
2014-05-28 4:50 ` Juanma Barranquero
2014-05-28 5:26 ` Juanma Barranquero
2014-05-28 11:35 ` Arash Cue
2014-05-30 2:10 ` Juanma Barranquero
2014-05-28 0:22 ` Stefan Monnier
2014-05-28 4:55 ` Juanma Barranquero
2014-05-28 5:28 ` Juanma Barranquero
2014-05-28 13:05 ` Stefan Monnier
2014-05-30 2:17 ` Juanma Barranquero [this message]
2020-09-09 12:06 ` Lars Ingebrigtsen
2021-10-10 22:46 ` Stefan Kangas
2021-10-11 7:55 ` Lars Ingebrigtsen
2021-10-11 11:41 ` Stefan Kangas
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='CAAeL0SQQ2EvegHar_pvhXnc2xvwvPo=jo=Y8fOMtc2w1RCG37A@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=17589@debbugs.gnu.org \
--cc=eg5cue@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).