unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Arash Cue <eg5cue@gmail.com>, 17589@debbugs.gnu.org
Subject: bug#17589: 24.3.91; lisp/frameset.el
Date: Wed, 28 May 2014 09:05:54 -0400	[thread overview]
Message-ID: <jwvvbsqm50h.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAAeL0SQu9AMQXbr74dHF7uS40+qSFMoXwRRxu47dRgFEA+=qgg@mail.gmail.com> (Juanma Barranquero's message of "Wed, 28 May 2014 07:28:23 +0200")

> :in-session arg in frameset-save, unless you also want that
> frameset-save returns non-writable framesets and add a
> frameset-writable function,

Right, that would be the idea.

> which is very ugly.

One way to make it less ugly is to fold the "make it writable" thingy
directly into the print code.  We've already had some discussions about
that in the past.  For example, we could provide
a `print-non-readable-function' which the C printing routines would
call when bumping into a non-readable object and which could return
either a string to print instead.


        Stefan





  reply	other threads:[~2014-05-28 13:05 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 [this message]
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=jwvvbsqm50h.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17589@debbugs.gnu.org \
    --cc=eg5cue@gmail.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).