unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Pool <mbp@sourcefrog.net>
Cc: Eli Zaretskii <eliz@elta.co.il>, emacs-devel@gnu.org
Subject: Re: suggested feature -- console-mode frame title sets Xterm title
Date: Tue, 14 Oct 2003 17:44:34 +1000	[thread overview]
Message-ID: <20031014074430.GN15872@vexed.ozlabs.hp.com> (raw)
In-Reply-To: <buohe2cs2eg.fsf@mcspd15.ucom.lsi.nec.co.jp>

On 14 Oct 2003, Miles Bader <miles@lsi.nec.co.jp> wrote:
> Martin Pool <mbp@sourcefrog.net> writes:
> > Some people like to have information in the title bar that won't fit
> > in their modeline.
> 
> I'm confused -- is there actually any question that this is a useful
> feature?  

That was what I thought Eli was asking.  Maybe I misunderstood his
question.

> I'm constantly annoyed by `full screen' programs in terminal
> emulators that _don't_ update the titlebar; it's a very useful feature,
> above and beyond the mode-line.

That's how I feel.

> > > 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?
> 
> That seems silly; why not just do _both_?  The `Fn' notation doesn't
> take up much room in the mode-line, and is simply _different_
> information that the actual title.  They're both handy.  So why not
> introduce the concept of a `frame index' and display F%d of that in the
> mode-line on terminals (hell some people might want to display it in X
> too -- it's just a generally handy concept, given that the emacs frame
> commands tend to cycle through frames in order).  [I _think_ this is
> the last possibility you suggested in your original post]

Yes, that's what I was getting at.  For the sake of discussion let's
use the term 'frame index'.  

This even makes sense in terms of the 21.3 manual, which half implies
that this already exists:

   Each frame has a number to distinguish it.  If your terminal can
   display only one frame at a time, the selected frame's number N appears
   near the beginning of the mode line, in the form `FN'.

The problem is in the next paragraph: 

    `FN' is actually the frame's name.  You can also specify a
    different name if you wish, and you can select a frame by its
    name.  Use the command `M-x set-frame-name <RET> NAME <RET>' to
    specify a new name for the selected frame, and use `M-x
    select-frame-by-name <RET> NAME <RET>' to select a frame according
    to its name.  The name you specify appears in the mode line when
    the frame is selected.

'F%d' would no longer be the frame's name.

Suppose we added a select-frame-by-index function?  

People would still be able to select-frame-by-name, but the names they
use would be those produced by frame-title-format or set-frame-name,
and never F%d.

Doing this would remove the ugliness of hiding
mode-line-frame-identification on window-system frames.

You could even put the frame index into the frame-title.

-- 
Martin 

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

  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=20031014074430.GN15872@vexed.ozlabs.hp.com \
    --to=mbp@sourcefrog.net \
    --cc=eliz@elta.co.il \
    --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 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).