unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Cc: tino.calancha@gmail.com
Subject: Standard check before creating large num of frames
Date: Thu, 15 Sep 2016 15:26:43 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1609151513030.25124@calancha-pc> (raw)


Dear all,

several functions might create new frames.  In particular when
`pop-up-frames' is non-nil, `display-buffer' creates a new frame.
Creating a lot of new frames might be expensive.

Some functions may ask for user confirmation before creating an
many frames.
For instance, see `ibuffer-do-view-1': this function ask for confirmation
before creating > 3 frames.
IMO, it's good if each function creating a large number of frames
do a similar check.
We might add a new option, for instance 'max-number-of-frames'
or 'frame-max-number':

(defcustom max-number-of-frames 3
   "Maximum number of frames to create before asking user confirmation."
     :version "25.2"
     :type 'integer
     :group 'convenience)

We might want to standarize the check as well:
(defun frame-create-many-frames-p (nframes &optional prompt)
   "Return non-nil if it's OK to create NFRAMES.
If NFRAMES + current number of frames is > `max-number-of-frames',
ask for user confirmation.
An optional arg is the prompt to ask the user."
   (let* ((tot (+ nframes (length (frame-list))))
          (str (or prompt (format "Really create %s frames? " nframes)))
          (res (or (<= tot max-number-of-frames)
                   (y-or-n-p str))))
     res))

Please, let me know your opinions/suggestions about this proposal.
In case we want to add these things: where should they live?

Regards,
Tino



             reply	other threads:[~2016-09-15  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15  6:26 Tino Calancha [this message]
2016-09-15 12:00 ` Standard check before creating large num of frames Stefan Monnier
2016-09-15 15:33   ` Tino Calancha
2016-09-15 14:58 ` Eli Zaretskii

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=alpine.DEB.2.20.1609151513030.25124@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).