From: Davide Masserut via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
65509@debbugs.gnu.org
Subject: bug#65509: [PATCH] Use correct env var when opening frames with freedesktop menu entries
Date: Sun, 03 Sep 2023 15:42:44 +0200 [thread overview]
Message-ID: <87lednz6u8.fsf@mssdvd.com> (raw)
In-Reply-To: <87wmx7jts3.fsf@yahoo.com>
Po Lu <luangruo@yahoo.com> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Not sure it's worth doing, but one option is to do both. Users
>> that
>> miss one would see the other.
>
> I won't object to such a change, though I cannot claim to
> understand the
> rationale behind it. (Who would see the message printed to
> stderr, but
> not the dialog displayed, during connection setup?)
X DEs don't set the $WAYLAND_DISPLAY environment variable, so
querying for it returns an empty string.
If I run this in X:
emacsclient --alternate-editor= --display=$WAYLAND_DISPLAY
.emacs.el
the following occurs.
When the --display argument is an empty string, Emacs first tries
to reuse an exiting frame and, if doesn't find one, it falls back
to open it in the same terminal. The problem arises when an
instance is launched through the DE facilities: Emacs can't use a
terminal as a fallback and therefore it opens in the background
without showing the frame.
If we decide that handling such case is not worth the trouble, an
error in system log should warn the user to use the X backend.
next prev parent reply other threads:[~2023-09-03 13:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 18:32 bug#65509: [PATCH] Use correct env var when opening frames with freedesktop menu entries Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-31 9:34 ` Eli Zaretskii
2023-08-31 11:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 18:43 ` Stefan Kangas
2023-09-01 19:04 ` Eli Zaretskii
2023-09-02 16:24 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 16:58 ` Eli Zaretskii
2023-09-03 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 5:34 ` Eli Zaretskii
2023-09-03 6:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 12:13 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 12:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 12:48 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 12:51 ` Stefan Kangas
2023-09-03 13:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 13:31 ` Stefan Kangas
2023-09-03 13:42 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-04 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 14:46 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 0:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 14:01 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 8:26 ` Eli Zaretskii
2023-09-07 9:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 9:37 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:49 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 7:05 ` Eli Zaretskii
2023-09-15 7:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 7:32 ` Eli Zaretskii
2023-09-15 7:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 11:34 ` 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
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=87lednz6u8.fsf@mssdvd.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65509@debbugs.gnu.org \
--cc=dm@mssdvd.com \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.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).