From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 34614@debbugs.gnu.org
Subject: bug#34614: 26.1.92; When reading input in mini-buffer, message to each area overide the input prompt
Date: Sun, 24 Feb 2019 21:02:44 +0200 [thread overview]
Message-ID: <83ef7xnh63.fsf@gnu.org> (raw)
In-Reply-To: <5C72E2EE.3010605@gmx.at> (message from martin rudalics on Sun, 24 Feb 2019 19:31:10 +0100)
> Date: Sun, 24 Feb 2019 19:31:10 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: 34614@debbugs.gnu.org
>
> > Yes, but I asked what kind of input event causes that. Since you
> > didn't type anything at this point, it cannot be keyboard input, so
> > what non-keyboard event did that?
>
> Elementary:
>
> (gdb) p event->kind
> $8 = FILE_NOTIFY_EVENT
That's what I thought. Does it help to explicitly restart sit-for for
the remainder of the time if this event comes in?
> > Anyway, I cannot reproduce anything like that, your change in
> > autorevert-handler works just fine for me on MS-Windows. Did you test
> > in "emacs -Q"?
>
> With emacs -Q and 'global-auto-revert-mode' enabled.
>
> > It might also be important whether autorevert works with file
> > notifications or not.
>
> Does the above show that it does? On Windows XP, if that matters.
Strange, I did the same.
next prev parent reply other threads:[~2019-02-24 19:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 12:17 bug#34614: 26.1.92; When reading input in mini-buffer, message to each area overide the input prompt Zhang Haijun
2019-02-22 13:20 ` Eli Zaretskii
2019-02-22 13:35 ` Zhang Haijun
2019-02-22 15:07 ` martin rudalics
2019-02-22 15:40 ` Zhang Haijun
2019-02-22 21:38 ` martin rudalics
2019-02-23 7:26 ` Eli Zaretskii
2019-02-23 7:54 ` martin rudalics
2019-02-23 8:25 ` Eli Zaretskii
2019-02-23 8:29 ` martin rudalics
2019-02-23 9:31 ` Eli Zaretskii
2019-02-23 9:57 ` martin rudalics
2019-02-23 10:35 ` Eli Zaretskii
2019-02-23 14:02 ` martin rudalics
2019-02-23 16:51 ` Eli Zaretskii
2019-02-24 8:44 ` martin rudalics
2019-02-24 16:11 ` Eli Zaretskii
2019-02-24 18:31 ` martin rudalics
2019-02-24 19:02 ` Eli Zaretskii [this message]
2019-02-25 10:11 ` martin rudalics
[not found] ` <5C7043C9.2090809@gmx.at>
2019-02-23 2:01 ` Zhang Haijun
2019-02-23 2:33 ` Zhang Haijun
2019-02-23 7:53 ` martin rudalics
2019-02-23 8:05 ` Zhang Haijun
2019-02-23 8:29 ` martin rudalics
2019-02-23 8:01 ` Eli Zaretskii
2019-02-23 8:29 ` Zhang Haijun
2019-11-06 22:02 ` Juri Linkov
2019-11-07 14:52 ` HaiJun Zhang
2019-11-07 22:12 ` Juri Linkov
2019-11-08 1:46 ` HaiJun Zhang
2019-11-09 23:05 ` Juri Linkov
2019-11-09 23:38 ` HaiJun Zhang
2019-11-10 21:22 ` Juri Linkov
2019-11-12 0:49 ` HaiJun Zhang
2019-11-12 8:10 ` martin rudalics
2019-11-14 0:44 ` Zhang Haijun
2019-11-12 1:15 ` HaiJun Zhang
2019-11-12 20:53 ` Juri Linkov
2019-11-14 0:46 ` Zhang Haijun
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=83ef7xnh63.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34614@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).