From: tpeplt <tpeplt@gmail.com>
To: Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Problem with new frame not recognizing `default-frame-alist' width and height
Date: Tue, 27 Feb 2024 17:05:17 -0500 [thread overview]
Message-ID: <87a5nla7he.fsf@gmail.com> (raw)
In-Reply-To: <jwv34tdlkkv.fsf-monnier+emacs@gnu.org> (Stefan Monnier via Users list for the's message of "Tue, 27 Feb 2024 15:28:24 -0500")
Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
>> A more canonical URL is https://debbugs.gnu.org/67654
>
> Oh, and from within Emacs you can view it with
>
> M-x gnu-emacs-bug RET 67654 RET
>
> [ That's not the actual name of the command, but completion makes it
> work, and I find it easier to remember it like that. ]
>
Thank you for the canonical URL. I have the ‘debbugs’ package
installed, so it is possible in gnus to click on https link that you
provided to get a table listing of the bug(s) that looks like:
Id State Submitter Title
67654 68463,normal Roshan Shariff 29.1; Hiding menu bar makes new frames very small
The table is displayed in ‘Debbugs’ major mode and includes a menu of
actions. Pressing RET on 67654 in the table then displays the thread of
reports in a gnus article summary buffer, just as M-x gnu-emacs-bugs RET
67654 RET.
--
prev parent reply other threads:[~2024-02-27 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 3:11 Problem with new frame not recognizing `default-frame-alist' width and height tpeplt
2024-02-27 3:31 ` tpeplt
2024-02-27 3:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-02-27 16:13 ` tpeplt
2024-02-27 8:14 ` Joost Kremers
2024-02-27 10:14 ` Eli Zaretskii
2024-02-27 11:19 ` Joost Kremers
2024-02-27 16:53 ` tpeplt
2024-02-27 19:50 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-02-27 20:28 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-02-27 22:05 ` tpeplt [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=87a5nla7he.fsf@gmail.com \
--to=tpeplt@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).