From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 36839@debbugs.gnu.org
Subject: bug#36839: 26.1: unique frame names
Date: Mon, 29 Jul 2019 22:28:41 +0300 [thread overview]
Message-ID: <83a7cwk5cm.fsf@gnu.org> (raw)
In-Reply-To: <20190729185429.hnmmck6fy3pf6jud@E15-2016.optimum.net> (message from Boruch Baum on Mon, 29 Jul 2019 14:54:29 -0400)
> Date: Mon, 29 Jul 2019 14:54:29 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: 36839@debbugs.gnu.org
>
> > Then give your frames names, you have functions to do that. What
> > exactly is the problem?
>
> I'm trying really hard not to repeat myself here... Emacs has the alist
> variable with the NAME parameter, so the presumption is that a user
> should be able to use it in a useful manner, but when it is used, the
> behavior of emacs changes to become less useful. Prior to manually
> setting the NAME parameter, all created frames have unique names, but
> once the name parameter is set by a user, all frames will have identical
> names. The behavior should continue to ensure unique frame names.
So you want Emacs to uniquify the frame's name using the 'name'
parameter as a template?
next prev parent reply other threads:[~2019-07-29 19:28 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
2019-07-29 18:00 ` Eli Zaretskii
2019-07-29 18:54 ` Boruch Baum
2019-07-29 19:28 ` Eli Zaretskii [this message]
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
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=83a7cwk5cm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36839@debbugs.gnu.org \
--cc=boruch_baum@gmx.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).