From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Campbell Barton <ideasman42@gmail.com>, 37257@debbugs.gnu.org
Subject: bug#37257: failure of emacsclient ... --alternate-editor="emacs --eval"
Date: Sat, 14 Sep 2019 14:15:37 +0200 [thread overview]
Message-ID: <87impv845y.fsf@gnus.org> (raw)
In-Reply-To: <42d7bbd5-cde9-e4ca-07f2-486eaff18dbc@cs.ucla.edu> (Paul Eggert's message of "Thu, 5 Sep 2019 14:52:51 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Lars, the commit in question is the following, so could you please
> look into Bug#37257? Thanks.
>
> commit 6fe661342a24edcaea255c3ba9a37613031554da
> Author: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu Jun 27 20:59:50 2019 +0200
>
> emacsclient: ignore --eval parameters when starting alternate editor
>
> * lib-src/emacsclient.c (fail): If the user said --eval, don't
> pass those arguments to the alternate editor as file names.
> Suggested by a patch from Scott Turner (bug#11474).
The test case here is:
emacsclient --eval '(progn (find-file "some_file.txt") (goto-line 1)
(back-to-indentation) (recenter) "")' --no-wait
--alternate-editor="emacs --eval"
So the alternate editor is Emacs itself.
Hm. I guess just reverting the change in question would fix this
regressions, but this is a rather strange use case. What's the point of
specifying Emacs as the alternate editor?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-14 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 16:21 bug#37257: 27.0.50; Campbell Barton
2019-09-05 21:52 ` bug#37257: failure of emacsclient ... --alternate-editor="emacs --eval" Paul Eggert
2019-09-14 12:15 ` Lars Ingebrigtsen [this message]
2019-09-14 18:01 ` Paul Eggert
2019-09-14 20:34 ` Lars Ingebrigtsen
2019-09-14 20:45 ` Cambell Barton
2019-09-15 12:13 ` Lars Ingebrigtsen
2019-09-15 17:52 ` Cambell Barton
2019-09-16 12:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87impv845y.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37257@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=ideasman42@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.