From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: luangruo@yahoo.com, 52809@debbugs.gnu.org
Subject: bug#52809: 28.0.90; X11 modeline context menu grows offscreen unreadable on smaller screen of two screen display
Date: Mon, 27 Dec 2021 16:45:00 +0200 [thread overview]
Message-ID: <83y246m7ir.fsf@gnu.org> (raw)
In-Reply-To: <d3452af8-3ab6-ad3-c569-39275ae98d@SDF.ORG> (message from Van Ly on Mon, 27 Dec 2021 10:25:22 +0000 (UTC))
> Date: Mon, 27 Dec 2021 10:25:22 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> Cc: 52809@debbugs.gnu.org
>
> On Mon, 27 Dec 2021, Po Lu wrote:
>
> > In the future, please use report-emacs-bug to report this kind of bug.
> > It avoids having to ask these questions.
>
> I don't have emacs configured for email and worry the mechanism might
> misfire.
There's no need to be afraid of that. report-emacs-bug first prepares
a buffer with all the data, and then waits for you to invoke a command
to send that as email (after adding the specifics of the problem). So
you can just copy the information it prepares to your MUA and discard
the buffer afterwards.
next prev parent reply other threads:[~2021-12-27 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 17:39 bug#52809: 28.0.90; X11 modeline context menu grows offscreen unreadable on smaller screen of two screen display Van Ly
2021-12-27 6:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-27 10:25 ` Van Ly
2021-12-27 14:45 ` Eli Zaretskii [this message]
2021-12-28 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-28 2:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-28 10:53 ` Van Ly
2021-12-28 10:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-28 13:09 ` Eli Zaretskii
2021-12-28 14:13 ` Van Ly
2021-12-28 14:17 ` Eli Zaretskii
2021-12-28 16:00 ` Van Ly
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=83y246m7ir.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52809@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=van.ly@sdf.org \
/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.