if system supports pty's. 'a' means it is /dev/ptya0. */
#define FIRST_PTY_LETTER 'a'
-/* Define HAVE_TERMIOS if the system provides POSIX-style
- functions and macros for terminal control.
-
- Define HAVE_TERMIO if the system provides sysV-style ioctls
- for terminal control.
-
- Do not define both. HAVE_TERMIOS is preferred, if it is
- supported on your system. */
-
-#define HAVE_TERMIOS
-/* #define HAVE_TERMIO */
-
/* Define HAVE_PTYS if the system supports pty devices. */
#define HAVE_PTYS
-/* Define this symbol if your system has the functions bcopy, etc. */
-#define BSTRING
-
/* subprocesses should be undefined if you do NOT want to
have code for asynchronous subprocesses
(as used in M-x compile and M-x shell).
/* #undef subprocesses */
-/* If your system uses COFF (Common Object File Format) then define the
- preprocessor symbol "COFF". */
-
-/* #define COFF */
-
/* Define CLASH_DETECTION if you want lock files to be written
so that Emacs can tell instantly when you try to modify
a file that someone else has modified in his Emacs. */
is not ':', #define this to be the appropriate character constant. */
/* #define SEPCHAR ':' */
-/* Define this if the system can use mmap for buffer text allocation. */
-/* #define USE_MMAP_FOR_BUFFERS 1 */
-
/* ============================================================ */
/* Here, add any special hacks needed to make Emacs work on this
/* ============================================================ */
/* After adding support for a new system, modify the large case
- statement in the `configure' script to recognize reasonable
+ statement in configure.in to recognize reasonable
configuration names, and add a description of the system to
`etc/MACHINES'.
+ Check for any tests of $opsys in configure.in, and add an entry
+ for the new system if needed.
+
If you've just fixed a problem in an existing configuration file,
you should also check `etc/MACHINES' to make sure its descriptions
of known problems in that configuration should be updated. */