GNU bug report logs - #17589
24.3.91; lisp/frameset.el

Previous Next

Package: emacs;

Reported by: eg5cue <at> gmail.com

Date: Sun, 25 May 2014 19:47:02 UTC

Severity: normal

Tags: patch

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log


Message #86 received at 17589 <at> debbugs.gnu.org (full text, mbox):

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: martin rudalics <rudalics <at> gmx.at>, Arash Cue <eg5cue <at> gmail.com>,
 17589 <at> debbugs.gnu.org
Subject: Re: bug#17589: 24.3.91; lisp/frameset.el
Date: Fri, 30 May 2014 04:17:44 +0200
On Wed, May 28, 2014 at 3:05 PM, Stefan Monnier
<monnier <at> 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




This bug report was last modified 3 years and 225 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.