Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
6c10d0cd
Commit
6c10d0cd
authored
Jun 10, 1993
by
Jim Blandy
Browse files
* filelock.c: Test HAVE_LONG_FILE_NAMES, not SHORT_FILE_NAMES, to
interface nicely with autoconf.
parent
dea95cc2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
src/filelock.c
src/filelock.c
+4
-4
No files found.
src/filelock.c
View file @
6c10d0cd
...
...
@@ -67,7 +67,7 @@ char *superlock_path;
/* Set LOCK to the name of the lock file for the filename FILE.
char *LOCK; Lisp_Object FILE; */
#ifdef
SHORT
_FILE_NAMES
#if
n
def
HAVE_LONG
_FILE_NAMES
#define MAKE_LOCK_PATH(lock, file) \
(lock = (char *) alloca (14 + strlen (lock_path) + 1), \
...
...
@@ -107,7 +107,7 @@ fill_in_lock_short_file_name (lockfile, fn)
crc
.
byte
[
4
],
crc
.
byte
[
5
],
crc
.
byte
[
6
]);
}
#else
/*
!
defined
SHORT
_FILE_NAMES */
#else
/* defined
HAVE_LONG
_FILE_NAMES */
#define MAKE_LOCK_PATH(lock, file) \
(lock = (char *) alloca (XSTRING (file)->size + strlen (lock_path) + 1), \
...
...
@@ -132,7 +132,7 @@ fill_in_lock_file_name (lockfile, fn)
*
p
=
'!'
;
}
}
#endif
/*
SHORT
_FILE_NAMES */
#endif
/*
!defined HAVE_LONG
_FILE_NAMES */
static
Lisp_Object
lock_file_owner_name
(
lfname
)
...
...
@@ -169,7 +169,7 @@ lock_file_owner_name (lfname)
and put in the Emacs lock directory. */
/* (ie., /ka/king/junk.tex -> /!/!ka!king!junk.tex). */
/* If
SHORT
_FILE_NAMES is defined, the lock file name is the hex
/* If
HAVE_LONG
_FILE_NAMES is
not
defined, the lock file name is the hex
representation of a 14-bytes CRC generated from the file name
and put in the Emacs lock directory (not very nice, but it works).
(ie., /ka/king/junk.tex -> /!/ec92d3ed24a8f0). */
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment