Re: [PATCH] Remove obsolete fast-lock and lazy-lock libraries

[Stefan Monnier]

>> > At the moment, sensible normal values are nil and jit-lock-mode.
>> > Also sensible would be, for example, jit-lock-debug-mode, when a
>> > user wants to compare standard jit with her own enhanced version.
>> > It is not inconceivable that somebody might write something entirely
>> > new to supersede jit-lock.  Why do you want to make these things
>> > more difficult to do?
> So the question remains: why do you want to make these more advanced
> forms of debugging more difficult?

I'm sorry, but you lost me: what "more advanced forms of debugging"?

And in which way would my suggestion make it more difficult: in order to
add a new possible value to `font-lock-support-mode` you'd have to
modify `font-lock.el` or use advice anyway, which you can do just as
well without `font-lock-support-mode`.

> Your "... help both discoverability and make it easier to use ..."
> could be summed up as dumbing down.

Great joke.

> Surely it would be possible to leave font-lock-support-mode with its
> current power, while adding on these other things, too?

What power are you talking about?


        Stefan