From: "Drew Adams" <drew.adams@oracle.com>
To: "'Steven Degutis'" <sbdegutis@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Any way to make minibuffer questions more obvious?
Date: Thu, 18 Apr 2013 15:00:34 -0700 [thread overview]
Message-ID: <2B014952EB7D4AA6B8B47F83BEF26C64@us.oracle.com> (raw)
In-Reply-To: <CACeWA3izu4GM9G+7PDOp_ho80GKP=T=-eJCjEKhbhmhG3H63Cw@mail.gmail.com>
> I was in dired, and I deleted a dir using D, then I hit "y"
> to confirm I want to delete it. Next I try to go copy another
> with C, but nothing happens. I look in the minibuffer and it
> says "Please answer y or n. Kill dired buffer of foo, too?
> (y or n)".
>
> I had no idea it was asking me this second question. I
> completely forgot that it would. And the minibuffer where it
> asks it is the bottom left of my screen, while the dired
> buffer is in the top-right, this being a 27" Apple display
> at highest possible resolution, so there's no way I would
> have noticed it.
>
> Is there a way to make this kind of question pop-up a new
> frame or some other more visual way of asking this?
I think we've all been bitten by that more than once. ;-)
Dunno whether someone else will have a brilliant suggestion. (I don't.)
There are ways to make Emacs flash, burp, and wave its arms wildly, and you
could always attach those to (your version of) `y-or-n-p'. But soon you might
find that annoying.
FWIW, `y-or-n-p' does not use the minibuffer. It simply reads a user-initiated
event, which is typically hitting a key (e.g. `y' or `n'). If it doesn't like
the event it reads then it asks you again. and again.
next prev parent reply other threads:[~2013-04-18 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 21:42 Any way to make minibuffer questions more obvious? Steven Degutis
2013-04-18 22:00 ` Drew Adams [this message]
2013-04-18 22:22 ` Steven Degutis
2013-04-18 23:24 ` Drew Adams
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=2B014952EB7D4AA6B8B47F83BEF26C64@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sbdegutis@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.