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: Fri, 11 Sep 2015 09:47:59 -0700 Message-ID: References: <83fv2o7rtp.fsf@gnu.org> <8337yo7mdo.fsf@gnu.org> <83d1xq5m8f.fsf@gnu.org> <83twr23yef.fsf@gnu.org> <83egi54dt5.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 1441990091 16983 80.91.229.3 (11 Sep 2015 16:48:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 11 Sep 2015 16:48:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 11 18:48:10 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 1ZaRUd-0006CH-Id for ged-emacs-devel@m.gmane.org; Fri, 11 Sep 2015 18:48:07 +0200 Original-Received: from localhost ([::1]:57463 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZaRUc-00025U-RF for ged-emacs-devel@m.gmane.org; Fri, 11 Sep 2015 12:48:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44652) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZaRUZ-00023f-Dm for emacs-devel@gnu.org; Fri, 11 Sep 2015 12:48:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZaRUY-00020I-Ez for emacs-devel@gnu.org; Fri, 11 Sep 2015 12:48:03 -0400 Original-Received: from mail-qg0-x22c.google.com ([2607:f8b0:400d:c04::22c]:36485) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZaRUW-0001zg-Ut; Fri, 11 Sep 2015 12:48:01 -0400 Original-Received: by qgx61 with SMTP id 61so67349810qgx.3; Fri, 11 Sep 2015 09:48:00 -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=j7GorA3+/HBHrgyRAs+y5tg/vJQd2dteyP2Qb7pHsLw=; b=TgS6RN931rqTbzVakWqbXVwO0wVAL1xT9IQUlvYZbmXb05Iv2SoKxMS+E8w7udf14L 59EG/61ratS5uNjipScJz6QUUjwTZZnQoJlPFfLdflSrU04j7LTLAsrXPkZK3pnb+x8A u4TO8zavrAQbVUEaKcCuXLAlpNWExLz0mwnTUldXYVyolOWQG0PNw0jO230O2bEQ40qF v3lV+r/wZ4GiBFpLbcmxWZ662PJkW1Xqx4NxrNjaZUoCZzhwkBQxBgIrvQXe5vWkcrh7 PhUdM68nB4GGysvUyhgyssTP56Z3+QU7O3vkQPbUozYofHHu5kFWFffstsIfi+JnXvDN yiXw== X-Received: by 10.140.94.111 with SMTP id f102mr63933916qge.102.1441990080072; Fri, 11 Sep 2015 09:48:00 -0700 (PDT) Original-Received: by 10.55.100.135 with HTTP; Fri, 11 Sep 2015 09:47:59 -0700 (PDT) In-Reply-To: <83egi54dt5.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::22c 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:189842 Archived-At: >> Do you have a way to try this with a development snapshot of Emacs 25? > I'll give this a shot and report if I encounter the issue again. Thanks.1 After some hours of usage today, the issue was reproduced with a recent git checkout of Emacs: "M-x version RET" GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6) of 2015-09-10 git hash: 8aa0386420f9d982b99568f27a5953dfc737640e > One other thing to try is "emacsclient -t", i.e. a text-mode frame. > Does that have the same problem, or does it display buffers as > expected? I played around with this and found some interesting notes. 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. If it helps, I execute mercurial commands from gnome-terminal and not from within Emacs. Sometimes mercurial require an editor. My "~/.hgrc" has the editor configured to "emacsclient -c". I'm not sure if the fact that this issue only occurs from mercurial is significant or merely a coincidence as other than mercurial new emacsclients are rarely invoked. 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. Thanks for the help! If there is any additional information I can provide to help debug this issue, please let me know. Cheers, Jon