view lisp/=term-nasty.el @ 9793:28267fcc61be

Use macros IS_ANY_SEP, IS_DIRECTORY_SEP, IS_DEVICE_SEP, DIRECTORY_SEP, and DEVICE_SEP. [WINDOWSNT]: Add includes. Don't define sys_siglist. (sigchld_handler): Work around bug in MS C compiler. (sigchld_handler) [WINDOWSNT]: Do not call signal. (signal_process) [WINDOWSNT]: Use win32_kill_process instead of kill. (read_process_output) [WINDOWSNT]: Use read_child_output instead of read. (create_process) [WINDOWSNT]: Use pipe_with_inherited_out and pipe_with_inherited_in. Use the pid returned by child_setup. Deal with not having vfork, Call register_child. (close_process_descs): Do nothing if WINDOWSNT. (proc_buffer_char): No longer static.
author Richard M. Stallman <rms@gnu.org>
date Tue, 01 Nov 1994 08:31:31 +0000
parents ca3af688a85d
children 3938a0350eea
line wrap: on
line source

;;; term-nasty.el --- Damned Things from terminfo.el
;;; This file is in the public domain, and was written by Stallman and Mlynarik

;;; Commentary:

;; Some people used to be bothered by the following comments that were
;; found in terminal.el.  We decided they were distracting, and that it
;; was better not to have them there.  On the other hand, we didn't want
;; to appear to be giving in to the pressure to censor obscenity that
;; currently threatens freedom of speech and of the press in the US.
;; So we decided to put the comments here.

;;; Code:

These comments were removed from te-losing-unix.
  ;(what lossage)
  ;(message "fucking-unix: %d" char)

This was before te-process-output.
;; fucking unix has -such- braindamaged lack of tty control...

And about the need to handle output characters such as C-m, C-g, C-h
and C-i even though the termcap doesn't say they may be used:
;fuck me harder
;again and again!
;wa12id!!
;(spiked)

;;; term-nasty.el ends here