[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changes to hi-lock before release.
From: |
Chong Yidong |
Subject: |
Re: Changes to hi-lock before release. |
Date: |
Sat, 21 Apr 2007 22:45:56 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.98 (gnu/linux) |
Richard Stallman <address@hidden> writes:
> > Also, it seems absurd for an explicit call to hi-lock-find-patterns to
> > check this variable. If the user explicitly gives the command, it
> > should be obeyed. I think that hi-lock-file-patterns-policy should be
> > tested only when hi-lock-find-patterns is called in other ways (such
> > as by find-file).
>
> What you suggested is indeed the behavior of hi-lock-find-patterns.
>
> I don't see it. hi-lock-find-patterns takes no arguments
> and it never bypasses checking hi-lock-file-patterns-policy.
> How does it distinguish explicit M-x calls from calls that come from hooks?
(when (and all-patterns
hi-lock-mode
(cond
((eq this-command 'hi-lock-find-patterns) t)
...
- Re: Changes to hi-lock before release., (continued)
Re: Changes to hi-lock before release., Richard Stallman, 2007/04/21
Re: Changes to hi-lock before release., Richard Stallman, 2007/04/21
Re: Changes to hi-lock before release.,
Chong Yidong <=
Re: Changes to hi-lock before release., Richard Stallman, 2007/04/22
Re: Changes to hi-lock before release., Chong Yidong, 2007/04/23
Re: Changes to hi-lock before release., Alan Mackenzie, 2007/04/24