Re: *compilation* buffers should be readonly

[Stefan Monnier]

>>>>> "Kevin" == Kevin Rodgers <kevinr@ihs.com> writes:
> Won't that prevent Emacs itself from writing the compile command's output to
> the compilation buffer?

Not necessarily.  I'm not sure whether the current code would burp,
but it would be trivial to fix in either case.

> I also disagree with your suggestion in general,
> since someone might want to run an interactive command that requires input
> via `compile'.

I don't think that this works right now anyway (compile-mode does not
provide any kind of comint-like facility for interactively sending
text to the subprocess).

I don't find the argument for why it should be made read-only very
compelling (after all `sh -x' output starts with `+ ' on every line
and similarly `make's output has never looked anything like code
to me, so you'd have to be pretty airheaded to make such a mistake)
but on the other hand, I can't think of any good reason why the buffer
should be writable either (after all typing RET doesn't do what you want
and neither does mouse-2, so any potential editing you might do there
would be significantly crippled).


        Stefan