GNU bug report logs -
#37257
failure of emacsclient ... --alternate-editor="emacs --eval"
Previous Next
Reported by: Campbell Barton <ideasman42 <at> gmail.com>
Date: Sun, 1 Sep 2019 16:23:02 UTC
Severity: normal
Tags: fixed
Found in version 27.0.50
Fixed in version 27.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On 2019-09-15 06:34, Lars Ingebrigtsen wrote:
> , I guess we should just revert the patch -- I don't see any obvious
> way to determine whether --alternate-editor is Emacs (which will then
> understand the rest of the parameters) or something else (which will
> then not). So leaving it the way it was is best.
I'm not sure what the best solution is here, it's just I had something
that worked and now I can't get emacs27 to work usefully in the same way.
It should be possible to run the code in the client or a new instance,
but I didn't manage to get this working.
CODE='(progn (message "HELLO WOLD"))'
emacsclient --eval "$CODE" --alternate-editor "emacs --eval '$CODE'"
Instead of starting a new emacs and printing HELLO WOLD,
it reports:
emacsclient: error executing alternate editor "emacs --eval '(progn
(message "HELLO WORLD"))'"
[emacsclient_or_emacs_with_file.sh (application/x-shellscript, attachment)]
This bug report was last modified 5 years and 250 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.