|
From: | Kevin Rodgers |
Subject: | Re: next-error modifies *compilation* buffer |
Date: | Tue, 27 May 2003 09:21:13 -0600 |
User-agent: | Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 |
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:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
[Prev in Thread] | Current Thread | [Next in Thread] |