all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: 36839@debbugs.gnu.org
Subject: bug#36839: 26.1: unique frame names
Date: Mon, 29 Jul 2019 12:16:06 -0400	[thread overview]
Message-ID: <20190729161606.fyjwowadnuwe27zd@E15-2016.optimum.net> (raw)

Subject: 26.1; unique frame names

By default, emacs creates frames with unique names, in the form "Fnn".
Emacs also offers a documented variable `default-frame-alist', which one
can use to customize frame parameters, one of which is NAME. However, I
don't see documented anywhere how to specify that frame names should be
unique, and when setting the NAME parameter, all new frames are created with
identical names:

   (setq default-frame-alist '((name . "Frame_%")))

My attempt to trace the code ended with `make-terminal-frame', a
built-in function in ‘src/frame.c’, since I don't have that source file handy.

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.

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





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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 16:16 Boruch Baum [this message]
2019-07-29 17:00 ` bug#36839: 26.1: unique frame names Eli Zaretskii
2019-07-29 17:49   ` Boruch Baum
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=20190729161606.fyjwowadnuwe27zd@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=36839@debbugs.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.