From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 53740@debbugs.gnu.org, chadpbrown@gmail.com
Subject: bug#53740: 29.0.50; Buffers->Frames menu lists F1
Date: Thu, 03 Feb 2022 10:33:31 +0200 [thread overview]
Message-ID: <834k5g5oys.fsf@gnu.org> (raw)
In-Reply-To: <87a6f891oz.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Cc: 53740@debbugs.gnu.org
> Date: Thu, 03 Feb 2022 09:30:20 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> chad brown <chadpbrown@gmail.com> writes:
>
> > When emacs is started in server mode, the Frames submenu of the Buffers
> > menu includes an entry F1, for the initial pseudo-frame. Selecting this
> > entry does nothing, but its presence is confusing.
>
> Should be fixed now on master, please test.
It doesn't seem to be fixed for me, neither on MS-Windows with a GUI
frame created by emacsclient, nor on GNU/Linux with TTY frames. In
both cases, after emacsclient creates a client frame, the
Buffers->Frames menu shows the F1 frame that cannot be switched to.
What do you see on your system that caused you think the bug is fixed?
What recipe did you try?
Your change uses frame-initial-frame, but that is usually nil, so I'm
not sure this is the correct implementation.
next prev parent reply other threads:[~2022-02-03 8:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 22:58 bug#53740: 29.0.50; Buffers->Frames menu lists F1 chad brown
2022-02-03 1:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 8:33 ` Eli Zaretskii [this message]
2022-02-03 9:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-03 10:30 ` Eli Zaretskii
2022-02-03 10:54 ` Robert Pluim
2022-02-03 11:06 ` Eli Zaretskii
2022-02-03 11:33 ` Robert Pluim
2022-02-03 11:52 ` Eli Zaretskii
2022-02-03 13:30 ` Robert Pluim
2022-02-03 16:49 ` Eli Zaretskii
2022-02-03 11:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=834k5g5oys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53740@debbugs.gnu.org \
--cc=chadpbrown@gmail.com \
--cc=luangruo@yahoo.com \
/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.