From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Damien Cassou <damien@cassou.me>
Cc: Peter Oliver <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 12:42:34 -0700 [thread overview]
Message-ID: <393f4388-f3da-1b54-9b7d-be99ed3498d7@gmail.com> (raw)
In-Reply-To: <87bkrj31r0.fsf@gnus.org>
On 9/13/2022 5:19 AM, Lars Ingebrigtsen wrote:
> I'd prefer to have a .desktop file that works without any helper
> scripts. Can't the emacsclient-mail.desktop file be rewritten to not
> use quoting here?
Here's another strategy for handling this, inspired by org-protocol[1].
For those who haven't used it, org-protocol invokes emacsclient with an
"org-protocol://..." URL to let you do things like capture text from
another application.
Extending from that, what if Emacs introduced URL handlers, so that these:
emacs mailto:foo@bar.com
emacsclient mailto:foo@bar.com
would look up a "mailto:" handler defined somewhere in Emacs[2] (e.g.
'message-mailto') and call that function instead of 'find-file'. This is
roughly how the org-protocol module handles this, although it only works
for emacsclient (it adds advice to a few functions from server.el).
This would be less flexible than having a generic way of feeding certain
command-line arguments to an Emacs Lisp function, but I'm not sure what
practical uses we'd need that for aside from handling URLs, as in this
bug or for org-protocol. If there are some other uses people have for
the more-flexible implementation, I think it would help to list those so
we can be sure the chosen solution addresses them.
[1] https://orgmode.org/manual/Protocols.html
[2] Possibly opt-in in the user's config. I don't have any preferences here.
next prev parent reply other threads:[~2022-09-16 19:42 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
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 [this message]
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=393f4388-f3da-1b54-9b7d-be99ed3498d7@gmail.com \
--to=jporterbugs@gmail.com \
--cc=57752@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=git@mavit.org.uk \
--cc=larsi@gnus.org \
/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).