bug#81638: 32.0.50; flyspell-prog-text-faces type and semantics

Stefan Monnier <[email protected]> writes:

> I'd be surprised if I'm the only one who has shell scripts where
> heredocs contain natural language text.  I agree it might not be
> desirable to add those elements globally, but they do make sense
> file-locally.

My initial motivation for reporting this was: I expect there will be
other kinds of markup languages or languages describing documents out
there where people will want to use a feature like `flyspell-prog-mode'.
Where it makes sense to be able to control this on a file or dir local
basis.  The point is: we don't know which (other) faces those modes may
use or add.

OTOH I don't understand what the benefit of the restricting the binding to
to a subset of three given faces is.  The warning might catch a typo,
ok.  But getting a warning every time I open the document is annoying.

The implementation of `flyspell-prog-mode' might be a bit naive.  But it
is not dangerous or harmful, and actually, the interface it offers might
be exactly what a lot of people want or expect.  At this moment I have
no idea what a rewrite would do differently in a fundamental way.  And
it works okish.

We can still improve the situation for LaTeX in a different way.  Fine
by me, really.  But `flyspell-prog-mode' will probably still have its
use cases for that the subject of this report is relevant.


Michael.