From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs enters in a loop with emacsclient -t Date: Sun, 03 Mar 2013 18:02:13 +0200 Message-ID: <83sj4ctqt6.fsf@gnu.org> References: <86ehfxrurw.fsf@chateau.d.if> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1362326549 9115 80.91.229.3 (3 Mar 2013 16:02:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Mar 2013 16:02:29 +0000 (UTC) Cc: emacs-devel@gnu.org To: wahjava.ml@gmail.com (Ashish SHUKLA) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 03 17:02:53 2013 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 1UCBND-0003xj-Rx for ged-emacs-devel@m.gmane.org; Sun, 03 Mar 2013 17:02:52 +0100 Original-Received: from localhost ([::1]:38560 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCBMs-0002ZZ-HC for ged-emacs-devel@m.gmane.org; Sun, 03 Mar 2013 11:02:30 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:53181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCBMp-0002ZT-Iv for emacs-devel@gnu.org; Sun, 03 Mar 2013 11:02:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UCBMo-00070I-A7 for emacs-devel@gnu.org; Sun, 03 Mar 2013 11:02:27 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:57856) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCBMo-000705-1P for emacs-devel@gnu.org; Sun, 03 Mar 2013 11:02:26 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MJ300500DRQLI00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Sun, 03 Mar 2013 18:02:24 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MJ3005I5DVZ8D80@a-mtaout22.012.net.il>; Sun, 03 Mar 2013 18:02:23 +0200 (IST) In-reply-to: <86ehfxrurw.fsf@chateau.d.if> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 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:157495 Archived-At: > From: wahjava.ml@gmail.com (Ashish SHUKLA) > Date: Sun, 03 Mar 2013 09:37:15 +0530 > > I'm running Emacs trunk r111924 on FreeBSD 9.1-RC3 (amd64). When I connect to > Emacs session using 'emacsclient -t', I noticed flicker in xterm. I truss-ed > Emacs process, and it seems like it's sending same stuff in a loop which seems > to be causing what I noticed: Thanks. First, please post this to bug-gnu-emacs@gnu.org, using the Emacs command report-emacs-bug. That way, this issue and all the ensuing discussions are recorded and tracked by the Emacs bug tracker. And second, please accompany such data with snapshots of the Emacs frame and description of what was displayed and which mode(s) were in effect in the displayed windows, when you collected the truss data. Without this information, the truss data is useless, as it doesn't even say enough to understand which part(s) of the display are being redrawn and cause the flicker. > write(23,"\^[[50d\^[[38;5;252m\^[[48;5;17m"...,330) = 330 (0x14a) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23,"_error\^[[39;49m\^[[38;5;252m\^["...,202) = 202 (0xca) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23,"[39;49m\^[[38;5;252m\^[[48;5;17m"...,143) = 143 (0x8f) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23,"49m\^[[38;5;84m\^[[48;5;17mservn"...,487) = 487 (0x1e7) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23," "...,258) = 258 (0x102) > write(23,"\n\^[[38;5;252m\^[[48;5;17m h"...,880) = 880 (0x370) > write(23,"\n\^[[38;5;252m\^[[48;5;17m h"...,765) = 765 (0x2fd) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,822) = 822 (0x336) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,957) = 957 (0x3bd) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,153) = 153 (0x99) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,937) = 937 (0x3a9) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,576) = 576 (0x240) See, all I can say given this is that you use xterm-256, and here Emacs is redrawing something like 11 lines with background color 17 and foreground color 252. I see some small parts of text, like "_error" and "servn", but that is not enough to understand what is going on. > write(23,"\^[[50d\^[[38;5;252m\^[[48;5;17m"...,330) = 330 (0x14a) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23,"_error\^[[39;49m\^[[38;5;252m\^["...,202) = 202 (0xca) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23,"[39;49m\^[[38;5;252m\^[[48;5;17m"...,143) = 143 (0x8f) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23,"49m\^[[38;5;84m\^[[48;5;17mservn"...,487) = 487 (0x1e7) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,1024) = 1024 (0x400) > write(23," "...,258) = 258 (0x102) > write(23,"\n\^[[38;5;252m\^[[48;5;17m h"...,880) = 880 (0x370) > write(23,"\n\^[[38;5;252m\^[[48;5;17m h"...,765) = 765 (0x2fd) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,822) = 822 (0x336) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,957) = 957 (0x3bd) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,153) = 153 (0x99) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,937) = 937 (0x3a9) > write(23,"\n\^[[38;5;252m\^[[48;5;17m "...,576) = 576 (0x240) Here the same stuff is being redrawn, some 13 milliseconds after the previous redisplay. That's all I can deduce from this data. Maybe someone else can see what I cannot. > The flicker stops, when I focus the X11 frame, and do some activity there, and > resumes when I focus back to xterm. Was the stuff shown in the X11 frame related in any way to what was shown in the xterm frame? Like the same buffer, perhaps? > I'm wondering if anyone else has noticed it, or know of a fix to the problem. I think we are very far from understanding this problem, let alone find a solution for it. Providing the missing information (as a bug report) would be a good first step forward.