unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-pretest-bug@gnu.org, 'Damon Permezel' <permezel@mac.com>,
	'Emacs-Devel' <emacs-devel@gnu.org>
Subject: Re: should frame names be unique?
Date: Fri, 21 Mar 2008 21:12:10 -0400	[thread overview]
Message-ID: <jwvod97efeq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <007001c88b92$1f99ac30$0600a8c0@us.oracle.com> (Drew Adams's message of "Fri, 21 Mar 2008 13:28:28 -0700")

>> Try
>> 
>> (setq frame-title-format
>> '(multiple-frames ("F"
>> (:eval (number-to-string
>> (length (memq
> (selected-frame)
>> 
> (frame-list)))))
>> " %b")
>> ("" invocation-name "@"
> system-name)))

> This is about commands that interact with user frames.  It's
> not appropriate to ask users to name their frames in some
> particular way. But perhaps I misunderstand you.

I was just proposing a way that gives a unique name to each frame.
Those people who suffer from the problems you cite may like to use it.
I'm not suggesting it as a general solution, which is obvious since I'm
not sure what is the problem.

>> I'm not opposed to making frame names unique, but first, I'd like to
>> hear about the use-cases where it matters.

> Think of the Frames menu.  If you have multiple frames
> showing the same buffer, then you will have multiple
> identical entries in the Frames menu.  No way to know which
> is which, which makes them pretty useless.

Yup, pretty useless.  So if it hurts, don't do that.

>> I.e. what uses of frame-names are we talking about
>> (select-frame-by-name?  The Frames menu?)?

> Yes, both. Though select-frame-by-name apparently removes
> duplicates, so AFAICT it doesn't even let you select some of
> the frames (a bug?).

Not a bug: a fundamental limitation of the command: you can't select by
name and at the same time distinguish between two objects that have the
same name.

> (The example that brought this up was an Icicles
> multi-command version of select-frame-by-name.)

Yes, but I don't know where it fits: if it just creates different names
in the names-list without actually changing the frame names, then the
problem is the same as the Frames menu: you can select any frame, but
you have no way to know beforehand which name corresponds to which frame
(among those that have the same name).

>> What is the difference between those frames showing the same buffer
>> (is it just to display two different parts of a buffer, if so do the
>> various frames play different roles?  Are they on different screens?
>> Can you see their names in the title bar? ...)

> I can't answer any of those questions.

So you're not faced with this problem in practice.  It's just
a hypothetical issue?


        Stefan




  reply	other threads:[~2008-03-22  1:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  3:41 difficulty creating unique frame names Damon Permezel
2008-03-21 15:40 ` should frame names be unique? [was: difficulty creating unique frame names] Drew Adams
2008-03-21 18:23   ` should frame names be unique? Stefan Monnier
2008-03-21 20:28     ` Drew Adams
2008-03-22  1:12       ` Stefan Monnier [this message]
2008-03-22  1:58         ` Damon Permezel
2008-03-22 16:55           ` Stefan Monnier
2008-03-22 18:12             ` Drew Adams
2008-03-23  0:47               ` Stefan Monnier
2008-03-22  2:34         ` Drew Adams
2008-03-22  9:50           ` Eli Zaretskii
2008-03-22 15:38             ` Drew Adams
2008-03-22 17:29               ` Eli Zaretskii
2008-03-22  1:43       ` Damon Permezel
2008-03-22  9:51         ` Eli Zaretskii

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=jwvod97efeq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=permezel@mac.com \
    /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).