all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: bojohan@gnu.org, emacs-devel@gnu.org
Subject: Re: Is emacsclient --eval broken?
Date: Sat, 06 Aug 2016 18:30:20 +0300	[thread overview]
Message-ID: <83h9axkj8z.fsf@gnu.org> (raw)
In-Reply-To: <c8a9d222-e4db-3ad6-f8b7-461ec3eefee7@gmail.com> (message from Clément Pit--Claudel on Sat, 6 Aug 2016 11:23:35 -0400)

> Cc: emacs-devel@gnu.org
> From: Clément Pit--Claudel <clement.pit@gmail.com>
> Date: Sat, 6 Aug 2016 11:23:35 -0400
> 
> >> $ git grep 'Unknown message'
> >> lib-src/emacsclient.c:        printf ("*ERROR*: Unknown message: %s\n", p);
> > 
> > Thanks.  What is the message received from the server that triggers
> > this?
> 
> The client print 
> 
>     *ERROR*: Unknown message: E EE EEEEE\n"
> 
> Is that the information you were looking for?

No, I wanted to know what came in from the server that caused this
message.  See the code in emacsclient.c that follows the comment which
says "Wait for an answer."  There must be something that the client
cannot interpret, or maybe we are not prepared to deal with strings
that span more than one packet returned by recv?

IOW, some more debugging is in order.

Thanks.



  reply	other threads:[~2016-08-06 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 15:32 Is emacsclient --eval broken? Clément Pit--Claudel
2016-08-06 10:09 ` Eli Zaretskii
2016-08-06 11:17   ` Johan Bockgård
2016-08-06 11:21     ` Eli Zaretskii
2016-08-06 15:23       ` Clément Pit--Claudel
2016-08-06 15:30         ` Eli Zaretskii [this message]
2016-08-15 19:08           ` Johan Bockgård
2016-08-18 19:39             ` Johan Bockgård
2016-08-19  7:04               ` Eli Zaretskii
2016-08-22 15:25               ` Clément Pit--Claudel

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=83h9axkj8z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bojohan@gnu.org \
    --cc=clement.pit@gmail.com \
    --cc=emacs-devel@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.
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.