From: Eli Zaretskii <eliz@gnu.org>
To: rrandresf@gmail.com (Andrés Ramírez)
Cc: emacs-devel@gnu.org
Subject: Re: frame names on tty are different than the ones on X-frames
Date: Mon, 26 Feb 2018 22:28:48 +0200 [thread overview]
Message-ID: <83fu5n1on3.fsf@gnu.org> (raw)
In-Reply-To: <87r2p78qy0.fsf@gmail.com> (rrandresf@gmail.com)
> From: rrandresf@gmail.com (Andrés Ramírez)
> Date: Mon, 26 Feb 2018 13:57:11 -0600
>
> Frame names on tty's are:
> --8<---------------cut here---------------start------------->8---
> F1
> F2
> ...
> --8<---------------cut here---------------end--------------->8---
>
> Frame names on X-frames are the buffer name
No. GUI frames don't really have names, they have titles. Only TTY
frames have real names, those Fn strings. A name of a frame cannot
change, otherwise it's not useful for specifying the frame.
> Why on tty frames the frame names could not be the buffer-name?
What would that be useful for?
In any case, you can supply a name for a frame using set-frame-name,
if you don't like the Fn notation.
> When using select-frame-by-name You could watch the name.
It's an illusion created by that function. That function is
mainly/only useful for TTY frames, because you have no other
convenient way of selecting a specific frame quickly: you only see one
frame, the current one, and have no idea what buffer is displayed on
others. That's why that function was written; but in order to make it
work with any kind of frames, it was extended to GUI frames, although
it has no real utility in that case.
next prev parent reply other threads:[~2018-02-26 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 19:57 frame names on tty are different than the ones on X-frames Andrés Ramírez
2018-02-26 20:28 ` Eli Zaretskii [this message]
2018-02-26 20:55 ` andrés ramírez
2018-02-26 21:06 ` Eli Zaretskii
2018-02-27 1:40 ` andrés ramírez
2018-02-27 13:13 ` Christian Lynbech
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=83fu5n1on3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rrandresf@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.