unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Zhang Haijun <ccsmile2008@outlook.com>
To: martin rudalics <rudalics@gmx.at>
Cc: "34614@debbugs.gnu.org" <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: Sat, 23 Feb 2019 02:01:52 +0000	[thread overview]
Message-ID: <PS1PR06MB275982F1DE1F946142D77AC8A8780@PS1PR06MB2759.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <5C7043C9.2090809@gmx.at>



> 在 2019年2月23日,上午2:47,martin rudalics <rudalics@gmx.at> 写道:
> 
> > Steps to reproduce the bug:
> > 1. start emacs with emacs -Q
> > 2. M-x global-auto-revert-mode
> > 3. Open a test file with emacs
> > 4. M-x find-file, it will prompt and read file name
> > 5.  modify the test file with other tool and save the file
> > 6. emacs will revert the file and print a message like "Reverting buffer xxx”.
> > 7. the find-file ui will not come back.
> 
> It comes back here with the next character I type.

Same here. Blind typing only for next one char.

> I have no idea how
> to fix this.  At least sitting for 'minibuffer-message-timeout' in
> 'auto-revert-handler' when the minibuffer depth is greater zero won't
> cut it - the message gets cleared immediately and minibuffer contents
> are restored.  Some 'sit-for' snafu, I suppose.
> 
> martin
> 

According the doc string of minibuffer-message-timeout, the input UI will be restored after the timeout.

If I resize the frame, the input UI is restored. Maybe there just needs a redisplay after the timeout?



  parent reply	other threads:[~2019-02-23  2:01 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
2019-02-25 10:11                                 ` martin rudalics
     [not found]     ` <5C7043C9.2090809@gmx.at>
2019-02-23  2:01       ` Zhang Haijun [this message]
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=PS1PR06MB275982F1DE1F946142D77AC8A8780@PS1PR06MB2759.apcprd06.prod.outlook.com \
    --to=ccsmile2008@outlook.com \
    --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).