From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Damien Cassou <damien@cassou.me>,
Jim Porter <jporterbugs@gmail.com>, 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 12:09:07 +0200 [thread overview]
Message-ID: <87bkrfiqbg.fsf@gmail.com> (raw)
In-Reply-To: <878rmjy78x.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 16 Sep 2022 11:54:22 +0200")
>>>>> On Fri, 16 Sep 2022 11:54:22 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> I've idly wondered before whether we should add a general mechanism for
Lars> this to avoid having to create functions that look at
Lars> `command-line-args-left' themselves. (And --eval is problematic in
Lars> circumstances like this.)
emacsclient interprets
emacsclient arg1 arg2 --eval (form1) (form2) (form3)
as "send (form1), then (form2) then (form3), so by analogy this:
Lars> --function foo --function-args bar zot gazonk
doesnʼt require a --function-args parameter
Lars> would result in calling `foo' with those arguments.
Lars> Hm... would we need some way to say "here's the end of
Lars> --function-args", perhaps? "--"? So:
and this also isnʼt necessary, since the end of args is implicit by
reaching the end of the arguments, same as '--eval'
Lars> --function foo --function-args bar zot gazonk --
Lars> Anybody have any thoughts here?
I idly wondered whether emacsclient could create a monster ʼ--evalʼ
form with a binding for `command-line-args-left', but then I started
having nightmares about string handling in C, so perhaps itʼs best to
just send stuff over to emacs and let server.el handle it :-)
Robert
--
next prev parent reply other threads:[~2022-09-16 10:09 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 [this message]
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
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=87bkrfiqbg.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=57752@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=eliz@gnu.org \
--cc=git@mavit.org.uk \
--cc=jporterbugs@gmail.com \
--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).