unofficial mirror of emacs-devel@gnu.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 13:59:33 +1000	[thread overview]
Message-ID: <20031014035931.GH15872@vexed.ozlabs.hp.com> (raw)
In-Reply-To: <E1A5p16-0001Wq-3Y@fencepost.gnu.org>

On  4 Oct 2003, Richard Stallman <rms@gnu.org> wrote:
>     Sorry, I meant select-frame-by-name.
> 
>     >       For multi-frame text terminals the names
>     >     used to be F%d, but now they're "full" names, probably including the
>     >     name of the buffer.
> 
> Now I understand.  But I think this is an undesirable
> side effect that the user will notice.  Can you find a way
> to avoid altering these names?

I've thought about this and I can't think of a completely satisfactory
way to reconcile the differences between window-system and text frames
in the existing documented behaviour.

I don't feel qualified to decide what to break.  If you let me know
how you would like it to behave I'll try to write a patch.

I'd guess the number of people using multiple frames on a text
terminal is fairly small, though non-zero.  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.

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'd choose this because in the long term it's
better to move towards internal consistency at the price of sometimes
breaking things.

In some ways this is an improvement: when people have multiple frames,
they will by default be named using buffer names, which are more
meaningful than F%d.  If people give their frames explicit names
either by hand or from code then those names will work the same way.
C-x 5 commands will also still be the same.

I haven't ever seriously used multiple termcap frames.  Maybe somebody
who does use them has an opinion.

Alternatively we could add an option to give tty frames these names as
'explicit names'.  I would probably have it off by default, because
for users who weren't specifically using this feature they're less
friendly than the names produced by frame-title-format.

Yet another option would be to introduce a new user-visible concept of
a "frame number".  That wouldn't preserve the exact same behaviour and
I'm not sure it would be useful, but if you really want to preserve
F%d it might be the best way.

On the whole I think just making the behaviour the same will please
many people, and annnoy fairly few, and be good for the code.  But let
me know what you want and I'll write it.

-- 
Martin 

  parent reply	other threads:[~2003-10-14  3:59 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 [this message]
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
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=20031014035931.GH15872@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 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).