From: Eli Zaretskii <eliz@gnu.org>
To: michael_heerdegen@web.de
Cc: 34179@debbugs.gnu.org
Subject: bug#34179: 27.0.50; message hangs when buffer with process visible
Date: Thu, 24 Jan 2019 21:49:58 +0200 [thread overview]
Message-ID: <83bm457s49.fsf@gnu.org> (raw)
In-Reply-To: <83ef917tf7.fsf@gnu.org> (message from Eli Zaretskii on Thu, 24 Jan 2019 21:21:48 +0200)
> Date: Thu, 24 Jan 2019 21:21:48 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 34179@debbugs.gnu.org
>
> Here's the Lisp backtrace:
>
> "select-window" (0x82a508)
> "window-max-chars-per-line" (0x82aae0)
> "window-adjust-process-window-size" (0x82b0a0)
> "window-adjust-process-window-size-smallest" (0x82b618)
> "window--adjust-process-windows" (0x82bbc0)
> "redisplay_internal (C function)" (0x0)
> "message" (0x82cdb0)
> "progn" (0x82cff8)
> "if" (0x82d198)
> "let*" (0x82d3c8)
> "catch" (0x82d608)
> "fracy-display-frame-list" (0x82d7c0)
> "if" (0x82dac8)
> "fracy-flash-window" (0x82dc80)
> "let" (0x82e018)
> "ad-Advice-handle-switch-frame" (0x82e4a0)
> "apply" (0x82e498)
> "handle-switch-frame" (0x82ebe0)
> "funcall-interactively" (0x82ebd8)
> "call-interactively" (0x82f030)
> "command-execute" (0x82f628)
>
> The C portion of the backtrace below selec t-window is this:
>
> #0 redisplay_other_windows () at xdisp.c:597
> #1 0x010aa09e in select_window (window=XIL(0xa000000006919aa0),
> norecord=XIL(0x3d36a14), inhibit_point_swap=false) at window.c:540
> #2 0x010aa62a in Fselect_window (window=XIL(0xa000000006919aa0),
> norecord=XIL(0x3d36a14)) at window.c:628
To clarify: these backtraces show where windows_or_buffers_changed is
being set to the value of 2, which causes us to retry redisplay. It
is a direct consequence of the fact that window-max-chars-per-line
calls select-window.
next prev parent reply other threads:[~2019-01-24 19:49 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:10 bug#34179: 27.0.50; message hangs when buffer with process visible Michael Heerdegen
2019-01-23 16:29 ` Eli Zaretskii
2019-01-24 13:19 ` Michael Heerdegen
2019-01-24 13:35 ` Michael Heerdegen
2019-01-24 14:39 ` Eli Zaretskii
2019-01-24 14:58 ` Michael Heerdegen
2019-01-24 15:04 ` Michael Heerdegen
2019-01-24 15:25 ` Michael Heerdegen
2019-01-24 15:36 ` Michael Heerdegen
2019-01-24 16:05 ` martin rudalics
2019-01-24 18:22 ` Michael Heerdegen
2019-01-24 18:33 ` martin rudalics
2019-01-24 18:36 ` Eli Zaretskii
2019-01-24 18:51 ` martin rudalics
2019-01-24 18:59 ` Eli Zaretskii
2019-01-24 19:20 ` Michael Heerdegen
2019-01-24 18:55 ` Michael Heerdegen
2019-01-24 18:47 ` Michael Heerdegen
2019-01-24 19:21 ` Eli Zaretskii
2019-01-24 19:49 ` Eli Zaretskii [this message]
2019-01-25 9:44 ` martin rudalics
2019-01-25 10:15 ` Eli Zaretskii
2019-01-25 10:36 ` martin rudalics
2019-01-25 13:32 ` Eli Zaretskii
2019-01-25 16:51 ` martin rudalics
2019-01-25 17:22 ` martin rudalics
2019-01-26 12:58 ` Michael Heerdegen
2019-01-26 15:09 ` martin rudalics
2019-01-26 18:48 ` martin rudalics
2019-01-27 14:22 ` Michael Heerdegen
2019-01-28 18:38 ` martin rudalics
2019-01-30 22:29 ` Michael Heerdegen
2019-01-31 8:32 ` martin rudalics
2019-01-31 14:06 ` Eli Zaretskii
2019-01-31 18:44 ` martin rudalics
2019-01-31 20:10 ` Eli Zaretskii
2019-02-01 9:04 ` martin rudalics
2019-01-31 14:44 ` Michael Heerdegen
2019-02-02 9:28 ` martin rudalics
2019-02-04 23:35 ` Michael Heerdegen
2019-02-19 8:39 ` martin rudalics
2019-01-25 18:31 ` Eli Zaretskii
2019-01-25 18:54 ` martin rudalics
2019-01-25 19:48 ` Eli Zaretskii
2019-01-24 15:46 ` martin rudalics
2019-01-24 14:32 ` Eli Zaretskii
2019-01-24 14:41 ` Michael Heerdegen
2019-01-24 14:49 ` Michael Heerdegen
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=83bm457s49.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34179@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.