From: Visuwesh <visuweshm@gmail.com>
To: 41719@debbugs.gnu.org
Cc: luangruo@yahoo.com, eliz@gnu.org, lomov.vl@yandex.ru
Subject: bug#41719: 28.0.50; [FR] emacsclient should provide '--name' option as emacs
Date: Sun, 12 Jun 2022 14:19:18 +0530 [thread overview]
Message-ID: <87pmjeuv01.fsf@gmail.com> (raw)
In-Reply-To: <87czfefgxg.fsf@yahoo.com> (Po Lu via's message of "Sun, 12 Jun 2022 16:02:19 +0800")
[ஞாயிறு ஜூன் 12, 2022 16:02] Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:
> Visuwesh <visuweshm@gmail.com> writes:
>
>> WM_CLASS and WM_NAME are commonly matched against in "window manager
>> rules." For example, I have a script that essentially calls
>> `make-frame' with a specific frame `name' [*] which I then match against
>> in my window manager configuration to move the frame to the top right
>> corner of my screen.
>>
>> [*] I see that Emacs sets WM_CLASS and WM_NAME to the `name' frame
>> parameter.
>>
>> % xprop |grep wm_'\(class\|name\)'
>> _NET_WM_NAME(UTF8_STRING) = "vz/calendar-frame"
>> WM_CLASS(STRING) = "vz_calendar-frame", "Emacs"
>> WM_NAME(STRING) = "vz/calendar-frame"
>
> Class hints are only set by Emacs under X toolkit and no toolkit builds.
> On GTK builds, it's set by GTK to a value set during GTK initialization.
>
That checks out. I use a lucid build.
> BTW, the `name' frame parameter is rather special, since it's set by
> `x-create-frame' binding special values to `x-resource-name' and
> `x-resource-class' during frame creation. So for the record, changing
> the `name' parameter of a frame after it is created will not change the
> values of the WM_CLASS and WM_NAME properties.
Ah, thanks for the info. I was afraid the WM_NAME property would change
when the frame title changes.
next prev parent reply other threads:[~2022-06-12 8:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 3:09 bug#41719: 28.0.50; [FR] emacsclient should provide '--name' option as emacs Vladimir Lomov
2020-06-05 11:14 ` Basil L. Contovounesios
2020-06-05 16:53 ` Vladimir Lomov
2020-06-06 12:36 ` Dmitry Alexandrov
2020-06-06 14:52 ` Vladimir Lomov
2020-06-06 17:08 ` Dmitry Alexandrov
2020-06-06 18:24 ` Dmitry Alexandrov
2020-06-07 14:26 ` bug#41719: 28.0.50; emacsclient -c -F '((name . "NAME"))' is not respected --with-x-toolkit=gtk328.0.50 (Was: [FR] emacsclient should provide '--name' option as emacs) Vladimir Lomov
2020-06-07 16:15 ` bug#41719: 28.0.50; emacsclient -c -F '((name . "NAME"))' is not respected --with-x-toolkit=gtk3 Dmitry Alexandrov
2020-06-09 7:12 ` Vladimir Lomov
2022-02-10 7:17 ` Lars Ingebrigtsen
2022-03-12 22:45 ` Lars Ingebrigtsen
2022-06-11 13:00 ` bug#41719: 28.0.50; emacsclient -c -F '((name . "NAME"))' is Colin Horne
2022-06-11 13:46 ` Colin Horne
2022-06-12 5:10 ` bug#41719: 28.0.50; [FR] emacsclient should provide '--name' option as emacs Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-12 6:32 ` Eli Zaretskii
2022-06-12 6:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-12 7:03 ` Eli Zaretskii
2022-06-12 7:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-12 7:26 ` Eli Zaretskii
2022-06-12 7:52 ` Visuwesh
2022-06-12 8:00 ` Eli Zaretskii
2022-06-12 8:47 ` Visuwesh
2022-06-12 8:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-12 8:20 ` Andreas Schwab
2022-06-12 8:49 ` Visuwesh [this message]
2022-06-12 8:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-12 8:54 ` Visuwesh
2022-06-12 9:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-14 3:04 ` Vladimir Lomov
2022-06-14 4:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-14 6:00 ` Vladimir Lomov
2022-06-14 6:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-14 11:23 ` 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=87pmjeuv01.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=41719@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lomov.vl@yandex.ru \
--cc=luangruo@yahoo.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.