all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: wahjava.ml@gmail.com (Ashish SHUKLA)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs enters in a loop with emacsclient -t
Date: Mon, 04 Mar 2013 03:39:47 +0530	[thread overview]
Message-ID: <86vc98m8yc.fsf@chateau.d.if> (raw)
In-Reply-To: 83sj4ctqt6.fsf@gnu.org

[-- Attachment #1: Type: text/plain, Size: 5447 bytes --]

Hi,

On Sun, 03 Mar 2013 18:02:13 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> 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.

I posted to list via M-x report-emacs-bug few hours ago, but it never showed
up, though it left my MTA.

#v+
Mar  3 19:20:21 arati postfix/smtp[31792]: B2235661: to=<bug-gnu-emacs@gnu.org>, relay=eggs.gnu.org[208.118.235.92]:25, delay=5.7, delays=0.24/0/2.2/3.3, dsn=2.0.0, status=sent (250 OK id=1UCESO-0003OD-Ej)
#v-

Anyways, in the debbug report, I mentioned following steps to reproduce with
emacs -Q:

1. Start Emacs: emacs -Q
2. Start Emacs server: M-x server-start
3. Start emacsclient: emacsclient -t
4. Do C-x C-f, and minibuffer prompt shows up.

And xterm window starts flickering, press C-g and it'll stop.

Now open any file in 'emacsclient', it'll work fine. Focus to X11 frame, and
focus back to xterm running 'emacsclient' session, and press any key. xterm
will start flickering again. Press C-g and it'll stop flickering.

> 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.

Whole of the window frame is being redrawn, from menu-bar to minibuffer. And
this happens irrespective of what modes/buffers are active in tty/X11 frames.

>> 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.

Right.

>> 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?

Replied above.

Also this doesn't happen when emacs is started with '-nw'.

Let me know if you need more information.

Thanks
-- 
Ashish SHUKLA

“If tempted by something that feels "altruistic," examine your motives and root
out that self-deception. Then, if you still want to do it, wallow in it!”
(Robert A. Heinlein, 1973)

Sent from my Emacs

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2013-03-03 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03  4:07 Emacs enters in a loop with emacsclient -t Ashish SHUKLA
2013-03-03 16:02 ` Eli Zaretskii
2013-03-03 22:09   ` Ashish SHUKLA [this message]

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=86vc98m8yc.fsf@chateau.d.if \
    --to=wahjava.ml@gmail.com \
    --cc=eliz@gnu.org \
    --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.