all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Gregory Heytings <ghe@sdf.org>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, drew.adams@oracle.com, juri@linkov.net
Subject: Re: Where to show message output while inputting [was: New multi-command facility displays in the wrong echo area]
Date: Wed, 14 Oct 2020 13:27:53 -0400	[thread overview]
Message-ID: <jwvk0vs3ent.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2010141640510453.21021@sdf.lonestar.org> (Gregory Heytings's message of "Wed, 14 Oct 2020 14:58:23 +0000")

>> Eldoc's purpose is different from the purpose of displaying echo-area
>> messages.  For example, nothing significantly bad can happen if you miss
>> the Eldoc's hints, but the same is not true for some important
>> echo-area messages.
> AFAICS you can't miss them with the proposed solution: they are displayed on
>  the left of the mode-line, with a different background and foreground.

In my setup, the minibuffer is in its own frame, with no mode-line in
sight.  So indeed I don't get the eldoc hints in `M-:` because they're
placed in a non-displayed mode-line.  E.g.:

    % src/emacs -Q --eval '(setq default-frame-alist (quote ((minibuffer . nil))))'
    M-: (format
    ...wait a little...

...and see that the mode-line doesn't display anything about `format`


        Stefan




  reply	other threads:[~2020-10-14 17:27 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 ` Where to show message output while inputting Kévin Le Gouguec
2020-10-13 19:42 ` Where to show message output while inputting [was: New multi-command facility displays in the wrong echo area] 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk0vs3ent.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 \
    /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.