unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, emacsq <laszlomail@protonmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Intelligent stacking of messages in the echo area
Date: Sat, 9 Apr 2022 20:53:00 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488ADE172026E870EFF68EDF3E89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86mtgu141p.fsf@mail.linkov.net>

> We still have unsolved bug#40774.  Maybe it could be fixed now.
> Or maybe better to create a new report.

40774 isn't a bug, AFAICT.  It's an enhancement
request.  And if ever there was a bug thread
that runs in circles and isn't clear, this is it.
Eli's posts there are clear, IMO, but not the
thread overall.

If there really is a need for some enhancement
that's related to the request, it should be
thought through again, IMO -- and not starting
from an assumption that (ab)using the echo area
is the right way to begin.

There are presumably many other way to "solve"
the (unclear) problem.  Among them are probably
various ways to _view_ the *Messages* log,
showing only what the OP wants to see, or
perhaps highlighting it.

Use the content of *Messages* - view/display
parts of it that might be particularly relevant
in different contexts.  Leave the echo area out
of it.

(And no, I'm not proposing any such solution.
My comment is only that the "problem" is not
clearly specified, and likewise the "stack
messages in the echo area" solution for it.)




      reply	other threads:[~2022-04-09 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09  4:46 Intelligent stacking of messages in the echo area emacsq
2022-04-09 18:53 ` Juri Linkov
2022-04-09 20:53   ` Drew Adams [this message]

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=SJ0PR10MB5488ADE172026E870EFF68EDF3E89@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=laszlomail@protonmail.com \
    /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).