Re: next-error accepts a prefix argument, but previous-error doesn't

[Kevin Rodgers]

Juri Linkov <juri@jurta.org> wrote:
> Kevin Rodgers <ihs_4664@yahoo.com> writes:
> > Here's a patch to allow the user to specify how many errors to move:
> > [skipped...]
> >
> > ! (defun previous-error (argp)
> >
> > [...skipped]
> 
> You should change the argument argp of previous-error to be optional,
> just as argument of next-error already is:
> 
> (defun next-error (&optional argp)

Definitely.

It would also be nice if just `C-u' as a prefix argument for previous-error
had a special meaning, like it does for next-error.  I'd like it to reparse
the error messages and move to the last error, but that is a bigger change
and harder to implement.  The difficulty is that compilation-next-error-locus's
MOVE and REPARSE arguments are not orthogonal:

  (compile-reinitialize-errors reparse nil (and (not reparse) (max 0 move)))

-- 
Kevin Rodgers

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com