all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36839@debbugs.gnu.org
Subject: bug#36839: 26.1: unique frame names
Date: Mon, 29 Jul 2019 13:49:33 -0400	[thread overview]
Message-ID: <20190729174933.jkov4mji5uovxlm6@E15-2016.optimum.net> (raw)
In-Reply-To: <83imrkkc6y.fsf@gnu.org>

On 2019-07-29 20:00, Eli Zaretskii wrote:
> > Date: Mon, 29 Jul 2019 12:16:06 -0400
> > From: Boruch Baum <boruch_baum@gmx.com>
> >
> > My expectation is that emacs should by default create frames with unique
> > names, similar to how it uniquely names buffers, by appending a number
> > to what would otherwise be a duplicate name.
>
> Are you sure you don't confuse a frame's name with its title?

I'm referring to the NAME parameter of the alist variable, which sets
the frame NAME that appears by default in the mode-line, and which is
used by function `select-frame-by-name'. I'm not sure what you mean by
frame title.

> In general, a frame's name is Emacs's internal business, and is rarely
> if ever exposed to the user. About the only exception I know of is TTY
> frames. I'd be interested to know why you care about a frame's name,
> i.e. what is your use case.

I'm using C-x 5 b (M-x select-frame-by-name) to switch between frames
and in my case, I would like the names to be more informative than just
Fnn. In a more general sense, if emacs is offering the NAME parameter,
it should assume the parameter will be used, and currently emacs isn't
handling its use well.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





  reply	other threads:[~2019-07-29 17:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 16:16 bug#36839: 26.1: unique frame names Boruch Baum
2019-07-29 17:00 ` Eli Zaretskii
2019-07-29 17:49   ` Boruch Baum [this message]
2019-07-29 18:00     ` Eli Zaretskii
2019-07-29 18:54       ` Boruch Baum
2019-07-29 19:28         ` Eli Zaretskii
2019-07-29 19:43           ` Boruch Baum
2019-07-30 15:11             ` Eli Zaretskii
2022-03-23 13:38               ` Lars Ingebrigtsen
2019-07-31  9:13     ` martin rudalics
2019-07-31 14:10       ` Eli Zaretskii
2019-08-01  8:54         ` martin rudalics
2019-08-02  8:57           ` Eli Zaretskii
2019-08-02 12:50             ` martin rudalics
2019-07-29 17:43 ` Andreas Schwab
2019-07-29 18:00   ` Boruch Baum
2019-07-29 20:42     ` Andreas Schwab

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=20190729174933.jkov4mji5uovxlm6@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=36839@debbugs.gnu.org \
    --cc=eliz@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.