From: Jim Porter <jporterbugs@gmail.com>
To: Robert Pluim <rpluim@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: Damien Cassou <damien@cassou.me>, Eli Zaretskii <eliz@gnu.org>,
git@mavit.org.uk, 57752@debbugs.gnu.org
Subject: bug#57752: 28.1.91; emacsclient-mail.desktop doesn't work for me
Date: Fri, 16 Sep 2022 08:21:23 -0700 [thread overview]
Message-ID: <b707b1a1-b0fd-41c3-0df9-f2322732fa0b@gmail.com> (raw)
In-Reply-To: <877d23iesn.fsf@gmail.com>
On 9/16/2022 7:18 AM, Robert Pluim wrote:
> There are also quoting and conversion issues to think about, eg:
>
> emacs --function foo hello 3 indent-tabs-mode 'always
>
> Do we make people say
>
> "hello" if they want strings, which implies that indent-tabs-mode
> would be treated as a variable, 3 as a number, and the ' needs to be
> escaped somehow?
Hopefully not, since one of the goals here is to be able to accept
arbitrary strings from other programs (e.g. your mailto: handler). If we
required strings to look "like this", then it becomes much more
difficult to ensure that internal quotation marks are properly escaped.
Instead, I think the arguments passed this way should always be strings.
If you need something fancier, --eval can step in. (Of course, a
function called with --function can convert its arguments however it likes.)
next prev parent reply other threads:[~2022-09-16 15:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 18:31 bug#57752: 28.1.91; emacsclient-mail.desktop doesn't work for me Damien Cassou
2022-09-13 12:19 ` Lars Ingebrigtsen
2022-09-13 13:29 ` Damien Cassou
2022-09-13 13:41 ` Eli Zaretskii
2022-09-13 13:58 ` Damien Cassou
2022-09-13 14:57 ` Robert Pluim
2022-09-13 15:32 ` Damien Cassou
2022-09-15 18:30 ` Jim Porter
2022-09-16 9:54 ` Lars Ingebrigtsen
2022-09-16 10:09 ` Robert Pluim
2022-09-16 10:14 ` Lars Ingebrigtsen
2022-09-16 14:18 ` Robert Pluim
2022-09-16 15:21 ` Jim Porter [this message]
2022-09-16 12:38 ` Damien Cassou
2022-09-16 12:50 ` Gregory Heytings
2022-09-16 14:46 ` Damien Cassou
2022-09-16 15:07 ` Gregory Heytings
2022-09-16 16:18 ` Peter Oliver
2022-09-16 16:42 ` Gregory Heytings
2022-09-16 17:21 ` Jim Porter
2022-09-16 18:26 ` Gregory Heytings
2022-09-16 19:33 ` Jim Porter
2022-09-16 20:04 ` Gregory Heytings
2022-09-18 13:58 ` Robert Pluim
2022-09-16 14:19 ` Robert Pluim
2022-09-16 14:47 ` Damien Cassou
2022-09-16 15:17 ` Jim Porter
2022-09-18 10:23 ` Lars Ingebrigtsen
2022-09-18 14:46 ` Robert Pluim
2022-09-19 8:09 ` Lars Ingebrigtsen
2022-09-18 18:31 ` Jim Porter
2022-09-19 8:12 ` Lars Ingebrigtsen
2022-09-19 15:48 ` Jim Porter
2022-09-19 18:45 ` Lars Ingebrigtsen
2022-09-19 8:56 ` Gregory Heytings
2022-09-19 12:00 ` Lars Ingebrigtsen
2022-09-19 16:05 ` Jim Porter
2022-09-19 17:01 ` Gregory Heytings
2022-12-02 14:52 ` Max Nikulin
2023-07-26 5:14 ` Max Nikulin
2022-09-16 19:42 ` Jim Porter
2022-09-18 10:26 ` Lars Ingebrigtsen
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=b707b1a1-b0fd-41c3-0df9-f2322732fa0b@gmail.com \
--to=jporterbugs@gmail.com \
--cc=57752@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=eliz@gnu.org \
--cc=git@mavit.org.uk \
--cc=larsi@gnus.org \
--cc=rpluim@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).