From: Eli Zaretskii <eliz@elta.co.il>
Cc: mbp@sourcefrog.net, emacs-devel@gnu.org
Subject: Re: suggested feature -- console-mode frame title sets Xterm title
Date: 15 Oct 2003 08:07:55 +0200 [thread overview]
Message-ID: <ubrsj3uf8.fsf@elta.co.il> (raw)
In-Reply-To: <E1A9cxD-00084j-2G@fencepost.gnu.org> (message from Richard Stallman on Wed, 15 Oct 2003 00:08:07 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Wed, 15 Oct 2003 00:08:07 -0400
>
> 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]).
next prev parent reply other threads:[~2003-10-15 6:07 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 [this message]
2003-10-15 6:22 ` Miles Bader
2003-10-15 6:36 ` Martin Pool
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=ubrsj3uf8.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=mbp@sourcefrog.net \
/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).