From: Max Nikulin <firstname.lastname@example.org>
Subject: Re: Lazy load of org-protocol
Date: Thu, 10 Feb 2022 21:44:40 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 10/02/2022 02:22, Jim Porter wrote:
> On 2/9/2022 8:46 AM, Max Nikulin wrote:
>>> On a related note, there is still an issue with `--eval' in some
>>> cases. It fails to work with emacsclient when invoking an alternate
>>> emacsclient --alternate-editor emacs --eval '(message "hi")'
>>> If Emacs isn't already running, that will open a new buffer named
>>> '(message "hi")'. I think that's just a bug in how emacsclient
>>> handles `--eval', though fixing it would make org-protocol links work
>>> more reliably (if they used `--eval' as proposed, that is).
>> emacsclient --alternate-editor '' --eval '(message "hi")'
>> But it makes it harder to use it during debugging when -Q -L
>> ~/src/org-mode/lisp options are required.
> Right, invoking the main Emacs instance as a daemon (i.e. when
> --alternate-editor is the empty string) works pretty differently from
> invoking the main Emacs instance directly (i.e. when --alternate-editor
> is "emacs" or somesuch). In the former case, emacsclient starts "emacs
> --daemon" and then tries to reconnect to the daemon; in the latter, it
> just takes the arguments passed to emacsclient and forwards them (well,
> some of them) to emacs. The end result is that it runs "emacs '(message
> "hi")'", which isn't correct.
It looks like a bug. I believed that other application may be specified
as --alternate-editor, so --eval arguments should not be passed to it.
Actually I do not like --alternate-editor option at all. It is a single
string, not an array of executable and options. It allows quotes but
does not support escaping.
On linux a solution is to start emacs daemon from systemd session as a
next prev parent reply other threads:[~2022-02-10 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 11:54 Lazy load of org-protocol Max Nikulin
2022-02-05 18:27 ` Jim Porter
2022-02-06 16:42 ` Max Nikulin
2022-02-06 19:40 ` Jim Porter
2022-02-07 14:57 ` Max Nikulin
2022-02-07 19:06 ` Jim Porter
2022-02-09 16:46 ` Max Nikulin
2022-02-09 19:22 ` Jim Porter
2022-02-10 14:44 ` Max Nikulin [this message]
2022-02-08 10:44 ` Emacs-orgmode Digest, Vol 192, Issue 8 Tianshu Wang
[not found] <firstname.lastname@example.org>
2022-02-08 19:02 ` [PATCH] lisp/org-capture.el: Add hook & hook options to org-capture (Valentin Herrmann) No Wayman
2022-02-09 4:10 ` Ihor Radchenko
2022-02-09 7:11 ` No Wayman
2022-03-20 10:43 ` Ihor Radchenko
2022-02-10 19:32 ` Greg Minshall
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).