Re: Unsafe variable in a saved *compilation* buffer

[Stefan Monnier]

>     I'm not sure what's the reason to put such a file-local variable.
>     More to the point, I'm not sure it's a good idea in the first place.

> The reason M-x compile generates this local variable is to make sure
> the error messages are interpreted with respect to the proper
> directory.

> We want this variable to be put into effect if the text is saved and
> visited again.

Presumably if it's saved, it'll be saved in that same directory, so it'll
work just as well without the default-directory file-local variable.

OTOH, if the whole directory tree is moved/renamed (or accessed under
a different name, such as via Tramp, or sshfs, or ...), without the
default-directory file-local variable, things will still work just as well,
whereas with the default-directory file-local variable, the error messages
will be interpreted with respect to the improper directory.


        Stefan