From: VanL <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: local emacs and a remote emacs daemon
Date: Thu, 29 Aug 2019 20:04:27 +1000 [thread overview]
Message-ID: <m27e6wgudw.fsf@wakeman.localnet> (raw)
In-Reply-To: 838ssuung0.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> The protocol between emacsclient and Emacs is in emacsclient.c and in
> server.el. in the latter you will see the commands that the client
> sends and how each command is executed; you can then look up those
> commands in the client source and see when each command is sent.
A problem that needs fixing is EmacsMac's `emacsclient -t' which doesn't work.
--
© 2019 VanL
gpg using EEF2 37E9 3840 0D5D 9183 251E 9830 384E 9683 B835
'If the bug bites don't fight it.' - Nancy S. Steinhardt
next prev parent reply other threads:[~2019-08-29 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 13:13 local emacs and a remote emacs daemon Perry Smith
2019-07-19 14:08 ` Eli Zaretskii
2019-08-29 10:04 ` VanL [this message]
2019-08-29 12:33 ` Eli Zaretskii
2019-08-30 19:24 ` 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
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=m27e6wgudw.fsf@wakeman.localnet \
--to=van@scratch.space \
--cc=help-gnu-emacs@gnu.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.
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).