According to Jan Harkes:
>
>Emacs is sending itself signals that tend to interrupt long running
>upcalls to userspace. As far as I know our kernel code knows about this
>and explicitly ignores the signals that emacs is triggering for a while.
>
Hmmm - I did try tracing the process and it looked l
I have had problems with emacs as well. I found that emacs would
create lockfiles (symlinks in the file's directory) when a file was
modified to protect against simultaneous edits. Sometimes these would
get confused and point oddly (which I suspect is a coda bug). I
didn't have time to track it
On Tue, Aug 08, 2000 at 12:56:56PM +0930, Brett Lymn wrote:
> I am running coda-5.3.5 on a couple of NetBSD-1.5 boxes, one
...
> The problem I have is that I cannot edit files in my coda file system
> with emacs-20.4, if I try then emacs just spins it's wheels and chews
> up all the CPU u
