From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <m.kupfer@acm.org>
Cc: jon.dufresne@gmail.com, emacs-devel@gnu.org
Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes
Date: Mon, 28 Sep 2015 09:39:52 +0300 [thread overview]
Message-ID: <83si5zdp3b.fsf@gnu.org> (raw)
In-Reply-To: <17620.1443392512@allegro.localdomain>
> From: Mike Kupfer <m.kupfer@acm.org>
> cc: Jon Dufresne <jon.dufresne@gmail.com>, emacs-devel@gnu.org
> Date: Sun, 27 Sep 2015 15:21:52 -0700
>
> If it happens again, I can certainly tell you how emacsclient got
> invoked. But I could use a clue about how to log communication between
> emacsclient and the server.
Set the variable server-log to a non-nil value (in your .emacs), then
look at the contents of the buffer named " *server*" after each
invocation of emacsclient.
next prev parent reply other threads:[~2015-09-28 6:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 13:00 Need help debugging Emacs: emacsclient will not draw its contents sometimes Jon Dufresne
2015-09-08 13:28 ` Tassilo Horn
2015-09-08 17:18 ` Eli Zaretskii
2015-09-08 18:58 ` Jon Dufresne
2015-09-08 19:16 ` Eli Zaretskii
2015-09-09 22:29 ` Jon Dufresne
2015-09-10 15:26 ` Eli Zaretskii
2015-09-10 18:20 ` Jon Dufresne
2015-09-10 18:46 ` Eli Zaretskii
2015-09-10 18:52 ` Jon Dufresne
2015-09-11 7:26 ` Eli Zaretskii
2015-09-11 16:47 ` Jon Dufresne
2015-09-14 10:09 ` Eli Zaretskii
2015-09-23 0:51 ` Jon Dufresne
2015-09-23 6:45 ` Eli Zaretskii
2015-09-27 22:21 ` Mike Kupfer
2015-09-28 6:39 ` Eli Zaretskii [this message]
2016-02-16 1:07 ` Mike Kupfer
2016-02-16 16:26 ` Eli Zaretskii
2016-02-16 16:38 ` Kaushal Modi
2016-02-16 16:44 ` Eli Zaretskii
2016-02-16 17:06 ` Kaushal Modi
2016-02-17 2:05 ` Mike Kupfer
2016-02-17 20:02 ` Eli Zaretskii
2016-02-18 5:01 ` Mike Kupfer
2016-02-20 11:24 ` Eli Zaretskii
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=83si5zdp3b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jon.dufresne@gmail.com \
--cc=m.kupfer@acm.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).