From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: luangruo@yahoo.com, 53740@debbugs.gnu.org, chadpbrown@gmail.com
Subject: bug#53740: 29.0.50; Buffers->Frames menu lists F1
Date: Thu, 03 Feb 2022 18:49:01 +0200 [thread overview]
Message-ID: <83bkzn520y.fsf@gnu.org> (raw)
In-Reply-To: <8735l09iwh.fsf@gmail.com> (message from Robert Pluim on Thu, 03 Feb 2022 14:30:54 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: luangruo@yahoo.com, 53740@debbugs.gnu.org, chadpbrown@gmail.com
> Date: Thu, 03 Feb 2022 14:30:54 +0100
>
> >>>>> On Thu, 03 Feb 2022 13:52:27 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: Robert Pluim <rpluim@gmail.com>
> >> Cc: luangruo@yahoo.com, 53740@debbugs.gnu.org, chadpbrown@gmail.com
> >> Date: Thu, 03 Feb 2022 12:33:57 +0100
> >>
> >> Would it be useful to have the TTY frames named something other than
> >> Fn?
>
> Eli> By default? (Because we already have "M-x set-frame-name".) What
> Eli> would you call them?
>
> "Fn <tty>" or similar?
Is that really so different? It will take more space on the mode
line, for starters.
next prev parent reply other threads:[~2022-02-03 16:49 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
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 [this message]
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=83bkzn520y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53740@debbugs.gnu.org \
--cc=chadpbrown@gmail.com \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.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.