From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacsuser@freemail.hu, emacs-devel@gnu.org, juri@linkov.net
Subject: Re: Intelligent stacking of messages in the echo area
Date: Tue, 24 Dec 2019 17:24:29 +0800 [thread overview]
Message-ID: <87sgladqk2.fsf@localhost> (raw)
In-Reply-To: <83imm7xiu9.fsf@gnu.org>
> I'd rather think a better way would be to have a variable which allows
> to filter messages by regular expressions: any message that matches a
> regexp in a list will not be stacked.
It is a good idea. However, generating a universal regexp for, say, eldoc
may be challenging.
>> Also, it would be great to avoid stacking the echo-keystrokes, but I
>> have no clue how to detect them.
>
> See above.
I cannot find what you refer to.
Best,
Ihor
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ihor Radchenko <yantar92@gmail.com>
>> Date: Mon, 23 Dec 2019 11:50:48 +0800
>> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>>
>> A slightly improved version of the code, which prevents stacking
>> potentially "spammy" messages (like from eldoc or
>> org-display-outline-path). The messages are detected by looking at
>> messages-log-max variable, which is typically set to nil by such
>> functions.
>
> I'd rather think a better way would be to have a variable which allows
> to filter messages by regular expressions: any message that matches a
> regexp in a list will not be stacked.
>
>> Also, it would be great to avoid stacking the echo-keystrokes, but I
>> have no clue how to detect them.
>
> See above.
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg
next prev parent reply other threads:[~2019-12-24 9:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 5:35 Intelligent stacking of messages in the echo area ndame
2019-08-31 9:46 ` Marcin Borkowski
2019-12-21 22:07 ` Juri Linkov
2019-12-22 3:30 ` Eli Zaretskii
2019-12-23 2:59 ` Richard Stallman
2019-12-23 22:46 ` Juri Linkov
2019-12-23 3:50 ` Ihor Radchenko
2019-12-23 13:38 ` Eli Zaretskii
2019-12-24 9:24 ` Ihor Radchenko [this message]
2019-12-24 15:36 ` Eli Zaretskii
2019-12-25 4:21 ` Ihor Radchenko
2019-12-23 22:47 ` Juri Linkov
2019-12-24 9:40 ` Ihor Radchenko
2019-12-24 15:43 ` Eli Zaretskii
2019-12-24 17:32 ` Ihor Radchenko
2019-12-25 0:15 ` Juri Linkov
2019-12-25 5:35 ` Ihor Radchenko
2020-01-29 22:54 ` Juri Linkov
2020-01-24 10:14 ` Eric S Fraga
2020-01-28 22:34 ` Juri Linkov
2020-01-29 22:41 ` Juri Linkov
2020-01-29 23:53 ` Stefan Monnier
2020-01-30 22:35 ` Juri Linkov
2020-01-30 23:07 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2022-04-09 4:46 emacsq
2022-04-09 18:53 ` Juri Linkov
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=87sgladqk2.fsf@localhost \
--to=yantar92@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacsuser@freemail.hu \
--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 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).