Mercurial > hg > xemacs-beta
comparison etc/MSDOS @ 0:376386a54a3c r19-14
Import from CVS: tag r19-14
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 08:45:50 +0200 |
| parents | |
| children | cca96a509cfe |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:376386a54a3c |
|---|---|
| 1 XEmacs does not yet work under MSDOS. If you would be interested in | |
| 2 porting XEmacs to MSDOS, please contact Chuck Thompson <cthomp@xemacs.org>. | |
| 3 | |
| 4 The following information applies to FSF Emacs, not to XEmacs. | |
| 5 | |
| 6 --------------------------------------------------------------------------- | |
| 7 This file describes use of Emacs 19 on MS-DOG. | |
| 8 | |
| 9 * The commands `mode25' and `mode4350' change the number of | |
| 10 lines of the screen. You get 43 lines on an EGA monitor, 50 on | |
| 11 a VGA monitor. | |
| 12 | |
| 13 * Ctrl-Break takes the place of C-g. Using compilers prior to | |
| 14 djgpp 1.11 maint 5, you should not use Ctrl-Break unless you | |
| 15 run under DPMI (i.e., you are using Windows, Qdpmi, ...) | |
| 16 | |
| 17 Actually, if Emacs is in an endless loop, you might as well go | |
| 18 ahead and try. Usually it works, but sometimes Emacs crashes | |
| 19 with a stack trace. This is not an Emacs bug. | |
| 20 | |
| 21 * Character codes 0200-0237 are self-inserting. | |
| 22 | |
| 23 * The keyboard support is made as X-like as possible. This means | |
| 24 that events like M-S-f1 will be generated (by Shift + Alt + f1). | |
| 25 | |
| 26 * Mouse support is partially implemented. | |
| 27 | |
| 28 * The `compile' command works on MS-DOG, but it waits for the | |
| 29 compilation to finish before letting you edit again. There's no other | |
| 30 way to do it, given the lack of asynchronous processes. | |
| 31 | |
| 32 * The function `expand-file-name' maps upper case letters to lower | |
| 33 case letters, since MS-DOG does not distinguish. | |
| 34 | |
| 35 * The new buffer-local variable `buffer-file-type' controls whether a | |
| 36 file contains text (newlines will be written as CR+LF) or binary data | |
| 37 (newlines written as LF). Text is specified by nil, and binary by t. | |
| 38 The status of a buffer can be seen in the mode line as "T:" or "B:" | |
| 39 before the major mode. | |
| 40 | |
| 41 Normally `buffer-file-type' is set automatically from the variable | |
| 42 `file-name-buffer-file-type-alist' which is an alist mapping regexps | |
| 43 to file types. | |
| 44 | |
| 45 You can visit a file explicitly as text, or as binary, using the | |
| 46 commands `find-file-binary' and `find-file-text'. | |
| 47 | |
| 48 * New variables `binary-process-input' and `binary-process-output' | |
| 49 control whether temporary files are opened as binary or as text | |
| 50 files. nil means text, and t means binary. The difference is | |
| 51 translation of CR+LF to LF and C-z handling. | |
| 52 | |
| 53 * Environment variables "HOME", "EMACSPATH", "TERM", "SHELL", | |
| 54 "USER", "NAME", and "TZ" are given default values as suitable | |
| 55 for a single user system. See src/msdos.c for details. | |
| 56 | |
| 57 * The function `substitute-in-file-name' disregards case in | |
| 58 environment variables, as the MS-DOG SET command does. | |
| 59 | |
| 60 * The variable `msdos-shells' contains a list of commands that | |
| 61 are shells. This variable is used to convert to map Unix-like | |
| 62 commands like "$SHELL -c /some/command" to MS-DOG commands | |
| 63 like "$SHELL /c \some\command". |