Re: Path to make desktop.el remember hi-lock-interactive-patterns

[Lennart Borgman <lennart.borgman@gmail.com>]

On Tue, May 12, 2009 at 4:52 PM, Davis Herring <herring@lanl.gov> wrote:
>> +        ;; Hi-lock
>> +        (when (and (boundp 'hi-lock-interactive-patterns)
>> +                   hi-lock-interactive-patterns
>> +                   hi-lock-mode)
>> +          (font-lock-add-keywords nil hi-lock-interactive-patterns t)
>> +          (font-lock-fontify-buffer))))))
>
> It would be cleaner to invoke some function in hi-lock.el rather than
> going straight into font-lock.

Yes, absolutely. This was more of a reminder of what need to be done.

> Moreover, hi-lock-mode already has a
> persistence mechanism; why does desktop need to additionally provide one
> that lasts only as long as you don't kill the buffer?

Doesn't they serve very different situations? I could for example save
a desktop file for a special problem I am working on. When that is
solved I might delete that desktop file (or at least never use it any
more...)