From: Eli Zaretskii <eliz@gnu.org>
To: mvoteiza@udel.edu
Cc: 18112@debbugs.gnu.org
Subject: bug#18112: 24.4.50; emacs --daemon infinite loop in find_interval
Date: Sat, 26 Jul 2014 12:33:30 +0300 [thread overview]
Message-ID: <83egx8ihw5.fsf@gnu.org> (raw)
In-Reply-To: <83fvhoij80.fsf@gnu.org>
> Date: Sat, 26 Jul 2014 12:04:47 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 18112@debbugs.gnu.org
>
> > Date: Sat, 26 Jul 2014 10:55:11 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: 18112@debbugs.gnu.org
> >
> > The loop is in redisplay, and the reason seems to be that get_tty_size
> > returns incorrect size after the second tmux pane is closed with ^D.
> > We get one line more than tmux leaves us (after usurping 1 line for
> > its status line).
>
> Actually, I think I was wrong (I forgot to count the line used for the
> menu bar). So the reason is probably elsewhere...
Ok, my original analysis was based on a mistake. Moreover, tmux is
not really related to the problem at all, and neither is "C-x 3".
Here's a simpler way to reproduce the problem:
Open a terminal emulator (e.g., xterm) window, and in that window:
emacs -Q --daemon
emacsclient -t
Now open another terminal emulator window, and make it have a smaller
size. Then, in that window:
emacsclient -t
C-x C-c
Now go back to the first xterm window and resize it (e.g., with a
mouse). Emacs is now stuck in an infloop.
So the important players here are (1) a frame on another tty that has
a different size, and (2) resizing the frame after deleting another
frame on a different tty.
next prev parent reply other threads:[~2014-07-26 9:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 23:08 bug#18112: 24.4.50; emacs --daemon infinite loop in find_interval Mark Oteiza
2014-07-26 6:42 ` Eli Zaretskii
2014-07-26 7:55 ` Eli Zaretskii
2014-07-26 8:06 ` Andreas Schwab
2014-07-26 8:15 ` Andreas Schwab
2014-07-26 8:22 ` Eli Zaretskii
2014-07-26 9:04 ` Eli Zaretskii
2014-07-26 9:33 ` Eli Zaretskii [this message]
2014-07-27 13:05 ` Eli Zaretskii
2014-07-27 13:35 ` martin rudalics
2014-07-27 14:55 ` Eli Zaretskii
2014-07-27 18:15 ` martin rudalics
2014-08-08 10:10 ` martin rudalics
2014-08-08 10:40 ` Eli Zaretskii
2014-08-09 11:14 ` martin rudalics
2014-08-09 15:37 ` Eli Zaretskii
2014-08-09 15:56 ` martin rudalics
2014-08-09 16:29 ` Eli Zaretskii
2014-08-10 10:42 ` martin rudalics
2014-08-10 14:04 ` Eli Zaretskii
2014-07-26 9:17 ` Andreas Schwab
2014-07-26 9:44 ` Andreas Schwab
2014-07-26 11:07 ` Eli Zaretskii
2014-07-26 11:27 ` Andreas Schwab
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83egx8ihw5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18112@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).