From: Eli Zaretskii <eliz@gnu.org>
To: jao <mail@jao.io>
Cc: 71683@debbugs.gnu.org
Subject: bug#71683: 30.0.50; Ellipsis buttons in compilation buffers can only be activated with the mouse
Date: Sat, 22 Jun 2024 13:42:02 +0300 [thread overview]
Message-ID: <86zfrdgsxx.fsf@gnu.org> (raw)
In-Reply-To: <875xu1jo5a.fsf@mail.jao.io> (message from jao on Sat, 22 Jun 2024 09:57:26 +0000)
[Please use Reply All, to keep the bug tracker on the CC list.]
> Date: Sat, 22 Jun 2024 09:57:26 +0000
> From: jao <mail@jao.io>
>
> On Sat, Jun 22 2024, Eli Zaretskii wrote:
>
> >
> > So what is the problems you see with this? If I go to the […] thing
> > (cursor is shown on the opening bracket) and press RET, Emacs asks me
> > where to find the file corresponding to this "error message". Is this
> > what you wanted? If not, what did you want to do?
>
> I want to see the ellided content, instead of jumping to the error. And
> I find no way of expanding it (i.e., pressing the [..] button) other
> than M-x push-button. What I am expecting is that if i press RET with
> the cursor there, the [..] is expanded and i can see the full message.
I've now installed a change whereby you should be able to use either
M-RET or M-mouse-2 to expand the truncated output.
next prev parent reply other threads:[~2024-06-22 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 18:29 bug#71683: 30.0.50; Ellipsis buttons in compilation buffers can only be activated with the mouse Jose A. Ortega Ruiz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 18:46 ` Eli Zaretskii
2024-06-20 20:41 ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 23:41 ` Jose A. Ortega Ruiz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 9:37 ` Eli Zaretskii
[not found] ` <875xu1jo5a.fsf@mail.jao.io>
2024-06-22 10:42 ` Eli Zaretskii [this message]
2024-06-26 1:52 ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 11:20 ` Eli Zaretskii
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=86zfrdgsxx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71683@debbugs.gnu.org \
--cc=mail@jao.io \
/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.