all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Martin Pool <mbp@sourcefrog.net>
Cc: emacs-devel@gnu.org
Subject: Re: suggested feature -- console-mode frame title sets Xterm title
Date: Tue, 14 Oct 2003 17:15:39 +1000	[thread overview]
Message-ID: <20031014071535.GM15872@vexed.ozlabs.hp.com> (raw)
In-Reply-To: <u4qyc2ui2.fsf@elta.co.il>

On 14 Oct 2003, Eli Zaretskii <eliz@elta.co.il> wrote:
> > Date: Tue, 14 Oct 2003 13:59:33 +1000
> > From: Martin Pool <mbp@sourcefrog.net>
> > 
> > I'd guess the number of people using multiple frames on a text
> > terminal is fairly small, though non-zero.
> 
> I do.

Thanks for responding!

> Please note that some Emacs features, such as Speedbar, create their
> own dedicated frames, so if you use those features, you'll be using
> multiple frames on text-mode displays whether you want that or not.
> 
> > I would also guess that
> > more than half the people using emacs in termcap mode are doing so
> > from some kind of terminal emulator under a window system (xterm,
> > putty, etc) and so could benefit from seeing the title.
> 
> Sorry, I don't see how the latter follows from the former.  Could you
> please explain?

With this feature added, people gain control over a part of their
environment (the xterm titlebar) that previously showed a fixed and
possibly unhelpful string.  The patch puts more of the environment
under the user's control (through mode-line-format), and I think that
control is useful in itself.

One way it might be helpful is in distinguishing emacs xterms from
each other or from other xterms.  I was motivated to do this by having
several emacs sessions open on different machines over ssh.

If you do happen to have several tty frames open, labelling them in
the title bar might help keep track of which one is which.

Some people like to have information in the title bar that won't fit
in their modeline.

Also, vim does it :-)

> > If I had to decide, I would probably just remove the 'F%d' behaviour.
> > (Specifically, remove that indicator from the toolbar, and remove it
> > as the default name for tty frames.)  This is a bit disturbing to
> > people who were accustomed to those features, but it does not really
> > remove any functionality, as they can still name frames by hand and
> > switch between them.
> 
> I think it'd be annoying to force the user to set frame names
> manually.  That is why I kept the old F1 name and generalized it to
> Fn back when I made multiple frames work on ttys.
> 
> How about if we have an option that would cause Emacs to either use
> the F<num> names (default) or the new names you implemented.  If it
> uses F<num>, that name will be displayed on the mode line, as today;
> otherwise, the name will be displayed in the xterm's title and be
> removed from the mode line.

OK.

Should this be a separate variable, or just controlled by
tty-frame-use-title?  Should it be on by default?

> (I also think that the code that sets the xterm's title should test
> whether the required capability is supported, in case we run on
> something that is not an xterm at all.)

The logic is that it is turned on if you set tty-frame-use-title (t by
default) and if emacs knows how to set it.  emacs knows how to set it
if the escape sequences are set either in termcap, or in
tty-frame-title-start/end, typically by xterm.el.  So on e.g. a text
mode virtual console with no title, it should just do nothing.

-- 
Martin 

  reply	other threads:[~2003-10-14  7:15 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031014071535.GM15872@vexed.ozlabs.hp.com \
    --to=mbp@sourcefrog.net \
    --cc=emacs-devel@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 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.