unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: RFC: defcustom display-popup-menus for display-popup-menus-p
Date: Wed, 21 Dec 2016 22:28:08 +0200	[thread overview]
Message-ID: <83r35110yv.fsf@gnu.org> (raw)
In-Reply-To: <87y3z9hxs1.fsf@lifelogs.com> (message from Ted Zlatanov on Wed,  21 Dec 2016 14:45:02 -0500)

> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Wed, 21 Dec 2016 14:45:02 -0500
> 
> Currently the function `display-popup-menus-p' doesn't have any
> user-customizable behavior as far as I can tell, and it's used by
> `read-multiple-choice' for instance.
> 
> This creates annoying dialogs that require a mouse to click.
> 
> I propose a new boolean defcustom `display-popup-menus' so users can
> disable graphical popups.

display-popup-menus-p is supposed to be a capability-reporting
function, like display-graphic-p.  It shouldn't be customizable.  What
should be customizable are the Lisp programs which ask questions via
popup menus.  The function you mention, read-multiple-choice, already
allows that via the existing variable use-dialog-box.

Btw, the dialog/menu should only pop up if the command itself was
invoked via a mouse.  Since you say you don't want to click the mouse,
I wonder how come you got that popup menu in the first place.



  reply	other threads:[~2016-12-21 20:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 19:45 RFC: defcustom display-popup-menus for display-popup-menus-p Ted Zlatanov
2016-12-21 20:28 ` Eli Zaretskii [this message]
2016-12-21 20:43   ` Ted Zlatanov
2016-12-21 20:49     ` Eli Zaretskii
2016-12-27 20:43       ` Ted Zlatanov
2017-01-31 19:20         ` Ted Zlatanov

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=83r35110yv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).