From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74467@debbugs.gnu.org, Alexey Lebedeff <binarin@binarin.info>,
Ihor Radchenko <yantar92@posteo.net>
Subject: bug#74467: 31.0.50; org-protocol emacsclient.desktop change is not fully functional
Date: Sat, 23 Nov 2024 21:58:22 +0200 [thread overview]
Message-ID: <1839.32108791254$1732391970@news.gmane.org> (raw)
In-Reply-To: <86seriksak.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 23 Nov 2024 15:12:35 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> (Each time such issues pop up, I regret again that we agreed to
> include these *.desktop files in our source tree, sigh.)
Part of the issue with the desktop files is that someone of some them
try to execute multiple lines of shell script in them which can always
create issues.
It would be much better if desktop file calls only emacsclient
and it takes care by itself if DISPLAY is set and doesn't use sh.
Can Emacs handle file:/ URI's? If so simply changing from %F to %U would
be an option.
next prev parent reply other threads:[~2024-11-23 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 18:53 bug#74467: 31.0.50; org-protocol emacsclient.desktop change is not fully functional Alexey Lebedeff via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 13:12 ` Eli Zaretskii
2024-11-23 19:58 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-07 12:17 ` Eli Zaretskii
2024-12-16 19:34 ` Ihor Radchenko
2024-12-16 20:01 ` Eli Zaretskii
2024-12-16 21:07 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87o71bgwvl.fsf@>
2024-12-17 12:15 ` Eli Zaretskii
2024-12-17 13:00 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='1839.32108791254$1732391970@news.gmane.org' \
--to=bug-gnu-emacs@gnu.org \
--cc=74467@debbugs.gnu.org \
--cc=binarin@binarin.info \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=yantar92@posteo.net \
/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.