From: Jude DaShiell <jdashiel@panix.com>
To: torys.anderson@gmail.com
Cc: Emacs Help List <help-gnu-emacs@gnu.org>
Subject: Re: Getting rid of the GUI pop-ups
Date: Wed, 15 Feb 2017 18:11:36 -0500 (EST) [thread overview]
Message-ID: <alpine.NEB.2.20.1702151810190.20455@panix1.panix.com> (raw)
In-Reply-To: <87tw7vyw5v.fsf@gmail.com>
not good, screen readers in command line environments like espeak and
fenrir and speechdup at the least are not going to like this.
On Wed, 15
Feb 2017, torys.anderson@gmail.com wrote:
> Date: Wed, 15 Feb 2017 16:35:40
> From: torys.anderson@gmail.com
> To: Jude DaShiell <jdashiel@panix.com>
> Cc: Emacs Help List <help-gnu-emacs@gnu.org>
> Subject: Re: Getting rid of the GUI pop-ups
>
> This behaves precisely the same way: :30-1:00 wait time for KDE to put up a
> "password" prompt which requires I use a mouse.
> Jude DaShiell <jdashiel@panix.com> writes:
>
>> Have you tried running emacs -nw inside of a terminal yet and interfacing
>> with a password yet?
>>
>> On Wed, 15 Feb 2017, Tory S. Anderson wrote:
>>
>>> Date: Wed, 15 Feb 2017 14:09:40
>>> From: Tory S. Anderson <torys.anderson@gmail.com>
>>> To: Emacs Help List <help-gnu-emacs@gnu.org>
>>> Subject: Getting rid of the GUI pop-ups
>>>
>>> With Emacs 25.1.1, password prompts are no longer in the menu bar but via
>>> my (KDE/Plasma) window manager. Not only is this annoying, it is costly --
>>> it takes 30 seconds to a full minute for the popup to appear, meanwhile
>>> Emacs is frozen. I would love for this to just be the menu prompt, as it
>>> used to be. I've tried
>>>
>>> `(setq menu-prompting nil)` but it doesn't seem to have any effect. I see
>>> these prompts most often when opening .gpg files and when trying to
>>> perform a git push. I'm hoping someone will tell me there is a better way
>>> to disable these than just rebuilding emacs from source with X menus
>>> disabled (particularly as I have been pleased to get my emacs from the
>>> repo without needing to build from source).
>>>
>>> Good news would be much appreciated!
>>>
>>> - Tory
>>>
>>>
>
--
next prev parent reply other threads:[~2017-02-15 23:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 19:09 Getting rid of the GUI pop-ups Tory S. Anderson
2017-02-15 21:03 ` Jude DaShiell
2017-02-15 21:35 ` torys.anderson
2017-02-15 23:11 ` Jude DaShiell [this message]
2017-02-15 23:16 ` Jude DaShiell
2017-02-16 21:44 ` torys.anderson
2017-02-16 22:09 ` John Mastro
2017-02-17 8:37 ` tomas
2017-02-15 23:12 ` Jude DaShiell
2017-02-16 2:14 ` Glenn Morris
2017-02-16 8:28 ` tomas
2017-02-16 15:44 ` torys.anderson
2017-02-16 15:53 ` tomas
2017-02-16 14:49 ` 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=alpine.NEB.2.20.1702151810190.20455@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=help-gnu-emacs@gnu.org \
--cc=torys.anderson@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.
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).