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-2012  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 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
  63    have code for asynchronous subprocesses
  64    (as used in M-x compile and M-x shell).
  65    Currently only MSDOS does not support this.  */
  66
  67 /* #undef subprocesses */
  68
  69 /* If the character used to separate elements of the executable path
  70    is not ':', #define this to be the appropriate character constant.  */
  71 /* #define SEPCHAR ':' */
  72
  73 /* ============================================================ */
  74
  75 /* Here, add any special hacks needed to make Emacs work on this
  76    system.  For example, you might define certain system call names
  77    that don't exist on your system, or that do different things on
  78    your system and must be used only through an encapsulation (which
  79    you should place, by convention, in sysdep.c).  */
  80
  81 /* If the system's imake configuration file defines `NeedWidePrototypes'
  82    as `NO', we must define NARROWPROTO manually.  Such a define is
  83    generated in the Makefile generated by `xmkmf'.  If we don't
  84    define NARROWPROTO, we will see the wrong function prototypes
  85    for X functions taking float or double parameters.  */
  86
  87 /*  #define NARROWPROTO 1 */
  88
  89 /* ============================================================ */
  90
  91 /* After adding support for a new system, modify the large case
  92    statement in configure.ac to recognize reasonable
  93    configuration names, and add a description of the system to
  94    `etc/MACHINES'.
  95
  96    Check for any tests of $opsys in configure.ac, and add an entry
  97    for the new system if needed.
  98
  99    If you've just fixed a problem in an existing configuration file,
 100    you should also check `etc/MACHINES' to make sure its descriptions
 101    of known problems in that configuration should be updated.  */