|--==> "JZ" == Jamie Zawinski <jwz(a)jwz.org&gt; writes: JZ> It used to be that (setq lock-directory nil) would tell xemacs to never, JZ> ever prompt me with "user blah is locking file foo, really edit?" JZ> Apparently things have been "improved" such that this is no longer JZ> the case. [...] JZ> How do I break the legs off this horrid misfeature? Does `(setq inhibit-clash-detection t)' give you what you need? -- |---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---| | XEmacs - The only _______ you'll ever need. | | Fill in the blank, yes, it's THAT good! | |------------------------------&lt;sryoungs(a)bigpond.net.au&gt;---|

|--==> "JZ" == Jamie Zawinski <jwz(a)jwz.org&gt; writes: JZ> Steve Youngs wrote: JZ> Yes, thanks. You're welcome. JZ> Never in a million years would I have found that, since it does JZ> not have "lock" in its name, and the messages do not use the JZ> word "clash". The only reason I found it was because I can remember configuring with '--with-clash-detection'. Someone not building their own XEmacs (Redhat people who use RPMs?) would have a hell of a time tracking this down. I think Jamie makes a very valid point here, that variable name blows goats. Yes, the name does correctly describe what it does, but you'd only find it if you were familiar with XEmacs' configuration options. I propose a name change (or at least a defvaralias) to `inhibit-file-locking'. And perhaps the warning message could be prepended with "Clash detected:". -- |---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---| | XEmacs - The only _______ you'll ever need. | | Fill in the blank, yes, it's THAT good! | |------------------------------&lt;sryoungs(a)bigpond.net.au&gt;---|