[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34294: 27.0.50; flymake-start-on-save-buffer has no effect
From: |
Eli Zaretskii |
Subject: |
bug#34294: 27.0.50; flymake-start-on-save-buffer has no effect |
Date: |
Thu, 25 Apr 2019 08:46:19 +0300 |
> From: Juri Linkov <juri@linkov.net>
> Cc: joaotavora@gmail.com, 34294@debbugs.gnu.org
> Date: Wed, 24 Apr 2019 23:25:00 +0300
>
> >> I expect everything displayed in the echo area to remain in the
> >> *Messages* buffer.
> >
> > That assumption is false, only 'message' and its derivatives do that.
> > Is there something in our documentation that promotes this fallacy?
>
> I expected everything displayed in the echo area to be preserved
> in the *Messages* buffer because clicking on the echo area displays
> the *Messages* buffer.
If it's just an expectation, and is not based on anything the
documentation says, then I guess you will have to adapt your
expectations. The echo area has more than one use, and not all of
them are logged in *Messages*. The ELisp manual tells that:
The “echo area” is used for displaying error messages (*note Errors::),
for messages made with the ‘message’ primitive, and for echoing
keystrokes. It is not the same as the minibuffer, despite the fact that
the minibuffer appears (when active) in the same place on the screen as
the echo area. *Note The Minibuffer: (emacs)Minibuffer.