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, Ihor Radchenko <yantar92@posteo.net>,
binarin@binarin.info
Subject: bug#74467: 31.0.50; org-protocol emacsclient.desktop change is not fully functional
Date: Mon, 16 Dec 2024 23:07:26 +0200 [thread overview]
Message-ID: <39756.4068249025$1734383377@news.gmane.org> (raw)
In-Reply-To: <86cyhrpfbf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Dec 2024 22:01:56 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ihor Radchenko <yantar92@posteo.net>
>> Cc: Alexey Lebedeff <binarin@binarin.info>, 74467@debbugs.gnu.org
>> Date: Mon, 16 Dec 2024 19:34:01 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> One solution would be introducing separate .desktop file
>> >> (i.e. 'etc/emacsclient-org-protocol.desktop'), analoguous to the already
>> >> existing 'etc/emacsclient-mail.desktop' (which uses '%u').
>> >
>> > Ihor, could you please look into this?
>>
>> I am attaching an *untested* patch that implements a new .desktop file.
>
> Thanks. Let's see if someone objects.
>
>> Note that an alternative could be handling file:// URIs by Emacs. Your call.
>
> I thought we already did?
Not really if I open Emacs with a file uri such as
file:///home/bidar/test.sh /home/bidar/home/bidar/test.sh will be
opened.
Would it be possible to call file-name-handlers if a path starts with
'$uri-name://' for the files passed to Emacs or Emacsclient?
>> > (Each time such issues pop up, I regret again that we agreed to
>> > include these *.desktop files in our source tree, sigh.)
>>
>> We are obliged to cooperate with other parts of GNU toolchain, don't we?
>
> To some extent, yes. This one goes waaaay beyond that. I don't
> understand why Emacs must come with these files, instead of the
> desktop folks developing and keeping them up to date. There's nothing
> specific to Emacs in these files, just a lot of XDG and shell
> trickery.
No application I have seen so far does require shell trickery in their
desktop files. Most of one or two desktop files with some metadata and
the commands to call and that's it.
It would be easier for Emacs to follow closer to the standard instead
asking for separate implementations. I don't know how this could get any
simpler. Maybe some scripts to generate desktop files for Emacs
packages if there is no for separate desktop files per modes e.g. a
desktop file for Gnus or Info mode.
prev parent reply other threads:[~2024-12-16 21:07 UTC|newest]
Thread overview: 7+ 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
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 [this message]
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='39756.4068249025$1734383377@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 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).