From: Eli Zaretskii <eliz@gnu.org>
To: meedstrom@teknik.io
Cc: 50224@debbugs.gnu.org
Subject: bug#50224: 27.2; auto-save-visited-mode blanks out the echo area after 5 seconds
Date: Fri, 27 Aug 2021 15:39:09 +0300 [thread overview]
Message-ID: <83fsuvqcya.fsf@gnu.org> (raw)
In-Reply-To: <bf0d8c8ff317f5384104bf77a1d4f631@teknik.io> (bug-gnu-emacs@gnu.org)
> Date: Fri, 27 Aug 2021 11:06:53 +0000
> From: meedstrom--- via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> So this has been troubling me for years, I thought it was just a part of
> how Emacs worked. But it cannot be intended. Often there are complex
> prompts that take time to read, such what lsp-mode asks you upon
> visiting a .sh buffer. Then after 5 seconds, the prompt text
> disappears, but the minibuffer is still active and awaiting your reply.
>
> To test it:
>
> - M-x auto-save-visited-mode
> - edit any buffer
> - eval (message "foo")
> - wait 5 secs
>
> You'll see "foo" disappear.
I cannot reproduce this, neither in Emacs 27.2 nor in the current Git
master. I see some message flash momentarily after 5 sec, but then
"foo" gets restored.
I wonder what do you do differently to make Emacs behave like you say?
Thanks.
next prev parent reply other threads:[~2021-08-27 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 11:06 bug#50224: 27.2; auto-save-visited-mode blanks out the echo area after 5 seconds meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-27 12:39 ` Eli Zaretskii [this message]
2021-08-27 15:17 ` Lars Ingebrigtsen
2021-09-25 2:37 ` Lars Ingebrigtsen
[not found] ` <f17c50840020cf9e572e7ee701b457bb@teknik.io>
2021-09-27 10:46 ` Lars Ingebrigtsen
2021-09-27 15:37 ` meedstrom--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83fsuvqcya.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50224@debbugs.gnu.org \
--cc=meedstrom@teknik.io \
/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).