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: Mon, 26 May 2014 22:42:48 +0200 [thread overview]
Message-ID: <CAAeL0SSMYmcK+J9pE-q1N+C1Wzq2hk6FsZMEqwe29C=s6sMHdw@mail.gmail.com> (raw)
In-Reply-To: <jwvtx8cth9h.fsf-monnier+emacsbugs@gnu.org>
On Mon, May 26, 2014 at 10:32 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> Saving buffer names is indeed a problem. I think we should try and
> remember the actual buffer whenever possible (i.e. until we want to
> print the object) and when printing, we should try and print
> a description of the buffer, e.g. its file-name if it's visiting a file
Framesets treat window states (from window-state-get) as opaque
objects. I'm not sure what kind of changes would be required (in the
window state's API, I mean, not framesets) to implement what you
suggest.
Martin?
next prev parent reply other threads:[~2014-05-26 20:42 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 [this message]
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
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='CAAeL0SSMYmcK+J9pE-q1N+C1Wzq2hk6FsZMEqwe29C=s6sMHdw@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).