bug#74673: 30.0.92; face warning on legal elisp syntax

[Eli Zaretskii <eliz@gnu.org>]

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Christopher Howard <christopher@librehacker.com>,  74673@debbugs.gnu.org
> Date: Wed, 04 Dec 2024 18:12:06 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Some nice features of the UI need the mouse, yes, and there's no
> > (easy) way around that.  That said, you can go to the "" part and type
> > "M-x describe-text-properties", which will pop a buffer that tells you
> > there's a help-echo property at that spot, and show a button which you
> > could press to have the text shown in the echo-area.
> >
> > If you really need to be able to show tool tips without the mouse, you
> > can write a simple function to show its text in the echo-area.
> > However, most tooltips are shown on UI parts where you cannot go, so
> > such a command will be of somewhat limited use.
> 
> Apologies if I missed something: this specific diagnostic is also
> visible with 'C-h .', right?

Yes.

> Feeling like this is worth mentioning because IME a lot of "mouse-bound"
> information is actually reachable with display-local-help; though of
> course describe-text-properties is definitely a useful tool to have in
> one's kit (I usually reach for 'C-u C-x =' FWIW).

If only that command had a more descriptive name...

> (IMHO the flymake-warning face (wavy underline) would be less
> surprising; in fact I find this style check being part of the "regular"
> font-locking a bit surprising too, this is the kind of opt-in linting
> I'd expect of flymake 🤷)

The wavy underline is used by flyspell-mode to show mis-spellings, so
I at least would be confused by seeing it on code.