all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
	"'Damon Permezel'" <permezel@mac.com>
Cc: emacs-pretest-bug@gnu.org, 'Emacs-Devel' <emacs-devel@gnu.org>
Subject: RE: should frame names be unique?
Date: Sat, 22 Mar 2008 11:12:49 -0700	[thread overview]
Message-ID: <000901c88c48$56ff1230$0600a8c0@us.oracle.com> (raw)
In-Reply-To: <jwvfxuid85l.fsf-monnier+emacs@gnu.org>

> Your case didn't sound hypothetical indeed.  Drew's does, tho.

Uh, I was reporting Damon's case, AFAIK.

The original context for this was Damon's use of `icicle-select-frame', which
used `select-frame-by-name' at that time. (In Icicles, `C-0 C-x o' lets you
select frames by name, with completion. It now uses unique frame names.) 

Damon's original context was not the Frames menu. The general problem of
non-unique frame names exists for the Frames menu also, so I replied "both" to
your question. 

The point is the general limitation wrt frame names, not the particular by-name
access method. Frame names should be unique for the same reason that buffer
names should be unique.

> Basically, frame names in GUIs are currently assumed to be pretty much
> "display only", so they don't matter and having them unique 
> or not is of fairly low importance.

That's again just describing the status quo. It's not a justification: your "so"
doesn't follow. It's not _because_ the Emacs GUI or some other GUI currently
doesn't uniquify frame names that they should not be unique. The Emacs GUI
evolves, and it already has features that other GUIs do not have.

> This said, I wouldn't reject a patch that makes them unique,

I hope someone provides such a patch. If it were Lisp, not C, then I might.

> although I'd rather such a patch to only make them unique on a particular
> terminal, since I often access a single Emacs process from different
> terminals and would rather have most of my frames suddenly 
> get all named "foo<2>" just because there's already a "foo" on some
> other terminal.

I can't speak to the case for terminals. Everything I've said about this is for
the GUI case. If non-unique frames are inappropriate in some terminal contexts,
then exclude those contexts.

And if there is a good reason that some user might not want unique names in a
GUI context, then we could add an option for it. I can't imagine that, any more
than I can imagine a user wanting non-unique buffer names, but perhaps there is
such a reason.





  reply	other threads:[~2008-03-22 18: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
2008-03-22  1:58         ` Damon Permezel
2008-03-22 16:55           ` Stefan Monnier
2008-03-22 18:12             ` Drew Adams [this message]
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

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

  git send-email \
    --in-reply-to='000901c88c48$56ff1230$0600a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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 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.