It used to be that (setq lock-directory nil) would tell xemacs to never,
ever prompt me with "user blah is locking file foo, really edit?"
Apparently things have been "improved" such that this is no longer
the case.
I tried (defun file-locked-p (file) nil) but that doesn't fix it either.
debug-on-quit / debug-on-error tricks only get me as far as
Signaling: (quit)
sit-for(3)
byte-code("..." [...] 6)
ask-user-about-lock-minibuf("/tmp/a" "jwz(a)grendel.jwz.org (pid
9839)")
ask-user-about-lock("/tmp/a" "jwz(a)grendel.jwz.org (pid 9839)")
self-insert-command(1)
How do I break the legs off this horrid misfeature?
XEmacs 21.4.12.
--
Jamie Zawinski
jwz(a)jwz.org
http://www.jwz.org/
jwz(a)dnalounge.com
http://www.dnalounge.com/