Re: next-error modifies *compilation* buffer

Re: next-error modifies *compilation* buffer

[Kevin Rodgers]

Dan Jacobson wrote:

> Gentlemen, apparently next-error changes the *compilation* buffer.
> Let's say you save a *grep* or *compilation* buffer to a file, then
> proceed to do some next-error.  Well, looking at the modeline, one can
> see that buffer has now been modified for some unnecessary reason.
> Even if one does vc-toggle-read-only first too.

I could not repeat this in Emacs 21.3.  (I didn't actually save the
*grep* buffer to a file, but just made it read-only with C-x C-q.  If
next-error tried to modify the buffer, C-x ` should have signalled an
error, which didn't happen.)  Did you start emacs with the -q and
--no-site-file command line options?

-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;">Kevin Rodgers</a>

next-error modifies *compilation* buffer

[Dan Jacobson]

Gentlemen, apparently next-error changes the *compilation* buffer.
Let's say you save a *grep* or *compilation* buffer to a file, then
proceed to do some next-error.  Well, looking at the modeline, one can
see that buffer has now been modified for some unnecessary reason.
Even if one does vc-toggle-read-only first too.
-- 
http://jidanni.org/ Taiwan(04)25854780