From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: juri@linkov.net, monnier@iro.umontreal.ca,
Gregory Heytings <ghe@sdf.org>,
acm@muc.de, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Where to show message output while inputting
Date: Tue, 13 Oct 2020 20:39:13 +0200 [thread overview]
Message-ID: <87sgai7yy6.fsf@gmail.com> (raw)
In-Reply-To: <5f7af512-7951-4e10-a8a1-4f5d07ee6cda@default> (Drew Adams's message of "Tue, 13 Oct 2020 10:31:39 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> 4. If we do choose to overwrite (hide) something
> in order to show output in a temporary way, then
> IMO it's better to overwrite/hide some buffer
> text, or the mode-line, than it is to do that
> to minibuffer input.
>
> The last thing we should hide or interfere with
> is the immediate user interaction (responding to
> a prompt by providing text input).
Emacs is no stranger to popping up windows when the user needs to be
alerted of something (e.g. disabled-command-function). Maybe, when the
echo area is unavailable, `message' could…
- pop up the *Messages* buffer, highlighting the latest message (or
creating a window that's only tall enough for this message),
- arrange for *Messages* to be buried when the user exits the
minibuffer, and for a reminder about C-h e to be messaged?
next prev parent reply other threads:[~2020-10-13 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 17:31 Where to show message output while inputting [was: New multi-command facility displays in the wrong echo area] Drew Adams
2020-10-13 18:39 ` Kévin Le Gouguec [this message]
2020-10-13 19:42 ` Gregory Heytings via Emacs development discussions.
2020-10-13 20:38 ` Drew Adams
2020-10-13 20:59 ` Gregory Heytings via Emacs development discussions.
[not found] ` <2bedd6ef-c49a-4e0e-b0e4-4e3c6b8b79ce@default>
2020-10-13 21:55 ` Gregory Heytings via Emacs development discussions.
2020-10-14 14:39 ` Eli Zaretskii
2020-10-14 14:58 ` Gregory Heytings via Emacs development discussions.
2020-10-14 17:27 ` Stefan Monnier
2020-10-14 21:22 ` Gregory Heytings via Emacs development discussions.
2020-10-15 1:52 ` Stefan Monnier
[not found] ` <87eelo6iio.fsf@blind.guru>
2020-10-24 17:31 ` 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
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=87sgai7yy6.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=acm@muc.de \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ghe@sdf.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
/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).