danw@tbird9.prime.com (Dan Westerberg) (01/26/91)
I've just recently begun trying to install 18.56 here and have noticed something rather peculiar. I'd like Emacs to properly lock files being edited, as is stated in the Emacs manual. What I've found is a lock *is* written when a user begins to modify a file, but when another user begins to modify the same file, a *new* lock over-writes the existing lock. The user isn't prompted for this action, which seems should happen with ask-user-about-supercession, or something like that. After looking at the filelock.c source, it *looks* like everything SHOULD work, unless I am totally brain-dead. Our configuration does define CLASH_DETECTION. Here is my config.h setup: - define HAVE_SUN_WINDOWS - include "s-sunos4.h" - include "m-sparc.h" I am running a Sparc1 with SunOS 4.0.3, also I have learned that our Emacs 18.55 never locked files correctly either. Any help would be greatly appreciated. Dan -- =============================================================================== | | | Daniel I. Westerberg email: danw@tbird9.prime.com (or) | | Prime Computer Inc. danw@s49.prime.com | | MS 10-9 | | 500 Old Connecticut Path phone: 508-620-2800 x3644 | | Framingham, MA 10701 fax: 508-879-9098 | | | ===============================================================================
swansonc@acc.stolaf.edu (Chris Swanson, St. Olaf College) (01/31/91)
If anyone has an answer to this question, I would appreciate a copy. Could you please e-mail it to me, as I do not have a lot of time to read mail these days. Thank's in advance. -Chris -- Chris Swanson, Chem/CS/Pre-med Undergrad, St. Olaf College, Northfield,MN 55057 DDN: [CDS6] INTERNET: swansonc@acc.stolaf.edu UUCP: swansonc@stolaf AT&T: Work: (507)-645-6845 Home: (507)-663-6424 I would deny this reality, but that wouldn't pay the bills...