From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jon Dufresne Newsgroups: gmane.emacs.devel Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes Date: Tue, 22 Sep 2015 17:51:45 -0700 Message-ID: References: <83fv2o7rtp.fsf@gnu.org> <8337yo7mdo.fsf@gnu.org> <83d1xq5m8f.fsf@gnu.org> <83twr23yef.fsf@gnu.org> <83egi54dt5.fsf@gnu.org> <83egi19usm.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1442969513 15256 80.91.229.3 (23 Sep 2015 00:51:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 23 Sep 2015 00:51:53 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 23 02:51:53 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZeYHo-0003j3-9i for ged-emacs-devel@m.gmane.org; Wed, 23 Sep 2015 02:51:52 +0200 Original-Received: from localhost ([::1]:44052 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZeYHn-0004pV-OP for ged-emacs-devel@m.gmane.org; Tue, 22 Sep 2015 20:51:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58686) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZeYHk-0004pQ-Sl for emacs-devel@gnu.org; Tue, 22 Sep 2015 20:51:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZeYHk-00041p-0l for emacs-devel@gnu.org; Tue, 22 Sep 2015 20:51:48 -0400 Original-Received: from mail-qg0-x235.google.com ([2607:f8b0:400d:c04::235]:36515) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZeYHi-00041B-Fl; Tue, 22 Sep 2015 20:51:46 -0400 Original-Received: by qgx61 with SMTP id 61so8465158qgx.3; Tue, 22 Sep 2015 17:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IeC75o9YV9oZFXP5MTp9zSnGsPwqPFO5+afDAD50Ls4=; b=bjjdF42CtrEdxik9fh8sZA1TwrpENcwPiAAWUubMHAJnNwtm2Y9kxLxINVkGj+aL6w WaYUIH/DEbT89CHR6T48fMrlLahIJ9mmiNYVXBn3ORpBc+/0+Oo4udmr+s93umDS50cD 8QnnL3ATBOKOpaFQZ6Qi6crcxujsdAgjKpgSPU6qbqCAa7HxLMG5rLz6cQl9yDOxynUx sWfTJayPCksTMc8l+oehxuCuyKHvj9eBTfR1cX+gjvCnuuuUwgsao7z7JGxdQGkCUTbG dWW8u020upn0+V0CkMEQBhn9EcGmRXnyqr1nEGlforpNgzi+PlLCJ7CYiFlS0fmImBWb SIVQ== X-Received: by 10.140.22.48 with SMTP id 45mr33745612qgm.23.1442969505851; Tue, 22 Sep 2015 17:51:45 -0700 (PDT) Original-Received: by 10.55.100.135 with HTTP; Tue, 22 Sep 2015 17:51:45 -0700 (PDT) In-Reply-To: <83egi19usm.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c04::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:190258 Archived-At: On Mon, Sep 14, 2015 at 3:09 AM, Eli Zaretskii wrote: >> Once the issue arises, if I execute "emacsclient -c", "emacsclient -c >> filename.txt", "emacsclient -t", or "emacsclient -t filename.txt" from >> a new gnome-terminal the frame opens and display correctly as >> expected. It appears that only the frames created by mercurial >> commands regularly have the issue, and then only sometimes. > > I guess the question is now what does Mercurial do, exactly, to invoke > emacsclient. Can you look at the command line Mercurial passes to it, > for example? Perhaps also log the communications between emacsclient > and the server on the Emacs side, and see what is passed there. > > The screenshot you posted seems like the frame was never created > completely, so Emacs doesn't think it should be displaying any text > yet. I wonder why that happens. > >> If I execute the "emacsclient -c" from a separate terminal (as >> mentioned above), then retry the mercurial command, the next frame >> displays correctly as expected. It seems this sequence somehow gets >> around the issue. > > We need to figure out what kind of "issue" this works around. I'm at a loss on how to continue diagnosing this issue. I continue to hit the problem, even with the newer Emacs. Luckily less frequently than before and it is now easier to resume normal usage, but enough that it interrupts my flow. Any thoughts on how to possibly gather more useful information? Thanks, Jon