unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings via "Emacs development discussions." <emacs-devel@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	acm@muc.de, juri@linkov.net, monnier@iro.umontreal.ca,
	emacs-devel@gnu.org
Subject: RE: Where to show message output while inputting [was: New multi-command facility displays in the wrong echo area]
Date: Tue, 13 Oct 2020 20:59:17 +0000	[thread overview]
Message-ID: <alpine.NEB.2.22.394.2010132245410453.21623@sdf.lonestar.org> (raw)
In-Reply-To: <95909e9d-07d8-41de-96a5-fe13cbec3131@default>


>>> The same problem will exist if you move output (`message' echoes) to 
>>> the mode-line: you won't be able to see the mode-line info and the 
>>> message at the same time.
>>
>> That's obviously a problem that will exist in any possible solution to 
>> that problem: the message will hide something.
>
> Not if the area used for echoes (output) is separate from the area used 
> for the minibuffer (prompt and input).
>

I meant: it will hide something on screen.  For example with a 
conventional pop-up it would hide a part of a buffer.

>
> But we need not overwrite - or displace at all, if we show the output in 
> its own area - at least when there would otherwise be a conflict with 
> the minibuffer/echo area.  I mentioned "popping up" such an output area 
> as needed.
>

Yes, that's the idea of temporariy adding a "zeroth" / "minusoneth" line 
to the miniwindow in which the message would be shown.  But it will still 
hide something, namely another line in that frame.

>
> Shifting existing stuff around could be distracting or annoying for some 
> users.
>

It's what eldoc already does for a similar situation, and I haven't seen 
complaints about this.  IMO it's elegant to solve that problem in that 
way.

BTW, if you don't shift the contents of the mode-line, you shift the 
contents of the buffer(s) above the mode-line.  Which could also be 
distracting or annoying, because such a shift could imply a temporary 
recentering of these buffers in their windows, when point is on their last 
line.



  reply	other threads:[~2020-10-13 20:59 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. [this message]
     [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=alpine.NEB.2.22.394.2010132245410453.21623@sdf.lonestar.org \
    --to=emacs-devel@gnu.org \
    --cc=acm@muc.de \
    --cc=drew.adams@oracle.com \
    --cc=eliz@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).