Re: master 5c70ff9: New user option 'font-lock-ignore'

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> The symbol is interpreted as a glob
>> +pattern; in particular, @code{*} matches everything.
> Do you mean shell glob patterns?  AFAIK, we don't use them in Emacs
> except for shell wildcards, so why are they used here?

A bit of history: originally his code only supported `*` and I suggested
the use of `wildcard-to-regexp` to both simplify the code, be more
general, and simplify the doc since we can just say "glob pattern" which
is a known concept.

> why not regexps?

I did not suggest the use of regexps because I felt that regexps written
as symbols could be problematic (especially the `.` being a second-class
citizen among symbol constituents in ELisp).  Admittedly, in practice
`.` works fine (i.e. without backslash-escaping) in most places in
a symbol so maybe it wouldn't be that bad.

My gut tells me that globs are preferable here (slightly less verbose
and slightly less odd):

    (typer-mode foo-*-baz)

vs

    (typer-mode \\\`foo-.*-baz\\\')

But either way is fine by me (we can make the \\\` anchoring \\\' implicit).

> And in any case, those patterns need a thorough description,
> since we don't use them elsewhere.  For example, the way to quote
> meta-characters such as '*' must be documented, because it isn't
> self-evident.

AFAIK glob patterns come with their own standard way to escape,
e.g. `foo[*]bar`, tho admittedly to make it into a single symbol you need
to write it as `foo\[*\]bar` :-(


        Stefan