From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>
Cc: 48409@debbugs.gnu.org, juri@linkov.net
Subject: bug#48409: Text runs away before user can copy it
Date: Sat, 22 May 2021 16:36:40 +0200 [thread overview]
Message-ID: <713df055-e60b-16e7-42df-050892dc40b2@gmx.at> (raw)
In-Reply-To: <YKjuGtThrAFPwhmG@ACM>
>> But do we really want to show echo area messages even when there is no
>> echo in the first place?
>
> You mean, is view-echo-area-messages really a sensible command to bind to
> mouse-1? I wasn't actually aware of this facility until Juri (or was it
> Drew?) pointed it out in the bug report. It's not something I use myself
> (on a Linux tty with gpm-mouse-mode disabled).
I just wouldn't want to have the echo area messages pop up whenever I
accidentally click into an empty minibuffer window. So far this was no
issue because the mouse code prevented it ...
martin
next prev parent reply other threads:[~2021-05-22 14:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 6:32 bug#48409: Text runs away before user can copy it 積丹尼 Dan Jacobson
2021-05-14 7:07 ` Eli Zaretskii
2021-05-14 17:58 ` Juri Linkov
2021-05-14 18:46 ` Eli Zaretskii
2021-05-15 12:29 ` 積丹尼 Dan Jacobson
2021-05-15 12:34 ` Eli Zaretskii
2021-05-14 19:45 ` Eli Zaretskii
2021-05-14 19:51 ` bug#48409: [External] : " Drew Adams
2021-05-14 20:13 ` Eli Zaretskii
2021-05-14 20:53 ` Alan Mackenzie
2021-05-15 5:56 ` Eli Zaretskii
2021-05-15 11:15 ` Alan Mackenzie
2021-05-17 20:53 ` Juri Linkov
2021-05-18 13:13 ` Eli Zaretskii
2021-05-18 18:42 ` Alan Mackenzie
2021-05-18 19:05 ` Eli Zaretskii
2021-05-18 20:23 ` Alan Mackenzie
2021-05-19 12:12 ` Eli Zaretskii
2021-05-19 15:49 ` Alan Mackenzie
2021-05-19 17:40 ` martin rudalics
2021-05-20 16:54 ` martin rudalics
2021-05-21 20:55 ` Alan Mackenzie
2021-05-22 8:05 ` martin rudalics
2021-05-22 11:42 ` Alan Mackenzie
2021-05-22 14:36 ` martin rudalics [this message]
2021-05-22 15:12 ` Eli Zaretskii
2021-05-22 16:36 ` martin rudalics
2021-05-30 15:44 ` Alan Mackenzie
2021-05-31 7:55 ` martin rudalics
2021-05-31 10:44 ` Alan Mackenzie
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=713df055-e60b-16e7-42df-050892dc40b2@gmx.at \
--to=rudalics@gmx.at \
--cc=48409@debbugs.gnu.org \
--cc=acm@muc.de \
--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).