unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 74467@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	binarin@binarin.info
Subject: bug#74467: 31.0.50; org-protocol emacsclient.desktop change is not fully functional
Date: Tue, 07 Jan 2025 10:05:02 +0200	[thread overview]
Message-ID: <87jzb782xd.fsf@thaodan.de> (raw)
In-Reply-To: <877c77hjf2.fsf@localhost> (Ihor Radchenko's message of "Mon, 06 Jan 2025 18:44:01 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> Björn Bidar <bjorn.bidar@thaodan.de> writes:
>
>> Calling a shell and then the program is more complicated as the argument
>> supplied to Emacs first run through the shell and then Emacs making the
>> arguments subject to the shell parsing rules.
>> ...
>> It does fix that but dropping the shell in this context helps to avoid any
>> later potential issues.
>
> Maybe. But how does it have anything to do with the particular bug we
> are discussing now?
I'm not sure I merely mentioned it because of the issues we have been
facing regarding the desktop files.

> If you have ideas how to improve the sh command in the .desktop file, I
> suggest moving such discussion to emacs-devel.

I suggest to call Emacsclient without sh but yeah good call.





  reply	other threads:[~2025-01-07  8:05 UTC|newest]

Thread overview: 23+ 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
     [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
2024-12-28 11:37       ` Eli Zaretskii
2025-01-02 20:02         ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]         ` <87zfk9q91e.fsf@>
2025-01-04 13:18           ` Eli Zaretskii
2025-01-04 22:07             ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]             ` <877c7aw7va.fsf@>
2025-01-05  6:39               ` Eli Zaretskii
2025-01-05  8:55                 ` Ihor Radchenko
2025-01-05 18:13                   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                   ` <87wmf9t9hm.fsf@>
2025-01-05 18:36                     ` Ihor Radchenko
2025-01-05 21:31                       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                       ` <87cyh1t0ag.fsf@>
2025-01-06 18:44                         ` Ihor Radchenko
2025-01-07  8:05                           ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-11 11:09                   ` Eli Zaretskii
2025-01-05 18:20                 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                 ` <87sepxt953.fsf@>
2025-01-05 19:11                   ` 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=87jzb782xd.fsf@thaodan.de \
    --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).