Xref: utzoo comp.emacs:6125 gnu.emacs.bug:805 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!rpi!rpi.edu!tale From: tale@pawl.rpi.edu (David C Lawrence) Newsgroups: comp.emacs,gnu.emacs.bug Subject: Re: how to not lock-buffer? Message-ID: Date: 19 May 89 22:52:02 GMT References: Sender: usenet@rpi.edu Reply-To: tale@pawl.rpi.edu Lines: 17 In-reply-to: wjc@ho5cad.ATT.COM's message of 19 May 89 10:56:39 GMT The problem with what you want is that the calls to lock-buffer are apparently happening in the C code (I haven't checked on this). If this is the case then no matter what you do with elisp the original filelock information tthat was compiled in at build-time will always shine through, though any elisp functions will use the new definition. You can witness somehing similar to this by redefining y-or-n-p to do something of your own preference (like allowing a recursive edit so you can bounce around in windows and buffers to be sure of your answer). Any function you use that has y-or-n-p called from elisp will use your function, but any function that called in a C function will use the original definiton. Dave -- (setq mail '("tale@pawl.rpi.edu" "tale@itsgw.rpi.edu" "tale@rpitsmts.bitnet")) (error "UUCP not spoken here. Long bang paths unlikely to get mail replies.")