Known Problems with GNU Emacs
-Copyright (C) 1987-1989, 1993-1999, 2001-2011
+Copyright (C) 1987-1989, 1993-1999, 2001-2012
Free Software Foundation, Inc.
See the end of the file for license conditions.
the `flock' system call. The other involves creating a lock file;
`movemail' must be able to write in /usr/spool/mail in order to do
this. You control which one is used by defining, or not defining,
-the macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes.
+the macro MAIL_USE_FLOCK in config.h or the m/ or s/ file it includes.
IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR
SYSTEM, YOU CAN LOSE MAIL!
4) Use lbxproxy on the remote end of the connection. This is an interface
to the low bandwidth X extension in most modern X servers, which
improves performance dramatically, at the slight expense of correctness
- of the X protocol. lbxproxy acheives the performance gain by grouping
+ of the X protocol. lbxproxy achieves the performance gain by grouping
several X requests in one TCP packet and sending them off together,
instead of requiring a round-trip for each X request in a separate
packet. The switches that seem to work best for emacs are:
initialized variables. Emacs makes all initialized variables in most
of its files pure after dumping, but the variables declared static and
not initialized are not supposed to be pure. On these systems you
-may need to add "#define static" to the m- or the s- file.
+may need to add "#define static" to config.h.
* Runtime problems on legacy systems