unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Freezing frameset-restore
Date: Thu, 06 Mar 2014 19:16:46 +0100	[thread overview]
Message-ID: <5318BB8E.1010901@gmx.at> (raw)
In-Reply-To: <CAAeL0SRjppojZM+0T3wBHqcdaOsvXjtR_Ug=tiJqG8mRUXKguw@mail.gmail.com>

 >> Why the term "restored" here and not "reused"?
 >
 > "Restored frames" describes (or tries to) all frames that are the
 > result of restoration, that is, reused frames and new ones (created
 > specifically to be restored upon).
 >
 > Please suggest a better wording, my brain has an overdose of the words
 > "frame", "window", "restore" and "reuse" and cannot think straight.

Still IMO in

     :delete  Delete all frames that weren't restored.  This is the default.

a "frame that was not restored" refers to a frame stored in a past
session or configuration.  But IIUC you mean here a frame that existed
in the current session or configuration just before you started to
restore frames and you were not able to use profitably.  At least use
"restored upon" instead.

 >> IIUC "cleanup" means to take care of frames that were not "reused".
 >
 > No, the meaning of CLEANUP is to take care of all frames. It just that
 > most of the time, reused and created frames will be left alone. But...
 >
 >> understand that we should take care of "rejected" or "ignored" frames.
 >> But why care about "reused" and "created" ones?
 >
 > ...what if you want to iconify all restored frames too, or just count
 > them and do something about it?

Then CLEANUP is too narrow.  Maybe something like POST-RESTORE (which
clearly isn't a good term either) to emphasize that it does _not only_
deal with frames that were rejected or ignored.

martin



  reply	other threads:[~2014-03-06 18:16 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 [this message]
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
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

  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=5318BB8E.1010901@gmx.at \
    --to=rudalics@gmx.at \
    --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 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).