aboutsummaryrefslogtreecommitdiffstats
path: root/src/s/template.h
diff options
context:
space:
mode:
Diffstat (limited to 'src/s/template.h')
-rw-r--r--src/s/template.h58
1 files changed, 2 insertions, 56 deletions
diff --git a/src/s/template.h b/src/s/template.h
index e3557aa191b..e6f43896aac 100644
--- a/src/s/template.h
+++ b/src/s/template.h
@@ -19,46 +19,6 @@ GNU General Public License for more details.
19You should have received a copy of the GNU General Public License 19You should have received a copy of the GNU General Public License
20along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */ 20along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
21 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 BSD_SYSTEM */
31
32/* Emacs can read input using SIGIO and buffering characters itself,
33 or using CBREAK mode and making C-g cause SIGINT.
34 The choice is controlled by the variable interrupt_input.
35
36 Define INTERRUPT_INPUT to make interrupt_input = 1 the default (use SIGIO)
37
38 Emacs uses the presence or absence of the SIGIO and BROKEN_SIGIO macros
39 to indicate whether or not signal-driven I/O is possible. It uses
40 INTERRUPT_INPUT to decide whether to use it by default.
41
42 SIGIO can be used only on systems that implement it (4.2 and 4.3).
43 CBREAK mode has two disadvantages
44 1) At least in 4.2, it is impossible to handle the Meta key properly.
45 I hear that in system V this problem does not exist.
46 2) Control-G causes output to be discarded.
47 I do not know whether this can be fixed in system V.
48
49 Another method of doing input is planned but not implemented.
50 It would have Emacs fork off a separate process
51 to read the input and send it to the true Emacs process
52 through a pipe. */
53#define INTERRUPT_INPUT
54
55/* Letter to use in finding device name of first pty,
56 if system supports pty's. 'a' means it is /dev/ptya0. */
57#define FIRST_PTY_LETTER 'a'
58
59/* Define HAVE_PTYS if the system supports pty devices. */
60#define HAVE_PTYS
61
62/* subprocesses should be undefined if you do NOT want to 22/* subprocesses should be undefined if you do NOT want to
63 have code for asynchronous subprocesses 23 have code for asynchronous subprocesses
64 (as used in M-x compile and M-x shell). 24 (as used in M-x compile and M-x shell).
@@ -66,11 +26,6 @@ along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
66 26
67/* #undef subprocesses */ 27/* #undef subprocesses */
68 28
69/* Define CLASH_DETECTION if you want lock files to be written
70 so that Emacs can tell instantly when you try to modify
71 a file that someone else has modified in his Emacs. */
72#define CLASH_DETECTION
73
74/* If the character used to separate elements of the executable path 29/* If the character used to separate elements of the executable path
75 is not ':', #define this to be the appropriate character constant. */ 30 is not ':', #define this to be the appropriate character constant. */
76/* #define SEPCHAR ':' */ 31/* #define SEPCHAR ':' */
@@ -83,25 +38,16 @@ along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
83 your system and must be used only through an encapsulation (which 38 your system and must be used only through an encapsulation (which
84 you should place, by convention, in sysdep.c). */ 39 you should place, by convention, in sysdep.c). */
85 40
86/* If the system's imake configuration file defines `NeedWidePrototypes'
87 as `NO', we must define NARROWPROTO manually. Such a define is
88 generated in the Makefile generated by `xmkmf'. If we don't
89 define NARROWPROTO, we will see the wrong function prototypes
90 for X functions taking float or double parameters. */
91
92/* #define NARROWPROTO 1 */
93
94/* ============================================================ */ 41/* ============================================================ */
95 42
96/* After adding support for a new system, modify the large case 43/* After adding support for a new system, modify the large case
97 statement in configure.in to recognize reasonable 44 statement in configure.ac to recognize reasonable
98 configuration names, and add a description of the system to 45 configuration names, and add a description of the system to
99 `etc/MACHINES'. 46 `etc/MACHINES'.
100 47
101 Check for any tests of $opsys in configure.in, and add an entry 48 Check for any tests of $opsys in configure.ac, and add an entry
102 for the new system if needed. 49 for the new system if needed.
103 50
104 If you've just fixed a problem in an existing configuration file, 51 If you've just fixed a problem in an existing configuration file,
105 you should also check `etc/MACHINES' to make sure its descriptions 52 you should also check `etc/MACHINES' to make sure its descriptions
106 of known problems in that configuration should be updated. */ 53 of known problems in that configuration should be updated. */
107