Convert consecutive FSF copyright years to ranges.
[bpt/emacs.git] / src / s / template.h
1 /* Template for system description header files.
2 This file describes the parameters that system description files
3 should define or not.
4
5 Copyright (C) 1985-1986, 1992, 1999, 2001-2011 Free Software Foundation, Inc.
6
7 This file is part of GNU Emacs.
8
9 GNU Emacs is free software: you can redistribute it and/or modify
10 it under the terms of the GNU General Public License as published by
11 the Free Software Foundation, either version 3 of the License, or
12 (at your option) any later version.
13
14 GNU Emacs is distributed in the hope that it will be useful,
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 GNU General Public License for more details.
18
19 You should have received a copy of the GNU General Public License
20 along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
21
22
23 /* Define symbols to identify the version of Unix this is.
24 Define all the symbols that apply correctly. */
25
26 /* #define USG5 */
27 /* #define USG */
28 /* #define HPUX */
29 /* #define BSD4_2 */
30 /* #define BSD4_3 */
31 /* #define BSD_SYSTEM */
32
33 /* SYSTEM_TYPE should indicate the kind of system you are using.
34 It sets the Lisp variable system-type. */
35
36 #define SYSTEM_TYPE "berkeley-unix"
37
38 /* Emacs can read input using SIGIO and buffering characters itself,
39 or using CBREAK mode and making C-g cause SIGINT.
40 The choice is controlled by the variable interrupt_input.
41
42 Define INTERRUPT_INPUT to make interrupt_input = 1 the default (use SIGIO)
43
44 Emacs uses the presence or absence of the SIGIO and BROKEN_SIGIO macros
45 to indicate whether or not signal-driven I/O is possible. It uses
46 INTERRUPT_INPUT to decide whether to use it by default.
47
48 SIGIO can be used only on systems that implement it (4.2 and 4.3).
49 CBREAK mode has two disadvantages
50 1) At least in 4.2, it is impossible to handle the Meta key properly.
51 I hear that in system V this problem does not exist.
52 2) Control-G causes output to be discarded.
53 I do not know whether this can be fixed in system V.
54
55 Another method of doing input is planned but not implemented.
56 It would have Emacs fork off a separate process
57 to read the input and send it to the true Emacs process
58 through a pipe. */
59 #define INTERRUPT_INPUT
60
61 /* Letter to use in finding device name of first pty,
62 if system supports pty's. 'a' means it is /dev/ptya0. */
63 #define FIRST_PTY_LETTER 'a'
64
65 /* Define HAVE_PTYS if the system supports pty devices. */
66 #define HAVE_PTYS
67
68 /* subprocesses should be undefined if you do NOT want to
69 have code for asynchronous subprocesses
70 (as used in M-x compile and M-x shell).
71 Currently only MSDOS does not support this. */
72
73 /* #undef subprocesses */
74
75 /* Define CLASH_DETECTION if you want lock files to be written
76 so that Emacs can tell instantly when you try to modify
77 a file that someone else has modified in his Emacs. */
78 #define CLASH_DETECTION
79
80 /* Define this if your operating system declares signal handlers to
81 have a type other than the usual. `The usual' is `void' for ANSI C
82 systems (i.e. when the __STDC__ macro is defined), and `int' for
83 pre-ANSI systems. If you're using GCC on an older system, __STDC__
84 will be defined, but the system's include files will still say that
85 signal returns int or whatever; in situations like that, define
86 this to be what the system's include files want. */
87 /* #define SIGTYPE int */
88
89 /* If the character used to separate elements of the executable path
90 is not ':', #define this to be the appropriate character constant. */
91 /* #define SEPCHAR ':' */
92
93 /* ============================================================ */
94
95 /* Here, add any special hacks needed to make Emacs work on this
96 system. For example, you might define certain system call names
97 that don't exist on your system, or that do different things on
98 your system and must be used only through an encapsulation (which
99 you should place, by convention, in sysdep.c). */
100
101 /* If the system's imake configuration file defines `NeedWidePrototypes'
102 as `NO', we must define NARROWPROTO manually. Such a define is
103 generated in the Makefile generated by `xmkmf'. If we don't
104 define NARROWPROTO, we will see the wrong function prototypes
105 for X functions taking float or double parameters. */
106
107 /* #define NARROWPROTO 1 */
108
109 /* ============================================================ */
110
111 /* After adding support for a new system, modify the large case
112 statement in configure.in to recognize reasonable
113 configuration names, and add a description of the system to
114 `etc/MACHINES'.
115
116 Check for any tests of $opsys in configure.in, and add an entry
117 for the new system if needed.
118
119 If you've just fixed a problem in an existing configuration file,
120 you should also check `etc/MACHINES' to make sure its descriptions
121 of known problems in that configuration should be updated. */
122