From: Martin Pool <mbp@sourcefrog.net>
Cc: Eli Zaretskii <eliz@elta.co.il>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: suggested feature -- console-mode frame title sets Xterm title
Date: Wed, 15 Oct 2003 16:36:00 +1000 [thread overview]
Message-ID: <20031015063555.GG18244@vexed.ozlabs.hp.com> (raw)
In-Reply-To: <buowub781gr.fsf@mcspd15.ucom.lsi.nec.co.jp>
On 15 Oct 2003, Miles Bader <miles@lsi.nec.co.jp> wrote:
> Eli Zaretskii <eliz@elta.co.il> writes:
> > > If you're talking about the frame's name, what you would specify to
> > > switch frames, then I don't see why this is desirable. Always using
> > > the F<n> name seems better.
> >
> > I thought about using the xterm's title as the frame's name. People
> > may wish to use the name displayed in the xterm's title because it's
> > more descriptive, and thuis more easily remembered, than F<n>. In
> > effect, the string in the title could act as the frame's name, making
> > the use of set-frame-name unnecessary. (Which means, btw, that, if
> > Miles's suggestion is implemented, we should decide what to do with
> > set-frame-name: should it affect the xterm title or the F<n> displayed
> > in the mode line [or both]).
>
> I really think it ought to work as close to the way X does as possible,
> with the F%d notation only used as (1) an abbreviated form displayed in
> the mode-line (since the `true name' is too long), and (2) possibly as a
> `shortcut name' allowed for switching-frame commands as I described
> earlier.
I agree.
> In X, the displayed frame `title' is either the frame's name (set by
> set-frame-name), or if that's nil, a string computed using
> frame-title-format. select-frame-by-name actually seems to use the
> frame's title, not it's name.
This is how it looks to the user. On the inside it is much more
messy, because f->name and f->title are not used in the way their
documentation suggests. select-frame-by-name uses what seems to be
the frame's title because that gets written into f->name.
There is also some stuff about "explicitly set titles" -- I can see
basically what this is about but I don't understand all the
interactions.
However, it is only software, and can be fixed, if we decide how we
want it to work.
Here is how I think it should work on the inside:
f->name holds the frame's name, which is initially F%d and can be
set by set-frame-name
f->title holds the title generated by frame-title-format, except
it holds the "explicit title" if one is set.
f->title is always used for the window title on X or (where possible
and desired) on ttys.
f->name is used for the '%F' format in mode-line-frame-identification.
If you want, you can even put '%F' in frame-title-format to include
the frame name.
I haven't tried this yet, so it might not work. But it sounds like it
will give the behaviour we want, and it's cleaner than the present
code.
We have a choice of either making select-frame-by-name look only at
f->name (as it does on tty frames at the moment), or having it also
look at titles as Miles suggested. If we choose the first, we could
add select-frame-by-title.
> I see no reason _not_ to use this same model for ttys, and doing so
> would be a big win for consistency. If, as I described earlier, F%d
> notation were still be displayed in mode-lines, and usable for
> select-frame-by-name, the current tty behavior would also largely be
> preserved.
>
> I also think that the F%d stuff should work on X -- then there would be
> basically no difference between X and ttys in this area.
Yes, and users on ttys who like the F%d name could even arrange for it
to be shown in their xterm title if they wanted.
--
Martin
next prev parent reply other threads:[~2003-10-15 6:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 16:49 suggested feature -- console-mode frame title sets Xterm title Eric Hanchrow
2002-06-15 21:47 ` Richard Stallman
2003-09-26 5:04 ` Martin Pool
2003-09-27 2:32 ` Richard Stallman
2003-09-29 5:17 ` Martin Pool
2003-10-01 21:21 ` Richard Stallman
2003-10-01 21:45 ` Martin Pool
2003-10-02 6:34 ` Martin Pool
2003-10-02 7:00 ` Miles Bader
2003-10-02 8:52 ` Martin Pool
2003-10-02 14:58 ` Miles Bader
2003-10-02 19:15 ` Richard Stallman
2003-10-03 5:58 ` Martin Pool
[not found] ` <E1A58vH-0002KC-Mq@fencepost.gnu.org>
2003-10-03 1:04 ` Martin Pool
[not found] ` <E1A5p16-0001Wq-3Y@fencepost.gnu.org>
2003-10-14 3:59 ` Martin Pool
2003-10-14 6:39 ` Eli Zaretskii
2003-10-14 7:15 ` Martin Pool
2003-10-14 7:29 ` Miles Bader
2003-10-14 7:44 ` Martin Pool
2003-10-14 7:56 ` Miles Bader
2003-10-14 8:01 ` Martin Pool
2003-10-15 6:01 ` Eli Zaretskii
2003-10-14 9:10 ` Eli Zaretskii
2003-10-14 9:40 ` Romain FRANCOISE
2003-10-14 9:07 ` Eli Zaretskii
2003-10-15 4:08 ` Richard Stallman
2003-10-15 6:07 ` Eli Zaretskii
2003-10-15 6:22 ` Miles Bader
2003-10-15 6:36 ` Martin Pool [this message]
2003-10-16 14:06 ` Richard Stallman
2003-10-16 14:06 ` Richard Stallman
2003-10-14 19:32 ` Richard Stallman
2003-10-15 2:47 ` Martin Pool
2003-10-15 20:00 ` Richard Stallman
2003-10-16 7:32 ` Eli Zaretskii
2003-10-16 8:25 ` Miles Bader
2003-10-16 8:35 ` Martin Pool
2003-10-16 9:07 ` Miles Bader
2003-10-16 17:04 ` Stefan Monnier
2003-10-16 23:07 ` Richard Stallman
2003-10-30 3:03 ` Martin Pool
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=20031015063555.GG18244@vexed.ozlabs.hp.com \
--to=mbp@sourcefrog.net \
--cc=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).