Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
I just tried helping somebody compile XEmacs 20.4 to enable clash
detection again. So here are a few questions
1. Where is is this documented?
I have no idea.
2. Is the default (disabled) intentional?
I vaguely remember it being intentional. There are definitely
problems with the implementation.
Jan
P.S. That 'somebody' also asked me to forward his plea to
enable it
again. Which I just did :-). However if the answer to 2. is yes (like
I think it is because the old clash detection is ugly), I would say
we should implement the FSF 20.x style clash detection before
reenabling it. I also vaguely remember Steve writing something to that
effect.
That wouldn't hurt. If you can get it done soon enough it can go into
21.0.
Personally I think locking like this has no place in an application
(other
than automatic handling of other systems like for CVS).
I don't know. The Roman Numeral editor does it. File locking is
unreliable over NFS. IMO it's safer to not use it. The current code
will detect when a file has changed out from under the editor and
that's the best we can hope for in the general case.