From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: bug-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: bug#12833: 24.2.50; Avoid questions asked in the echo area to be overridden by messages
Date: Mon, 10 Dec 2012 11:16:14 +0100 [thread overview]
Message-ID: <80vccaqkk1.fsf@somewhere.org> (raw)
In-Reply-To: mailman.14688.1354824897.855.bug-gnu-emacs@gnu.org
Hello Stefan,
Stefan Monnier wrote:
>>>> What does that change in case of interactive question? If I do 1 require
>>>> before asking a question to the user, the message about that require
>>>> should hardly be visible (if visible at all -- because actions happen so
>>>> quickly). The question should use the space of the information message,
>>>> point.
>>>
>>> I see, yes, that would make sense.
>>
>> Does that mean it will be fixed that way?
>
> No, it just means that I'd accept such a change. But I don't have time to
> come up with a patch for it in the foreseeable future.
>
>> BTW, I tested a workaround in the meanwhile: let-binding
>> `minibuffer-message-timeout' to 0.
>
> I think you'd need to let-bind it around the code that brings up
> the minibuffer.
IIUC, in the examplified case, you mean to let-bind it in defun
`org-read-date'?
But that is only one case out of hundreds: the problem appears as well in many
other functions of many other packages (than Org): `describe-variable', and
`describe-function', just to name a few.
In fact, IIUC, it happens every time that a defun embeds a `require' and a
user interaction via the minibuffer.
All those packages (`org.el', `help-fns.el', etc.) are out of my
responsability area. I can't path them all, can I?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-12-10 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 12:34 bug#12833: 24.2.50; Avoid questions asked in the echo area to be overridden by messages Sebastien Vauban
2012-12-04 20:14 ` Stefan Monnier
2012-12-04 22:06 ` Jan Djärv
[not found] ` <jwvobi9tw7n.fsf-monnier+emacs-mXXj517/zsQ@public.gmane.org>
2012-12-04 22:10 ` bug#12833: **: " Sebastien Vauban
[not found] ` <1354662544.WXHGMQZGWMUF@spammotel.com>
2012-12-05 3:41 ` Stefan Monnier
[not found] ` <mailman.14537.1354678921.855.bug-gnu-emacs@gnu.org>
2012-12-05 8:49 ` Sebastien Vauban
2012-12-06 20:14 ` Stefan Monnier
[not found] ` <mailman.14688.1354824897.855.bug-gnu-emacs@gnu.org>
2012-12-10 10:16 ` Sebastien Vauban [this message]
2012-12-10 17:01 ` Stefan Monnier
[not found] ` <mailman.14984.1355158954.855.bug-gnu-emacs@gnu.org>
2012-12-11 9:54 ` Sebastien Vauban
2012-12-11 13:50 ` Stefan Monnier
[not found] ` <mailman.15030.1355233953.855.bug-gnu-emacs@gnu.org>
2012-12-12 9:16 ` Sebastien Vauban
2012-12-12 20:06 ` Stefan Monnier
[not found] ` <mailman.15189.1355342844.855.bug-gnu-emacs@gnu.org>
2012-12-13 11:17 ` Sebastien Vauban
2020-08-20 18:14 ` Lars Ingebrigtsen
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=80vccaqkk1.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=bug-gnu-emacs-mXXj517/zsQ@public.gmane.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).