* s/sunos4shr.h: Apply changes from David J. Mackenzie; this isn't
[bpt/emacs.git] / src / s / template.h
CommitLineData
20c428fd
JB
1/* Template for system description header files.
2 This file describes the parameters that system description files
3 should define or not.
d4327fec 4 Copyright (C) 1985, 1986, 1992 Free Software Foundation, Inc.
20c428fd
JB
5
6This file is part of GNU Emacs.
7
8GNU Emacs is free software; you can redistribute it and/or modify
9it under the terms of the GNU General Public License as published by
d4327fec 10the Free Software Foundation; either version 2, or (at your option)
20c428fd
JB
11any later version.
12
13GNU Emacs is distributed in the hope that it will be useful,
14but WITHOUT ANY WARRANTY; without even the implied warranty of
15MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16GNU General Public License for more details.
17
18You should have received a copy of the GNU General Public License
19along with GNU Emacs; see the file COPYING. If not, write to
20the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */
21
22
23/*
24 * Define symbols to identify the version of Unix this is.
25 * Define all the symbols that apply correctly.
26 */
27
28/* #define UNIPLUS */
29/* #define USG5 */
30/* #define USG */
31/* #define HPUX */
32/* #define UMAX */
33/* #define BSD4_1 */
34/* #define BSD4_2 */
35/* #define BSD4_3 */
36/* #define BSD */
37/* #define VMS */
38
39/* SYSTEM_TYPE should indicate the kind of system you are using.
40 It sets the Lisp variable system-type. */
41
42#define SYSTEM_TYPE "berkeley-unix"
43
44/* NOMULTIPLEJOBS should be defined if your system's shell
45 does not have "job control" (the ability to stop a program,
46 run some other program, then continue the first one). */
47
48/* #define NOMULTIPLEJOBS */
49
50/* Emacs can read input using SIGIO and buffering characters itself,
51 or using CBREAK mode and making C-g cause SIGINT.
52 The choice is controlled by the variable interrupt_input.
53 Define INTERRUPT_INPUT to make interrupt_input = 1 the default (use SIGIO)
54
55 SIGIO can be used only on systems that implement it (4.2 and 4.3).
56 CBREAK mode has two disadvatages
57 1) At least in 4.2, it is impossible to handle the Meta key properly.
58 I hear that in system V this problem does not exist.
59 2) Control-G causes output to be discarded.
60 I do not know whether this can be fixed in system V.
61
62 Another method of doing input is planned but not implemented.
63 It would have Emacs fork off a separate process
64 to read the input and send it to the true Emacs process
65 through a pipe.
66*/
67
68#define INTERRUPT_INPUT
69
70/* Letter to use in finding device name of first pty,
71 if system supports pty's. 'a' means it is /dev/ptya0 */
72
73#define FIRST_PTY_LETTER 'a'
74
d4327fec
JB
75/*
76 * Define HAVE_TERMIOS if the system provides POSIX-style
77 * functions and macros for terminal control.
78 */
79
80#define HAVE_TERMIOS
81
b350a838
JB
82/*
83 * Define HAVE_TERMIO if the system provides sysV-style ioctls
84 * for terminal control.
85 */
86
87#define HAVE_TERMIO
88
20c428fd
JB
89/*
90 * Define HAVE_TIMEVAL if the system supports the BSD style clock values.
91 * Look in <sys/time.h> for a timeval structure.
92 */
93
94#define HAVE_TIMEVAL
95
96/*
97 * Define HAVE_SELECT if the system supports the `select' system call.
98 */
99
100/* #define HAVE_SELECT */
101
102/*
103 * Define HAVE_PTYS if the system supports pty devices.
104 */
105
106#define HAVE_PTYS
107
108/*
109 * Define NONSYSTEM_DIR_LIBRARY to make Emacs emulate
110 * The 4.2 opendir, etc., library functions.
111 */
112
113#define NONSYSTEM_DIR_LIBRARY
114
115/* Define this symbol if your system has the functions bcopy, etc. */
116
117#define BSTRING
118
119/* subprocesses should be defined if you want to
120 have code for asynchronous subprocesses
121 (as used in M-x compile and M-x shell).
122 This is generally OS dependent, and not supported
123 under most USG systems. */
124
125#define subprocesses
126
127/* If your system uses COFF (Common Object File Format) then define the
128 preprocessor symbol "COFF". */
129
130/* #define COFF */
131
132/* define MAIL_USE_FLOCK if the mailer uses flock
133 to interlock access to /usr/spool/mail/$USER.
134 The alternative is that a lock file named
135 /usr/spool/mail/$USER.lock. */
136
137#define MAIL_USE_FLOCK
138
139/* Define CLASH_DETECTION if you want lock files to be written
140 so that Emacs can tell instantly when you try to modify
141 a file that someone else has modified in his Emacs. */
142
143#define CLASH_DETECTION
144
14e76af9
JB
145/* Define this if your operating system declares signal handlers to
146 have a type other than the usual. `The usual' is `void' for ANSI C
147 systems (i.e. when the __STDC__ macro is defined), and `int' for
148 pre-ANSI systems. If you're using GCC on an older system, __STDC__
149 will be defined, but the system's include files will still say that
150 signal returns int or whatever; in situations like that, define
151 this to be what the system's include files want. */
152/* #define SIGTYPE int */
153
d4198db9
JB
154/* If the character used to separate elements of the executable path
155 is not ':', #define this to be the appropriate character constant. */
156/* #define SEPCHAR ':' */
157
20c428fd
JB
158/* Here, on a separate page, add any special hacks needed
159 to make Emacs work on this system. For example,
160 you might define certain system call names that don't
161 exist on your system, or that do different things on
162 your system and must be used only through an encapsulation
163 (Which you should place, by convention, in sysdep.c). */
164\f
165/* Some compilers tend to put everything declared static
166 into the initialized data area, which becomes pure after dumping Emacs.
167 On these systems, you must #define static as nothing to foil this.
168 Note that emacs carefully avoids static vars inside functions. */
169
170/* #define static */
00b1a5fb
JB
171
172\f
173
174/* After adding support for a new system, modify the large case
175 statement in the `configure' script to recognize reasonable
176 configuration names, and add a description of the system to
177 `etc/MACHINES'.
178
179 If you've just fixed a problem in an existing configuration file,
180 you should also check `etc/MACHINES' to make sure its descriptions
181 of known problems in that configuration should be updated. */