From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eliza Velasquez <exv@google.com>
Cc: 25547@debbugs.gnu.org, Alex Hutcheson <alexhutcheson@google.com>
Subject: bug#25547: 25.1.91; emacsclient -c creates frames on the wrong display
Date: Wed, 04 Nov 2020 23:44:01 -0500 [thread overview]
Message-ID: <jwvk0v0mnce.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAK1djOpHs8Em80PeqzHMjwWAoVovC9tj5yUK-m8AxC287zTQLg@mail.gmail.com> (Eliza Velasquez's message of "Wed, 4 Nov 2020 18:00:14 -0800")
> It looks like I was able to make progress today. Just by modifying
> server.el, I've gotten `emacsclient -ce "..."` to create a new frame
> based on the currently selected frame's terminal when called in a dumb
> terminal.
Great!
> Unfortunately, the command for calling ediff is still very
> unpleasant:
>
> emacsclient -ucF "((delete-frame-on-ediff-quit . t))" \
> -e "(ediff-merge-with-ancestor \"${local}\" \"${other}\" \"${base}\"
> nil \"${output}\")" \
> -e "(add-hook 'ediff-quit-hook (lambda () (when (frame-parameter nil
> 'delete-frame-on-ediff-quit) (delete-frame))))"
I think the problem is that emacsclient lacks the equivalent of `-f`,
i.e. calling a particular ELisp function where the remaining arguments
can be consumed by that function. That would solve the problem of
quoting (your above script will stumble when encountering
a file name with quotes in it or with a final backslash).
> So perhaps introducing a wrapper script for ediff merges would still be useful.
We should be able to add a convenience `batch-ediff-merge-with-ancestor`.
Bonus points if you manage to make it work with `emacs --batch -f` as
well as with `emacsclient --<newflag>`.
Stefan
next prev parent reply other threads:[~2020-11-05 4:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 18:09 bug#25547: 25.1.91; emacsclient -c creates frames on the wrong display Alex Hutcheson
2020-11-02 22:37 ` Stefan Monnier
[not found] ` <CAK1djOorpaeoMU-gtd+hQnWWK8tOaER6OPYgukYrn=V1cDh+aQ@mail.gmail.com>
[not found] ` <jwvsg9rtghs.fsf-monnier+emacs@gnu.org>
2020-11-03 18:36 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-05 2:00 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-05 4:44 ` Stefan Monnier [this message]
2020-11-05 23:41 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 0:55 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 5:39 ` Eli Zaretskii
2020-11-06 19:14 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 22:07 ` Stefan Monnier
2020-11-07 8:04 ` Eli Zaretskii
2020-11-10 0:14 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-11 3:14 ` Stefan Monnier
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=jwvk0v0mnce.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=25547@debbugs.gnu.org \
--cc=alexhutcheson@google.com \
--cc=exv@google.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.