hi-lock-buffer-mode and hi-lock-mode do not follow normal convention

2005-12-03 Thread M Jared Finder
It seems that much of Emacs follows a convention for naming global minor modes vs buffer local minor modes that hi-lock-mode does not follow. The convention is for buffer local minor modes to be named minor-mode-name and for global minor modes to be named global-minor-mode-name. I realize tha

Re: hi-lock-buffer-mode and hi-lock-mode do not follow normal convention

2005-12-05 Thread Juri Linkov
> It seems that much of Emacs follows a convention for naming global > minor modes vs buffer local minor modes that hi-lock-mode does not > follow. The convention is for buffer local minor modes to be named > minor-mode-name and for global minor modes to be named > global-minor-mode-name. > > I rea

Re: hi-lock-buffer-mode and hi-lock-mode do not follow normal convention

2005-12-05 Thread M Jared Finder
Juri Linkov wrote: This bit me because I don't like having the H for hi-lock-mode displayed in the mode line, so I added (setf (second (assoc 'hi-lock-mode minor-mode-alist)) nil) to my init file. This just broke. I don't like having the H displayed in the mode line for no reason too. I hav

Re: hi-lock-buffer-mode and hi-lock-mode do not follow normal convention

2005-12-14 Thread Juri Linkov
>> I have a local fix that displays Hi in the mode line only when the >> list of regexps to highlight is not empty in the current buffer. >> This means it is displayed only when hi-lock has something to highlight. >> Do you think it would be useful to use this logic by default in >> hi-lock.el? > >