From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Freezing frameset-restore
Date: Fri, 07 Mar 2014 15:32:46 -0500 [thread overview]
Message-ID: <jwvr46deork.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAAeL0SRCYqo=mqytDzRyrW2f8fujbLP4GmRYbuLyZJLj4mqc=A@mail.gmail.com> (Juanma Barranquero's message of "Thu, 6 Mar 2014 01:03:30 +0100")
> I think it makes perfect sense to split REUSE-FRAMES into two:
> REUSE-FRAMES selects the policy to reuse frames when restoring:
> :all All existing frames can be reused. This is the default.
> :none No existing frame can be reused.
> :match Only frames with matching frame ids can be reused.
> LIST A list of frames to reuse; only these are reused (if possible).
> PRED A predicate function; it receives as argument a live frame,
> and must return t to allow reusing it, nil otherwise.
> CLEANUP allows to \"clean up\" the frame list after restoring a frameset:
> :delete Delete all frames that weren't restored. This is the default.
> :keep Keep all frames.
> FUNC A function called with two arguments:
> - FRAME, a live frame.
> - ACTION, which can be one of
> :rejected Frame existed, but was not a candidate for reuse.
> :ignored Frame existed, was a candidate, but wasn't reused.
> :reused Frame existed, was a candidate, and restored upon.
> :created Frame didn't exist, was created and restored upon.
> Return value is ignored.
Could we instead make frameset-restore return a list of (FRAME
. ACTION), so we can then use a plain dolist if we want to do some
extra cleanup.
Stefan
next prev parent reply other threads:[~2014-03-07 20:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 0:03 Freezing frameset-restore Juanma Barranquero
2014-03-06 17:27 ` martin rudalics
2014-03-06 17:33 ` Juanma Barranquero
2014-03-06 18:16 ` martin rudalics
2014-03-06 18:35 ` Juanma Barranquero
2014-03-06 18:41 ` Juanma Barranquero
2014-03-07 7:38 ` martin rudalics
2014-03-07 11:28 ` Juanma Barranquero
2014-03-07 15:16 ` martin rudalics
2014-03-07 20:32 ` Stefan Monnier [this message]
2014-03-07 21:34 ` Juanma Barranquero
2014-03-07 21:40 ` Juanma Barranquero
2014-03-08 0:34 ` Stefan Monnier
2014-03-08 1:42 ` Juanma Barranquero
2014-03-08 2:25 ` Juanma Barranquero
2014-03-08 4:31 ` Stefan Monnier
2014-03-08 6:00 ` Juanma Barranquero
2014-03-08 14:27 ` Stefan Monnier
2014-03-08 16:34 ` Juanma Barranquero
2014-03-08 23:45 ` Juanma Barranquero
2014-03-10 4:29 ` Stefan Monnier
2014-03-10 5:26 ` Juanma Barranquero
2014-03-10 13:04 ` Juanma Barranquero
2014-03-10 14:19 ` Stefan Monnier
2014-03-10 15:06 ` Juanma Barranquero
2014-03-10 18:33 ` Juanma Barranquero
2014-03-10 23:10 ` Stefan Monnier
2014-03-11 0:47 ` Juanma Barranquero
2014-03-10 20:32 ` Stefan Monnier
2014-03-10 21:07 ` Juanma Barranquero
2014-03-09 12:29 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr46deork.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.