From: Eli Zaretskii <eliz@gnu.org>
To: ashish.is@lostca.se (Ashish SHUKLA)
Cc: 13864@debbugs.gnu.org
Subject: bug#13864: 24.3.50; emacsclient -t loops when connected to emacs server running in X11
Date: Wed, 06 Mar 2013 23:00:18 +0200 [thread overview]
Message-ID: <83ppzc1bx9.fsf@gnu.org> (raw)
In-Reply-To: <868v60743o.fsf@chateau.d.if>
> From: ashish.is@lostca.se (Ashish SHUKLA)
> Cc: 13864@debbugs.gnu.org
> Date: Thu, 07 Mar 2013 00:22:43 +0530
>
> Output with 'emacs -Q' was more frequent, whereas output with 'emacs -Q -nw'
> only printed when I pressed some key into the 'emacsclient' xterm window.
So with "emacs -Q", you saw update_frame_1 being constantly called all
the time, even if you didn't press any key after "C-x C-f", is that
right?
If so, please add "bt" to the breakpoint commands, so that we see who
is calling update_frame_1.
next prev parent reply other threads:[~2013-03-06 21:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 19:19 bug#13864: 24.3.50; emacsclient -t loops when connected to emacs server running in X11 Ashish SHUKLA
2013-03-04 17:50 ` Eli Zaretskii
2013-03-04 19:13 ` Ashish SHUKLA
2013-03-04 20:22 ` Eli Zaretskii
2013-03-05 0:26 ` Ashish SHUKLA
2013-03-06 17:07 ` Eli Zaretskii
2013-03-06 18:52 ` Ashish SHUKLA
2013-03-06 21:00 ` Eli Zaretskii [this message]
2013-03-07 1:43 ` Ashish SHUKLA
2013-03-07 6:55 ` Eli Zaretskii
2013-03-07 7:38 ` Ashish SHUKLA
2013-03-07 9:16 ` Eli Zaretskii
2013-03-07 10:19 ` Ashish SHUKLA
2013-03-07 12:48 ` Eli Zaretskii
2013-03-08 10:08 ` Ashish SHUKLA
2013-03-08 15:58 ` Eli Zaretskii
2013-03-13 9:00 ` Ashish SHUKLA
2013-03-15 9:39 ` Eli Zaretskii
2013-03-22 12:44 ` Ashish SHUKLA
2013-03-24 19:54 ` Eli Zaretskii
2013-03-25 9:28 ` Ashish SHUKLA
2013-03-25 10:56 ` Eli Zaretskii
2013-04-01 16:45 ` Ashish SHUKLA
2013-04-02 17:10 ` Eli Zaretskii
2013-04-10 9:06 ` Ashish SHUKLA
2013-04-10 15:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ppzc1bx9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13864@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
/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.