all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [External] : Re: Is there a way to avoid clobbering minibuffer by messages?
Date: Thu, 30 Mar 2023 22:37:42 +0300	[thread overview]
Message-ID: <874jq2xc6x.fsf@osv.gnss.ru> (raw)
In-Reply-To: <834jq23xc3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 30 Mar 2023 21:31:24 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Thu, 30 Mar 2023 18:16:22 +0000
>> From: Gregory Heytings <gregory@heytings.org>
>> cc: help-gnu-emacs@gnu.org
>> 
>> > And I thought Drew wanted echo-area messages to pop in a separate 
>> > buffer.  The mode line is not a good place for showing messages, IMNSHO.
>> 
>> Hmmm... why not?
>
> Not enough screen estate, and cannot be enlarged to show more than one
> screen line.  You cannot base a general-purpose feature such as
> echo-area messages on the assumption that the message will never need
> more than one screen line.

There is no such assumption though, unless there is strict requirement
to show entire message. To me it looks fine to get only (part of) the
first line of the message, provided I can then check it in whole
elsewhere (if I decide to).

That said, I just checked my *Messages* buffer, and don't see anything
multi-line there, so multi-line echo area message is rather unusual to
encounter anyway?

>
>> It's not perhaps the solution that would suit everyone, but I'd bet
>> some users will prefer that to the way they are currently displayed.
>> A third option would indeed be a kind of pop-up buffer.  And there
>> are probably other options.
>
> Popup buffer and popup frame (perhaps a child frame?) are IMO the only
> viable alternatives that are worth having in Emacs.

Modeline looks more appealing to me, really hate popups.

Thanks,
-- Sergey



  reply	other threads:[~2023-03-30 19:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  7:57 Is there a way to avoid clobbering minibuffer by messages? Platon Pronko
2023-03-30  8:53 ` Eli Zaretskii
2023-03-30  9:40   ` Platon Pronko
2023-03-30 10:32     ` Eli Zaretskii
2023-03-30 15:05       ` Gregory Heytings
2023-03-30 16:28         ` [External] : " Drew Adams
2023-03-30 16:35           ` Eli Zaretskii
2023-03-30 16:49             ` Drew Adams
2023-03-30 17:27               ` Eli Zaretskii
2023-03-30 17:32             ` Gregory Heytings
2023-03-30 17:51               ` Eli Zaretskii
2023-03-30 18:14                 ` John Yates
2023-03-30 18:28                   ` Eli Zaretskii
2023-03-30 20:08                     ` John Yates
2023-03-31  6:32                       ` Yuri Khan
2023-03-30 18:16                 ` Gregory Heytings
2023-03-30 18:31                   ` Eli Zaretskii
2023-03-30 19:37                     ` Sergey Organov [this message]
2023-03-30 19:45                     ` Gregory Heytings
2023-03-30 20:02                       ` Gregory Heytings
2023-03-30 20:06                         ` Gregory Heytings
2023-03-30 19:26             ` Jean Louis
2023-03-31 10:40               ` Eric S Fraga
2023-03-30 19:22           ` Jean Louis
2023-03-31  6:24         ` Platon Pronko
2023-03-31  6:58           ` Gregory Heytings
2023-03-31  7:01             ` Gregory Heytings
2023-03-31  7:10               ` Platon Pronko
2023-03-31  7:17                 ` Gregory Heytings
2023-03-31  7:45                   ` Gregory Heytings
2023-03-31 11:04                     ` John Covici
2023-03-31 11:09                       ` Gregory Heytings
2023-03-31 12:46                         ` John Covici
2023-03-30  9:52 ` Gregory Heytings

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=874jq2xc6x.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 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.