Re: bind next-error and previous-error in Occur mode? read-only?

[Ted Zlatanov <tzz@lifelogs.com>]

On 25 Jan 2007, drew.adams@oracle.com wrote:

> I suppose this is a new-feature suggestion, but it might be considered a bug
> ;-).
>
> Now that `next-error' and `previous-error' work with `occur', why not bind
> them to easy-to-hit keys in Occur mode?

I don't maintain occur-mode, but I did add the next/previous-error
support.  I didn't set default keys because they are (IMO) more useful
from the *other* buffer, not the *occur* buffer itself, so you can
move among matches.  That requires global bindings, probably, and the
feature was too new at the time.  At least that's how I remember it.
Anyhow, yes, that's a good idea and should be a TODO item.

I have more plans for next/previous-error, but RMS asked me to wait
until after the release to discuss and perhaps implement them.

> Also, shouldn't buffer *Occur* be read-only? If it were, we could bind `n'
> and `p' to `next-error-noselect' and `previous-error-noselect', just as in
> buffer *grep*.

I think that's a good TODO item as well.

Ted