From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: storm@cua.dk, monnier@iro.umontreal.ca, 21747@debbugs.gnu.org,
bruce.connor.am@gmail.com
Subject: bug#21747: 25.0.50; while-no-input breaks kbd event handling when called from post-command-hook
Date: Sat, 24 Oct 2015 15:45:53 +0300 [thread overview]
Message-ID: <83si50wi2m.fsf@gnu.org> (raw)
In-Reply-To: <874mhg1n25.fsf@gnu.org>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: bruce.connor.am@gmail.com, monnier@iro.umontreal.ca, storm@cua.dk, 21747@debbugs.gnu.org
> Date: Sat, 24 Oct 2015 14:13:54 +0200
>
> Actually, the `post-command-hook' function in question
> (aggressive-indent--indent-if-changed) is not so overly expensive. At
> least I have validated that it has finished running I type the next key,
> thus the abort-on-input case doesn't even occur.
>
> My recipe for reproduction is
>
> 1. emacs -Q
> 2. M-x package-initialize
> 3. M-x global-aggressive-indent-mode
> 4. C-x C-f ~/test.sh
> 5. type the keyword if where the i is displayed immediately
> and the display of f is delayed
>
> This does only occur for sh-mode keywords like if, while, etc. where the
> delaying starts with after entering the last char of the keyword. Also,
> I can reproduce that problem only if test.sh doesn't exist.
I don't understand: are you saying that the post-command-hook finished
its job, and yet redisplay is not entered?
> Or well, I just tried what happens when I replace the `while-no-input'
> with a `progn'. Then Emacs goes into some infloop. Attaching with gdb
> shows:
There's a procedure in etc/DEBUG to determine which call-stack frame
infloops, please use it and tell what you found.
Thanks.
next prev parent reply other threads:[~2015-10-24 12:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 7:42 bug#21747: 25.0.50; while-no-input breaks kbd event handling when called from post-command-hook Tassilo Horn
2015-10-24 8:02 ` Eli Zaretskii
2015-10-24 8:53 ` Tassilo Horn
2015-10-24 9:14 ` Eli Zaretskii
2015-10-24 9:49 ` Tassilo Horn
2015-10-24 10:30 ` Artur Malabarba
2015-10-24 10:52 ` Eli Zaretskii
2015-10-24 12:13 ` Tassilo Horn
2015-10-24 12:45 ` Eli Zaretskii [this message]
2015-10-24 13:30 ` Tassilo Horn
2015-10-24 13:57 ` Artur Malabarba
2015-10-24 14:06 ` Eli Zaretskii
2015-10-24 14:05 ` Eli Zaretskii
2015-10-25 7:19 ` Tassilo Horn
2015-10-25 8:10 ` Tassilo Horn
2015-10-25 9:25 ` Tassilo Horn
2015-10-25 18:45 ` Eli Zaretskii
2015-10-25 18:49 ` Tassilo Horn
2015-10-25 20:10 ` Stefan Monnier
2015-10-26 6:57 ` Tassilo Horn
2015-10-25 18:43 ` Eli Zaretskii
2015-10-24 12:46 ` Tassilo Horn
2015-10-25 14:43 ` Artur Malabarba
2015-10-25 18:50 ` Eli Zaretskii
2015-10-26 0:27 ` Artur Malabarba
2015-10-26 3:32 ` Eli Zaretskii
2015-10-26 13:43 ` Tassilo Horn
2015-10-24 10:35 ` 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=83si50wi2m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21747@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=storm@cua.dk \
--cc=tsdh@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.