From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: dm@mssdvd.com, stefankangas@gmail.com, 65509@debbugs.gnu.org
Subject: bug#65509: [PATCH] Use correct env var when opening frames with freedesktop menu entries
Date: Fri, 15 Sep 2023 10:32:29 +0300 [thread overview]
Message-ID: <83r0mzki2a.fsf@gnu.org> (raw)
In-Reply-To: <87ttrvzz8v.fsf@yahoo.com> (message from Po Lu on Fri, 15 Sep 2023 15:12:16 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Davide Masserut <dm@mssdvd.com>, stefankangas@gmail.com,
> 65509@debbugs.gnu.org
> Date: Fri, 15 Sep 2023 15:12:16 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Ping! Po Lu, could you please respond?
> >
> >> From: Davide Masserut <dm@mssdvd.com>
> >> Cc: stefankangas@gmail.com, 65509@debbugs.gnu.org
> >> Date: Fri, 08 Sep 2023 17:49:43 +0200
> >>
> >>
> >> Po Lu <luangruo@yahoo.com> writes:
> >>
> >> > Eli Zaretskii <eliz@gnu.org> writes:
> >> >
> >> >>> From: Davide Masserut <dm@mssdvd.com>
> >> >>> Cc: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
> >> >>> 65509@debbugs.gnu.org
> >> >>> Date: Wed, 06 Sep 2023 16:01:58 +0200
> >> >>>
> >> >>> It turns out that Emacs 29 has new CLI option that solves exactly these problems.
> >> >>>
> >> >>> The attached patch replaces the usage of --display=$DISPLAY with --reuse-frame.
> >> >>
> >> >> Po Lu, any objections to installing this on emacs-29?
> >> >
> >> > Yes. Davide, would you please rewrite the patch so that your change is
> >> > only applied to the PGTK port?
> >>
> >> Done. Po, why can't we use --reuse-frame in X builds?
> >>
> >>
> >> >From 43085522a08b94ef594bd270d61a38d7bb26e036 Mon Sep 17 00:00:00 2001
> >> From: Davide Masserut <dm@mssdvd.com>
> >> Date: Thu, 24 Aug 2023 18:33:39 +0200
> >> Subject: [PATCH] Avoid using --display to reuse frames in PGTK
> >>
> >> Using hard-coded display values can cause PGTK graphical frames to
> >> open using the wrong backend or not open at all.
> >>
> >> * Makefile.in (install-etc): Use --reuse-frame instead of
> >> --display=$DISPLAY.
> >> ---
> >> Makefile.in | 5 +++++
> >> 1 file changed, 5 insertions(+)
> >>
> >> diff --git a/Makefile.in b/Makefile.in
> >> index fdd9353e254..c82aad1af60 100644
> >> --- a/Makefile.in
> >> +++ b/Makefile.in
> >> @@ -843,6 +843,9 @@ EMACS_ICON=
> >> ifeq (${USE_STARTUP_NOTIFICATION},no)
> >> USE_STARTUP_NOTIFICATION_SED_CMD=-e "/^StartupNotify=true$$/d"
> >> endif
> >> +ifeq ($(HAVE_PGTK),yes)
> >> +USE_WAYLAND_DISPLAY_SED_CMD=-e "s/display=[^ ]*/reuse-frame/"
> >> +endif
> >> install-etc:
> >> umask 022; ${MKDIR_P} "$(DESTDIR)${desktopdir}"
> >> tmp=etc/emacs.tmpdesktop; rm -f $${tmp}; \
> >> @@ -857,6 +860,7 @@ install-etc:
> >> sed -e "/^Exec=/ s|emacsclient|${bindir}/$${client_name}|" \
> >> -e "/^Icon=emacs/ s/emacs/${EMACS_NAME}/" \
> >> $(USE_STARTUP_NOTIFICATION_SED_CMD) \
> >> + $(USE_WAYLAND_DISPLAY_SED_CMD) \
> >> ${srcdir}/etc/emacsclient.desktop > $${tmp}; \
> >> ${INSTALL_DATA} $${tmp} "$(DESTDIR)${desktopdir}/$${client_name}.desktop"; \
> >> rm -f $${tmp}
> >> @@ -870,6 +874,7 @@ install-etc:
> >> client_name=`echo emacsclient | sed '$(TRANSFORM)'`${EXEEXT}; \
> >> sed -e "/^Exec=/ s|emacsclient|${bindir}/$${client_name}|" \
> >> -e "/^Icon=emacs/ s/emacs/${EMACS_NAME}/" \
> >> + $(USE_WAYLAND_DISPLAY_SED_CMD) \
> >> ${srcdir}/etc/emacsclient-mail.desktop > $${tmp}; \
> >> ${INSTALL_DATA} $${tmp} "$(DESTDIR)${desktopdir}/$${client_name}-mail.desktop"; \
> >> rm -f $${tmp}
> >> --
> >> 2.42.0
> >>
>
> That was lost in the spam filter. I'd rather not use --reuse-frame
> under the X build, because that's not safe for Emacs 29.
Why is it not safe?
> This LGTM now.
Thanks.
next prev parent reply other threads:[~2023-09-15 7:32 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r0mzki2a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65509@debbugs.gnu.org \
--cc=dm@mssdvd.com \
--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 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.