From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48409@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#48409: Text runs away before user can copy it
Date: Mon, 31 May 2021 10:44:18 +0000 [thread overview]
Message-ID: <YLS+AprtLR1RUOnH@ACM> (raw)
In-Reply-To: <83mtsxxfo8.fsf@gnu.org>
Hello, Eli.
On Fri, May 14, 2021 at 22:45:43 +0300, Eli Zaretskii wrote:
> > From: Juri Linkov <juri@linkov.net>
> > Cc: eliz@gnu.org, jidanni@jidanni.org
> > Date: Fri, 14 May 2021 20:58:24 +0300
> > I vaguely remember a feature that clicking on the echo area
> > pops up the *Messages* buffer with the recent messages
> > at the end of the *Messages* buffer. So Jidanni could just click
> > on the shell output in the echo area, and copy the complete output
> > from the displayed *Messages* buffer.
> > But this feature doesn't work anymore. Searching the source code
> > indicates that such a feature existed before. In minibuffer.el:
> > (defvar minibuffer-inactive-mode-map
> > (let ((map (make-keymap)))
> > ...
> > (define-key map [mouse-1] 'view-echo-area-messages)
> > But now clicking mouse-1 reports an error.
> It reports an error because it doesn't invoke view-echo-area-messages.
> Alan, this minibuffer-inactive-mode-map thing doesn't seem to work
> with mouse clicks, please take a look.
This has now been fixed with
commit 6e2d3bce087d30a535b1f01715d7820576ffe390
Author: Alan Mackenzie <acm@muc.de>
Date: Mon May 31 10:33:10 2021 +0000
Correct mouse handling when window origin changes between down and up events
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2021-05-31 10:44 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
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 [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=YLS+AprtLR1RUOnH@ACM \
--to=acm@muc.de \
--cc=48409@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).