Mercurial > emacs
annotate man/msdog.texi @ 31321:648bbc1ab413
*** empty log message ***
author | Dave Love <fx@gnu.org> |
---|---|
date | Fri, 01 Sep 2000 14:06:45 +0000 |
parents | d24cddac1e33 |
children | 551b6c1b5ee5 |
rev | line source |
---|---|
24095 | 1 @c This is part of the Emacs manual. |
2 @c Copyright (C) 1985, 86, 87, 93, 94, 95, 1997 Free Software Foundation, Inc. | |
3 @c See file emacs.texi for copying conditions. | |
4 @node MS-DOS, Manifesto, Antinews, Top | |
5 @appendix Emacs and MS-DOS | |
6 @cindex MS-DOG | |
7 @cindex MS-DOS peculiarities | |
8 | |
9 This section briefly describes the peculiarities of using Emacs under | |
10 the MS-DOS ``operating system'' (also known as ``MS-DOG''). If you | |
11 build Emacs for MS-DOS, the binary will also run on Windows 3.X, Windows | |
12 NT, Windows 9X, or OS/2 as a DOS application; the information in this | |
13 chapter applies for all of those systems, if you use an Emacs that was | |
14 built for MS-DOS. | |
15 | |
16 Note that it is possible to build Emacs specifically for Windows NT or | |
17 Windows 9X. If you do that, most of this chapter does not apply; | |
18 instead, you get behavior much closer to what is documented in the rest | |
19 of the manual, including support for long file names, multiple frames, | |
20 scroll bars, mouse menus, and subprocesses. However, the section on | |
21 text files and binary files does still apply. There are also two | |
22 sections at the end of this chapter which apply specifically for Windows | |
23 NT and 9X. | |
24 | |
25 @menu | |
26 * Input: MS-DOS Input. Keyboard and mouse usage on MS-DOS. | |
27 * Display: MS-DOS Display. Fonts, frames and display size on MS-DOS. | |
28 * Files: MS-DOS File Names. File name conventions on MS-DOS. | |
29 * Text and Binary:: Text files on MS-DOS use CRLF to separate lines. | |
30 * Printing: MS-DOS Printing. How to specify the printer on MS-DOS. | |
31 * I18N: MS-DOS and MULE. Support for internationalization on MS-DOS. | |
32 * Processes: MS-DOS Processes. Running subprocesses on MS-DOS. | |
33 * Windows Processes:: Running subprocesses on Windows. | |
34 * Windows System Menu:: Controlling what the ALT key does. | |
35 @end menu | |
36 | |
37 @node MS-DOS Input | |
38 @section Keyboard and Mouse on MS-DOS | |
39 | |
40 @cindex Meta (under MS-DOS) | |
41 @cindex Hyper (under MS-DOS) | |
42 @cindex Super (under MS-DOS) | |
43 @vindex dos-super-key | |
44 @vindex dos-hyper-key | |
45 The PC keyboard maps use the left @key{ALT} key as the @key{META} key. | |
46 You have two choices for emulating the @key{SUPER} and @key{HYPER} keys: | |
47 choose either the right @key{CTRL} key or the right @key{ALT} key by | |
48 setting the variables @code{dos-hyper-key} and @code{dos-super-key} to 1 | |
49 or 2 respectively. If neither @code{dos-super-key} nor | |
50 @code{dos-hyper-key} is 1, then by default the right @key{ALT} key is | |
51 also mapped to the @key{META} key. However, if the MS-DOS international | |
52 keyboard support program @file{KEYB.COM} is installed, Emacs will | |
53 @emph{not} map the right @key{ALT} to @key{META}, since it is used for | |
54 accessing characters like @kbd{~} and @kbd{@@} on non-US keyboard | |
55 layouts; in this case, you may only use the left @key{ALT} as @key{META} | |
56 key. | |
57 | |
58 @kindex C-j @r{(MS-DOS)} | |
59 @vindex dos-keypad-mode | |
60 The variable @code{dos-keypad-mode} is a flag variable that controls | |
61 what key codes are returned by keys in the numeric keypad. You can also | |
62 define the keypad @key{ENTER} key to act like @kbd{C-j}, by putting the | |
63 following line into your @file{_emacs} file: | |
64 | |
65 @smallexample | |
66 ;; Make the Enter key from the Numeric keypad act as C-j. | |
67 (define-key function-key-map [kp-enter] [?\C-j]) | |
68 @end smallexample | |
69 | |
70 @kindex DEL @r{(MS-DOS)} | |
71 @kindex BS @r{(MS-DOS)} | |
72 The key that is called @key{DEL} in Emacs (because that's how it is | |
73 designated on most workstations) is known as @key{BS} (backspace) on a | |
74 PC. That is why the PC-specific terminal initialization remaps the | |
75 @key{BS} key to act as @key{DEL}; the @key{DEL} key is remapped to act | |
76 as @kbd{C-d} for the same reasons. | |
77 | |
78 @kindex C-g @r{(MS-DOS)} | |
79 @kindex C-BREAK @r{(MS-DOS)} | |
80 @cindex quitting on MS-DOS | |
81 Emacs built for MS-DOS recognizes @kbd{C-@key{BREAK}} as a quit | |
82 character, just like @kbd{C-g}. This is because Emacs cannot detect | |
83 that you have typed @kbd{C-g} until it is ready for more input. As a | |
84 consequence, you cannot use @kbd{C-g} to stop a running command | |
85 (@pxref{Quitting}). By contrast, @kbd{C-@key{BREAK}} @emph{is} detected | |
86 as soon as you type it (as @kbd{C-g} is on other systems), so it can be | |
87 used to stop a running command and for emergency escape | |
88 (@pxref{Emergency Escape}). | |
89 | |
90 @cindex mouse support under MS-DOS | |
91 Emacs on MS-DOS supports a mouse (on the default terminal only). | |
92 The mouse commands work as documented, including those that use menus | |
93 and the menu bar (@pxref{Menu Bar}). Scroll bars don't work in | |
94 MS-DOS Emacs. PC mice usually have only two buttons; these act as | |
95 @kbd{Mouse-1} and @kbd{Mouse-2}, but if you press both of them | |
30534
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
96 together, that has the effect of @kbd{Mouse-3}. If the mouse does have |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
97 3 buttons, Emacs detects that at startup, and all the 3 buttons function |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
98 normally, as on X. |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
99 |
31057
40ac457814bc
Document support for help strings and mouse highlight.
Eli Zaretskii <eliz@gnu.org>
parents:
30534
diff
changeset
|
100 Help strings for menu-bar and pop-up menus are displayed in the echo |
40ac457814bc
Document support for help strings and mouse highlight.
Eli Zaretskii <eliz@gnu.org>
parents:
30534
diff
changeset
|
101 area when the mouse pointer moves across the menu items. |
40ac457814bc
Document support for help strings and mouse highlight.
Eli Zaretskii <eliz@gnu.org>
parents:
30534
diff
changeset
|
102 Highlighting of mouse-sensitive text (@pxref{Mouse References}) is also |
40ac457814bc
Document support for help strings and mouse highlight.
Eli Zaretskii <eliz@gnu.org>
parents:
30534
diff
changeset
|
103 supported. |
40ac457814bc
Document support for help strings and mouse highlight.
Eli Zaretskii <eliz@gnu.org>
parents:
30534
diff
changeset
|
104 |
30534
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
105 @cindex mouse, set number of buttons |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
106 @findex msdos-set-mouse-buttons |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
107 Some versions of mouse drivers don't report the number of mouse |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
108 buttons correctly. For example, mice with a wheel report that they have |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
109 3 buttons, but only 2 of them are passed to Emacs; the clicks on the |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
110 wheel, which serves as the middle button, are not passed. In these |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
111 cases, you can use the @kbd{M-x msdos-set-mouse-buttons} command to set |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
112 the notion of number of buttons used by Emacs. This command prompts for |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
113 the number of buttons, and forces Emacs to behave as if your mouse had |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
114 that number of buttons. You could make such a setting permanent by |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
115 adding this fragment to your @file{_emacs} init file: |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
116 |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
117 @example |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
118 ;; Force Emacs to behave as if the mouse had |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
119 ;; only 2 buttons |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
120 (msdos-set-mouse-buttons 2) |
cddd0f1a86b1
(MS-DOS Input): Document msdos-set-mouse-buttons.
Eli Zaretskii <eliz@gnu.org>
parents:
29853
diff
changeset
|
121 @end example |
24095 | 122 |
123 @cindex Windows clipboard support | |
124 Emacs built for MS-DOS supports clipboard operations when it runs on | |
125 Windows. Commands that put text on the kill ring, or yank text from the | |
126 ring, check the Windows clipboard first, just as Emacs does on X Windows | |
127 (@pxref{Mouse Commands}). Only the primary selection and the cut buffer | |
128 are supported by MS-DOS Emacs on Windows; the secondary selection always | |
129 appears as empty. | |
130 | |
131 Due to the way clipboard access is implemented by Windows, the | |
132 length of text you can put into the clipboard is limited by the amount | |
133 of free DOS memory that is available to Emacs. Usually, up to 620KB of | |
134 text can be put into the clipboard, but this limit depends on the system | |
135 configuration and is lower if you run Emacs as a subprocess of | |
136 another program. If the killed text does not fit, Emacs prints a | |
137 message saying so, and does not put the text into the clipboard. | |
138 | |
139 Null characters also cannot be put into the Windows clipboard. If the | |
140 killed text includes null characters, Emacs does not put such text into | |
141 the clipboard, and prints in the echo area a message to that effect. | |
142 | |
143 @vindex dos-display-scancodes | |
144 The variable @code{dos-display-scancodes}, when non-@code{nil}, | |
145 directs Emacs to display the ASCII value and the keyboard scan code of | |
146 each keystroke; this feature serves as a complement to the | |
147 @code{view-lossage} command, for debugging. | |
148 | |
149 @node MS-DOS Display | |
150 @section Display on MS-DOS | |
151 @cindex faces under MS-DOS | |
152 @cindex fonts, emulating under MS-DOS | |
153 | |
154 Display on MS-DOS cannot use font variants, like bold or italic, | |
155 but it does support | |
156 multiple faces, each of which can specify a foreground and a background | |
157 color. Therefore, you can get the full functionality of Emacs packages | |
158 that use fonts (such as @code{font-lock}, Enriched Text mode, and | |
159 others) by defining the relevant faces to use different colors. Use the | |
160 @code{list-colors-display} command (@pxref{Frame Parameters}) and the | |
161 @code{list-faces-display} command (@pxref{Faces}) to see what colors and | |
162 faces are available and what they look like. | |
163 | |
164 The section @ref{MS-DOS and MULE}, later in this chapter, describes | |
165 how Emacs displays glyphs and characters which aren't supported by the | |
166 native font built into the DOS display. | |
167 | |
28093
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
168 @cindex cursor shape on MS-DOS |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
169 When Emacs starts, it changes the cursor shape to a solid box. This |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
170 is for compatibility with the Unix version, where the box cursor is the |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
171 default. This default shape can be changed to a bar by specifying the |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
172 @code{cursor-type} parameter in the variable @code{default-frame-alist} |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
173 (@pxref{Creating Frames}). The MS-DOS terminal doesn't support a |
29853
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
174 vertical-bar cursor, so the bar cursor is horizontal, and the |
28093
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
175 @code{@var{width}} parameter, if specified by the frame parameters, |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
176 actually determines its height. As an extension, the bar cursor |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
177 specification can include the starting scan line of the cursor as well |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
178 as its width, like this: |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
179 |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
180 @example |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
181 '(cursor-type bar @var{width} . @var{start}) |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
182 @end example |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
183 |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
184 @noindent |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
185 In addition, if the @var{width} parameter is negative, the cursor bar |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
186 begins at the top of the character cell. |
3e652235df91
(MS-DOS Display) Explain the differences in cursor type control
Eli Zaretskii <eliz@gnu.org>
parents:
27213
diff
changeset
|
187 |
24095 | 188 @cindex frames on MS-DOS |
189 Multiple frames (@pxref{Frames}) are supported on MS-DOS, but they all | |
190 overlap, so you only see a single frame at any given moment. That | |
191 single visible frame occupies the entire screen. When you run Emacs | |
192 from MS-Windows DOS box, you can make the visible frame smaller than | |
193 the full screen, but Emacs still cannot display more than a single | |
194 frame at a time. | |
195 | |
196 @cindex frame size under MS-DOS | |
197 @findex mode4350 | |
198 @findex mode25 | |
199 The @code{mode4350} command switches the display to 43 or 50 | |
200 lines, depending on your hardware; the @code{mode25} command switches | |
201 to the default 80x25 screen size. | |
202 | |
203 By default, Emacs only knows how to set screen sizes of 80 columns by | |
204 25, 28, 35, 40, 43 or 50 rows. However, if your video adapter has | |
205 special video modes that will switch the display to other sizes, you can | |
206 have Emacs support those too. When you ask Emacs to switch the frame to | |
207 @var{n} rows by @var{m} columns dimensions, it checks if there is a | |
208 variable called @code{screen-dimensions-@var{n}x@var{m}}, and if so, | |
209 uses its value (which must be an integer) as the video mode to switch | |
210 to. (Emacs switches to that video mode by calling the BIOS @code{Set | |
211 Video Mode} function with the value of | |
212 @code{screen-dimensions-@var{n}x@var{m}} in the @code{AL} register.) | |
213 For example, suppose your adapter will switch to 66x80 dimensions when | |
214 put into video mode 85. Then you can make Emacs support this screen | |
215 size by putting the following into your @file{_emacs} file: | |
216 | |
217 @example | |
218 (setq screen-dimensions-66x80 85) | |
219 @end example | |
220 | |
221 Since Emacs on MS-DOS can only set the frame size to specific | |
222 supported dimensions, it cannot honor every possible frame resizing | |
223 request. When an unsupported size is requested, Emacs chooses the next | |
224 larger supported size beyond the specified size. For example, if you | |
225 ask for 36x80 frame, you will get 40x80 instead. | |
226 | |
227 The variables @code{screen-dimensions-@var{n}x@var{m}} are used only | |
228 when they exactly match the specified size; the search for the next | |
229 larger supported size ignores them. In the above example, even if your | |
230 VGA supports 38x80 dimensions and you define a variable | |
231 @code{screen-dimensions-38x80} with a suitable value, you will still get | |
232 40x80 screen when you ask for a 36x80 frame. If you want to get the | |
233 38x80 size in this case, you can do it by setting the variable named | |
234 @code{screen-dimensions-36x80} with the same video mode value as | |
235 @code{screen-dimensions-38x80}. | |
236 | |
237 Changing frame dimensions on MS-DOS has the effect of changing all the | |
238 other frames to the new dimensions. | |
239 | |
240 @node MS-DOS File Names | |
241 @section File Names on MS-DOS | |
242 @cindex file names under MS-DOS | |
243 @cindex init file, default name under MS-DOS | |
244 | |
245 MS-DOS normally uses a backslash, @samp{\}, to separate name units | |
246 within a file name, instead of the slash used on other systems. Emacs | |
247 on MS-DOS permits use of either slash or backslash, and also knows | |
248 about drive letters in file names. | |
249 | |
250 On MS-DOS, file names are case-insensitive and limited to eight | |
251 characters, plus optionally a period and three more characters. Emacs | |
252 knows enough about these limitations to handle file names that were | |
253 meant for other operating systems. For instance, leading dots @samp{.} | |
254 in file names are invalid in MS-DOS, so Emacs transparently converts | |
255 them to underscores @samp{_}; thus your default init file (@pxref{Init | |
256 File}) is called @file{_emacs} on MS-DOS. Excess characters before or | |
257 after the period are generally ignored by MS-DOS itself; thus, if you | |
258 visit the file @file{LongFileName.EvenLongerExtension}, you will | |
259 silently get @file{longfile.eve}, but Emacs will still display the long | |
260 file name on the mode line. Other than that, it's up to you to specify | |
261 file names which are valid under MS-DOS; the transparent conversion as | |
262 described above only works on file names built into Emacs. | |
263 | |
264 @cindex backup file names on MS-DOS | |
265 The above restrictions on the file names on MS-DOS make it almost | |
266 impossible to construct the name of a backup file (@pxref{Backup | |
267 Names}) without losing some of the original file name characters. For | |
268 example, the name of a backup file for @file{docs.txt} is | |
269 @file{docs.tx~} even if single backup is used. | |
270 | |
271 @cindex file names under Windows 95/NT | |
272 @cindex long file names in DOS box under Windows 95/NT | |
273 If you run Emacs as a DOS application under Windows 9X, you can | |
274 turn on support for long file names. If you do that, Emacs doesn't | |
275 truncate file names or convert them to lower case; instead, it uses the | |
276 file names that you specify, verbatim. To enable long file name | |
29107 | 277 support, set the environment variable @env{LFN} to @samp{y} before |
24095 | 278 starting Emacs. Unfortunately, Windows NT doesn't allow DOS programs to |
279 access long file names, so Emacs built for MS-DOS will only see their | |
280 short 8+3 aliases. | |
281 | |
29107 | 282 @cindex @env{HOME} directory under MS-DOS |
24095 | 283 MS-DOS has no notion of home directory, so Emacs on MS-DOS pretends |
29107 | 284 that the directory where it is installed is the value of @env{HOME} |
24095 | 285 environment variable. That is, if your Emacs binary, |
286 @file{emacs.exe}, is in the directory @file{c:/utils/emacs/bin}, then | |
29107 | 287 Emacs acts as if @env{HOME} were set to @samp{c:/utils/emacs}. In |
24095 | 288 particular, that is where Emacs looks for the init file @file{_emacs}. |
289 With this in mind, you can use @samp{~} in file names as an alias for | |
29107 | 290 the home directory, as you would in Unix. You can also set @env{HOME} |
24095 | 291 variable in the environment before starting Emacs; its value will then |
292 override the above default behavior. | |
293 | |
294 Emacs on MS-DOS handles the directory name @file{/dev} specially, | |
295 because of a feature in the emulator libraries of DJGPP that pretends | |
296 I/O devices have names in that directory. We recommend that you avoid | |
297 using an actual directory named @file{/dev} on any disk. | |
298 | |
299 @node Text and Binary | |
300 @section Text Files and Binary Files | |
301 @cindex text and binary files on MS-DOS/MS-Windows | |
302 | |
303 GNU Emacs uses newline characters to separate text lines. This is the | |
304 convention used on Unix, on which GNU Emacs was developed, and on GNU | |
305 systems since they are modeled on Unix. | |
306 | |
307 @cindex end-of-line conversion on MS-DOS/MS-Windows | |
308 MS-DOS and MS-Windows normally use carriage-return linefeed, a | |
309 two-character sequence, to separate text lines. (Linefeed is the same | |
310 character as newline.) Therefore, convenient editing of typical files | |
311 with Emacs requires conversion of these end-of-line (EOL) sequences. | |
312 And that is what Emacs normally does: it converts carriage-return | |
313 linefeed into newline when reading files, and converts newline into | |
314 carriage-return linefeed when writing files. The same mechanism that | |
315 handles conversion of international character codes does this conversion | |
316 also (@pxref{Coding Systems}). | |
317 | |
29853
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
318 @cindex cursor location, on MS-DOS |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
319 @cindex point location, on MS-DOS |
24095 | 320 One consequence of this special format-conversion of most files is |
321 that character positions as reported by Emacs (@pxref{Position Info}) do | |
322 not agree with the file size information known to the operating system. | |
323 | |
324 In addition, if Emacs recognizes from a file's contents that it uses | |
325 newline rather than carriage-return linefeed as its line separator, it | |
29853
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
326 does not perform EOL conversion when reading or writing that file. Thus, |
24095 | 327 you can read and edit files from Unix or GNU systems on MS-DOS with no |
328 special effort, and they will be left with their Unix-style EOLs. | |
329 | |
29853
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
330 The mode line indicates whether end-of-line translation was used for |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
331 the current buffer. If MS-DOS end-of-line translation is in use for the |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
332 buffer, a backslash @samp{\} is displayed after the coding system |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
333 mnemonic near the beginning of the mode line (@pxref{Mode Line}). If no |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
334 EOL translation was performed, the string @samp{(Unix)} is displayed |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
335 instead of the backslash, to alert you that the file's EOL format is not |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
336 the usual carriage-return linefeed. |
24095 | 337 |
29853
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
338 @cindex DOS-to-Unix conversion of files |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
339 @pindex dos2unix |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
340 End-of-line conversion is part of the general coding system conversion |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
341 mechanism, so the way to control whether to treat a text file as |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
342 DOS-style or Unix-style is with the commands for specifying a coding |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
343 system (@pxref{Specify Coding}). For example, @kbd{C-x @key{RET} c unix |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
344 @key{RET} C-x C-f foobar.txt} visits the file @file{foobar.txt} without |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
345 converting the EOLs; if that file has carriage-return linefeed pairs at |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
346 the end of its lines, Emacs will display @samp{^M} at the end of each |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
347 line. Similarly, you can force Emacs to save a buffer with specific EOL |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
348 format with the @kbd{C-x @key{RET} f} command. For example, to save a |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
349 buffer with Unix EOL format, type @kbd{C-x @key{RET} f unix @key{RET} |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
350 C-x C-s}. Thus, visiting a file with DOS EOL conversion, then saving it |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
351 with Unix EOL format effectively converts the file to Unix text style, |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
352 like the popular program @code{dos2unix} does. |
24095 | 353 |
354 @cindex untranslated file system | |
355 @findex add-untranslated-filesystem | |
356 When you use NFS or Samba to access file systems that reside on | |
357 computers using Unix or GNU systems, Emacs should not perform | |
358 end-of-line translation on any files in these file systems--not even | |
359 when you create a new file. To request this, designate these file | |
360 systems as @dfn{untranslated} file systems by calling the function | |
361 @code{add-untranslated-filesystem}. It takes one argument: the file | |
362 system name, including a drive letter and optionally a directory. For | |
363 example, | |
364 | |
365 @example | |
366 (add-untranslated-filesystem "Z:") | |
367 @end example | |
368 | |
369 @noindent | |
370 designates drive Z as an untranslated file system, and | |
371 | |
372 @example | |
373 (add-untranslated-filesystem "Z:\\foo") | |
374 @end example | |
375 | |
376 @noindent | |
377 designates directory @file{\foo} on drive Z as an untranslated file | |
378 system. | |
379 | |
380 Most often you would use @code{add-untranslated-filesystem} in your | |
381 @file{_emacs} file, or in @file{site-start.el} so that all the users at | |
382 your site get the benefit of it. | |
383 | |
384 @findex remove-untranslated-filesystem | |
385 To countermand the effect of @code{add-untranslated-filesystem}, use | |
386 the function @code{remove-untranslated-filesystem}. This function takes | |
387 one argument, which should be a string just like the one that was used | |
388 previously with @code{add-untranslated-filesystem}. | |
389 | |
29853
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
390 Designating a file system as untranslated does @strong{not} disable |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
391 code conversions as specified by the coding systems set up by your |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
392 language environment, it only affects the EOL conversions, by forcing |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
393 Emacs to create new files with Unix-style newline-only EOLs. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
394 |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
395 @vindex file-name-buffer-file-type-alist |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
396 @cindex binary files, on MS-DOS/MS-Windows |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
397 Some kinds of files should not be converted at all, because their |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
398 contents are not really text. Therefore, Emacs on MS-DOS distinguishes |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
399 certain files as @dfn{binary files}. (This distinction is not part of |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
400 MS-DOS; it is made by Emacs only.) Binary files include executable |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
401 programs, compressed archives, etc. Emacs uses the file name to decide |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
402 whether to treat a file as binary: the variable |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
403 @code{file-name-buffer-file-type-alist} defines the file-name patterns |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
404 that indicate binary files. If a file name matches one of the patterns |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
405 for binary files (those whose associations are of the type |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
406 @code{(@var{pattern} . t)}, Emacs reads and writes that file using the |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
407 @code{no-conversion} coding system (@pxref{Coding Systems}) which turns |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
408 off @emph{all} coding-system conversions, not only the EOL conversion. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
409 @code{file-name-buffer-file-type-alist} also includes file-name patterns |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
410 for files which are known to be DOS-style text files with |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
411 carriage-return linefeed EOL format, such as @file{CONFIG.SYS}; Emacs |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
412 always writes those files with DOS-style EOLs. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
413 |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
414 If a file which belongs to an untranslated file system matches one of |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
415 the file-name patterns in @code{file-name-buffer-file-type-alist}, the |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
416 EOL conversion is determined by @code{file-name-buffer-file-type-alist}. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
417 |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
418 @findex find-file-text |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
419 @findex find-file-binary |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
420 You can visit a file and specify whether to treat it as text or binary |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
421 using the commands @code{find-file-text} and @code{find-file-binary}. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
422 @code{find-file-text} specifies DOS EOL conversions, but leaves the |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
423 other coding conversions unspecified (Emacs determines the required |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
424 conversions via the usual defaults and coding-detection mechanisms). On |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
425 the other hand, @code{find-file-binary} turns off @emph{all} |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
426 coding-system conversions. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
427 |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
428 @findex find-file-literally@r{, and binary files} |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
429 The @code{find-file-text} and @code{find-file-binary} commands are |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
430 only available when Emacs runs on MS-DOS or MS-Windows. The command |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
431 @code{find-file-literally}, which is available on all platforms, |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
432 produces the same effect as @code{find-file-binary}. |
d49e929bbdf6
(Text and Binary): Separate description of EOL
Eli Zaretskii <eliz@gnu.org>
parents:
29107
diff
changeset
|
433 |
24095 | 434 @node MS-DOS Printing |
435 @section Printing and MS-DOS | |
436 | |
437 Printing commands, such as @code{lpr-buffer} (@pxref{Hardcopy}) and | |
27213 | 438 @code{ps-print-buffer} (@pxref{PostScript}) can work in MS-DOS and |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
439 MS-Windows by sending the output to one of the printer ports, if a |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
440 Unix-style @code{lpr} program is unavailable. This behaviour is |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
441 controlled by the same variables that control printing with @code{lpr} |
27213 | 442 on Unix (@pxref{Hardcopy}, @pxref{PostScript Variables}), but the |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
443 defaults for these variables on MS-DOS and MS-Windows are not the same |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
444 as the defaults on Unix. |
24095 | 445 |
24723 | 446 @vindex printer-name @r{(MS-DOS)} |
24095 | 447 If you want to use your local printer, printing on it in the usual DOS |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
448 manner, then set the Lisp variable @code{lpr-command} to @code{""} (its |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
449 default value) and @code{printer-name} to the name of the printer |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
450 port---for example, @code{"PRN"}, the usual local printer port (that's |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
451 the default), or @code{"LPT2"}, or @code{"COM1"} for a serial printer. |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
452 You can also set @code{printer-name} to a file name, in which case |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
453 ``printed'' output is actually appended to that file. If you set |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
454 @code{printer-name} to @code{"NUL"}, printed output is silently |
24095 | 455 discarded (sent to the system null device). |
456 | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
457 On MS-Windows, when the Windows network software is installed, you can |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
458 also use a printer shared by another machine by setting |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
459 @code{printer-name} to the UNC share name for that printer--for example, |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
460 @code{"//joes_pc/hp4si"}. (It doesn't matter whether you use forward |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
461 slashes or backslashes here.) To find out the names of shared printers, |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
462 run the command @samp{net view} at a DOS command prompt to obtain a list |
24731 | 463 of servers, and @samp{net view @var{server-name}} to see the names of printers |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
464 (and directories) shared by that server. |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
465 |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
466 If you set @code{printer-name} to a file name, it's best to use an |
24095 | 467 absolute file name. Emacs changes the working directory according to |
468 the default directory of the current buffer, so if the file name in | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
469 @code{printer-name} is relative, you will end up with several such |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
470 files, each one in the directory of the buffer from which the printing |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
471 was done. |
24095 | 472 |
473 @findex print-buffer @r{(MS-DOS)} | |
474 @findex print-region @r{(MS-DOS)} | |
475 @vindex lpr-headers-switches @r{(MS-DOS)} | |
476 The commands @code{print-buffer} and @code{print-region} call the | |
477 @code{pr} program, or use special switches to the @code{lpr} program, to | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
478 produce headers on each printed page. MS-DOS and MS-Windows don't |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
479 normally have these programs, so by default, the variable |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
480 @code{lpr-headers-switches} is set so that the requests to print page |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
481 headers are silently ignored. Thus, @code{print-buffer} and |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
482 @code{print-region} produce the same output as @code{lpr-buffer} and |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
483 @code{lpr-region}, respectively. If you do have a suitable @code{pr} |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
484 program (for example, from GNU Textutils), set |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
485 @code{lpr-headers-switches} to @code{nil}; Emacs will then call |
24095 | 486 @code{pr} to produce the page headers, and print the resulting output as |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
487 specified by @code{printer-name}. |
24095 | 488 |
489 @vindex print-region-function @r{(MS-DOS)} | |
490 @cindex lpr usage under MS-DOS | |
491 @vindex lpr-command @r{(MS-DOS)} | |
492 @vindex lpr-switches @r{(MS-DOS)} | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
493 Finally, if you do have an @code{lpr} work-alike, you can set the |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
494 variable @code{lpr-command} to @code{"lpr"}. Then Emacs will use |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
495 @code{lpr} for printing, as on other systems. (If the name of the |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
496 program isn't @code{lpr}, set @code{lpr-command} to specify where to |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
497 find it.) The variable @code{lpr-switches} has its standard meaning |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
498 when @code{lpr-command} is not @code{""}. If the variable |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
499 @code{printer-name} has a string value, it is used as the value for the |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
500 @code{-P} option to @code{lpr}, as on Unix. |
24095 | 501 |
502 @findex ps-print-buffer @r{(MS-DOS)} | |
503 @findex ps-spool-buffer @r{(MS-DOS)} | |
24715 | 504 @vindex ps-printer-name @r{(MS-DOS)} |
24095 | 505 @vindex ps-lpr-command @r{(MS-DOS)} |
506 @vindex ps-lpr-switches @r{(MS-DOS)} | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
507 A parallel set of variables, @code{ps-lpr-command}, |
27213 | 508 @code{ps-lpr-switches}, and @code{ps-printer-name} (@pxref{PostScript |
24564 | 509 Variables}), defines how PostScript files should be printed. These |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
510 variables are used in the same way as the corresponding variables |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
511 described above for non-PostScript printing. Thus, the value of |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
512 @code{ps-printer-name} is used as the name of the device (or file) to |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
513 which PostScript output is sent, just as @code{printer-name} is used for |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
514 non-PostScript printing. (There are two distinct sets of variables in |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
515 case you have two printers attached to two different ports, and only one |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
516 of them is a PostScript printer.) |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
517 |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
518 The default value of the variable @code{ps-lpr-command} is @code{""}, |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
519 which causes PostScript output to be sent to the printer port specified |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
520 by @code{ps-printer-name}, but @code{ps-lpr-command} can also be set to |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
521 the name of a program which will accept PostScript files. Thus, if you |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
522 have a non-PostScript printer, you can set this variable to the name of |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
523 a PostScript interpreter program (such as Ghostscript). Any switches |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
524 that need to be passed to the interpreter program are specified using |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
525 @code{ps-lpr-switches}. (If the value of @code{ps-printer-name} is a |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
526 string, it will be added to the list of switches as the value for the |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
527 @code{-P} option. This is probably only useful if you are using |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
528 @code{lpr}, so when using an interpreter typically you would set |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
529 @code{ps-printer-name} to something other than a string so it is |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
530 ignored.) |
24095 | 531 |
532 For example, to use Ghostscript for printing on an Epson printer | |
24715 | 533 connected to the @samp{LPT2} port, put this in your @file{_emacs} file: |
24095 | 534 |
535 @example | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
536 (setq ps-printer-name t) ; Ghostscript doesn't understand -P |
24095 | 537 (setq ps-lpr-command "c:/gs/gs386") |
538 (setq ps-lpr-switches '("-q" "-dNOPAUSE" | |
539 "-sDEVICE=epson" | |
540 "-r240x72" | |
541 "-sOutputFile=LPT2" | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
542 "-Ic:/gs")) |
24095 | 543 @end example |
544 | |
545 @noindent | |
546 (This assumes that Ghostscript is installed in the @file{"c:/gs"} | |
547 directory.) | |
548 | |
24096
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
549 @vindex dos-printer |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
550 @vindex dos-ps-printer |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
551 For backwards compatibility, the value of @code{dos-printer} |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
552 (@code{dos-ps-printer}), if it has a value, overrides the value of |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
553 @code{printer-name} (@code{ps-printer-name}), on MS-DOS and MS-Windows |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
554 only. |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
555 |
083c21910c49
(MS-DOS Printing): Rewrite section.
Andrew Innes <andrewi@gnu.org>
parents:
24095
diff
changeset
|
556 |
24095 | 557 @node MS-DOS and MULE |
558 @section International Support on MS-DOS | |
559 @cindex international support @r{(MS-DOS)} | |
560 | |
561 Emacs on MS-DOS supports the same international character sets as it | |
562 does on Unix and other platforms (@pxref{International}), including | |
563 coding systems for converting between the different character sets. | |
564 However, due to incompatibilities between MS-DOS/MS-Windows and Unix, | |
565 there are several DOS-specific aspects of this support that users should | |
566 be aware of. This section describes these aspects. | |
567 | |
568 @table @kbd | |
569 @item M-x dos-codepage-setup | |
570 Set up Emacs display and coding systems as appropriate for the current | |
571 DOS codepage. | |
572 | |
573 @item M-x codepage-setup | |
574 Create a coding system for a certain DOS codepage. | |
575 @end table | |
576 | |
577 @cindex codepage, MS-DOS | |
578 @cindex DOS codepages | |
579 MS-DOS is designed to support one character set of 256 characters at | |
580 any given time, but gives you a variety of character sets to choose | |
581 from. The alternative character sets are known as @dfn{DOS codepages}. | |
582 Each codepage includes all 128 ASCII characters, but the other 128 | |
583 characters (codes 128 through 255) vary from one codepage to another. | |
584 Each DOS codepage is identified by a 3-digit number, such as 850, 862, | |
585 etc. | |
586 | |
587 In contrast to X Windows, which lets you use several fonts at the same | |
588 time, MS-DOS doesn't allow use of several codepages in a single session. | |
589 Instead, MS-DOS loads a single codepage at system startup, and you must | |
590 reboot MS-DOS to change it@footnote{Normally, one particular codepage is | |
591 burnt into the display memory, while other codepages can be installed by | |
592 modifying system configuration files, such as @file{CONFIG.SYS}, and | |
593 rebooting.}. Much the same limitation applies when you run DOS | |
594 executables on other systems such as MS-Windows. | |
595 | |
596 @cindex unibyte operation @r{(MS-DOS)} | |
597 If you invoke Emacs on MS-DOS with the @samp{--unibyte} option | |
598 (@pxref{Initial Options}), Emacs does not perform any conversion of | |
599 non-ASCII characters. Instead, it reads and writes any non-ASCII | |
600 characters verbatim, and sends their 8-bit codes to the display | |
601 verbatim. Thus, unibyte Emacs on MS-DOS supports the current codepage, | |
602 whatever it may be, but cannot even represent any other characters. | |
603 | |
604 @vindex dos-codepage | |
605 For multibyte operation on MS-DOS, Emacs needs to know which | |
606 characters the chosen DOS codepage can display. So it queries the | |
607 system shortly after startup to get the chosen codepage number, and | |
608 stores the number in the variable @code{dos-codepage}. Some systems | |
609 return the default value 437 for the current codepage, even though the | |
610 actual codepage is different. (This typically happens when you use the | |
611 codepage built into the display hardware.) You can specify a different | |
612 codepage for Emacs to use by setting the variable @code{dos-codepage} in | |
613 your init file. | |
614 | |
615 @cindex language environment, automatic selection on @r{MS-DOS} | |
24615
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
616 Multibyte Emacs supports only certain DOS codepages: those which can |
24594
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
617 display Far-Eastern scripts, like the Japanese codepage 932, and those |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
618 that encode a single ISO 8859 character set. |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
619 |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
620 The Far-Eastern codepages can directly display one of the MULE |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
621 character sets for these countries, so Emacs simply sets up to use the |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
622 appropriate terminal coding system that is supported by the codepage. |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
623 The special features described in the rest of this section mostly |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
624 pertain to codepages that encode ISO 8859 character sets. |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
625 |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
626 For the codepages which correspond to one of the ISO character sets, |
24615
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
627 Emacs knows the character set name based on the codepage number. Emacs |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
628 automatically creates a coding system to support reading and writing |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
629 files that use the current codepage, and uses this coding system by |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
630 default. The name of this coding system is @code{cp@var{nnn}}, where |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
631 @var{nnn} is the codepage number.@footnote{The standard Emacs coding |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
632 systems for ISO 8859 are not quite right for the purpose, because |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
633 typically the DOS codepage does not match the standard ISO character |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
634 codes. For example, the letter @samp{@,{c}} (@samp{c} with cedilla) has |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
635 code 231 in the standard Latin-1 character set, but the corresponding |
393b5f9a3631
Fix wording for the last change.
Eli Zaretskii <eliz@gnu.org>
parents:
24594
diff
changeset
|
636 DOS codepage 850 uses code 135 for this glyph.} |
24095 | 637 |
638 @cindex mode line @r{(MS-DOS)} | |
639 All the @code{cp@var{nnn}} coding systems use the letter @samp{D} (for | |
640 ``DOS'') as their mode-line mnemonic. Since both the terminal coding | |
641 system and the default coding system for file I/O are set to the proper | |
642 @code{cp@var{nnn}} coding system at startup, it is normal for the mode | |
643 line on MS-DOS to begin with @samp{-DD\-}. @xref{Mode Line}. | |
24594
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
644 Far-Eastern DOS terminals do not use the @code{cp@var{nnn}} coding |
2105eae5069b
Describe Far-Eastern DOS terminal support.
Eli Zaretskii <eliz@gnu.org>
parents:
24564
diff
changeset
|
645 systems, and thus their initial mode line looks like on Unix. |
24095 | 646 |
647 Since the codepage number also indicates which script you are using, | |
648 Emacs automatically runs @code{set-language-environment} to select the | |
649 language environment for that script (@pxref{Language Environments}). | |
650 | |
651 If a buffer contains a character belonging to some other ISO 8859 | |
652 character set, not the one that the chosen DOS codepage supports, Emacs | |
653 displays it using a sequence of ASCII characters. For example, if the | |
654 current codepage doesn't have a glyph for the letter @samp{@`o} (small | |
655 @samp{o} with a grave accent), it is displayed as @samp{@{`o@}}, where | |
656 the braces serve as a visual indication that this is a single character. | |
657 (This may look awkward for some non-Latin characters, such as those from | |
658 Greek or Hebrew alphabets, but it is still readable by a person who | |
659 knows the language.) Even though the character may occupy several | |
660 columns on the screen, it is really still just a single character, and | |
661 all Emacs commands treat it as one. | |
662 | |
663 @vindex dos-unsupported-character-glyph | |
664 Not all characters in DOS codepages correspond to ISO 8859 | |
665 characters---some are used for other purposes, such as box-drawing | |
666 characters and other graphics. Emacs cannot represent these characters | |
667 internally, so when you read a file that uses these characters, they are | |
668 converted into a particular character code, specified by the variable | |
669 @code{dos-unsupported-character-glyph}. | |
670 | |
671 Emacs supports many other characters sets aside from ISO 8859, but it | |
672 cannot display them on MS-DOS. So if one of these multibyte characters | |
24113
fd1968847853
(MS-DOS and MULE): dos-unsupported-character-glyph is
Eli Zaretskii <eliz@gnu.org>
parents:
24096
diff
changeset
|
673 appears in a buffer, Emacs on MS-DOS displays them as specified by the |
fd1968847853
(MS-DOS and MULE): dos-unsupported-character-glyph is
Eli Zaretskii <eliz@gnu.org>
parents:
24096
diff
changeset
|
674 @code{dos-unsupported-character-glyph} variable; by default, this glyph |
fd1968847853
(MS-DOS and MULE): dos-unsupported-character-glyph is
Eli Zaretskii <eliz@gnu.org>
parents:
24096
diff
changeset
|
675 is an empty triangle. Use the @kbd{C-u C-x =} command to display the |
fd1968847853
(MS-DOS and MULE): dos-unsupported-character-glyph is
Eli Zaretskii <eliz@gnu.org>
parents:
24096
diff
changeset
|
676 actual code and character set of such characters. @xref{Position Info}. |
24095 | 677 |
678 @findex codepage-setup | |
679 By default, Emacs defines a coding system to support the current | |
680 codepage. To define a coding system for some other codepage (e.g., to | |
681 visit a file written on a DOS machine in another country), use the | |
682 @kbd{M-x codepage-setup} command. It prompts for the 3-digit code of | |
683 the codepage, with completion, then creates the coding system for the | |
684 specified codepage. You can then use the new coding system to read and | |
685 write files, but you must specify it explicitly for the file command | |
686 when you want to use it (@pxref{Specify Coding}). | |
687 | |
688 These coding systems are also useful for visiting a file encoded using | |
689 a DOS codepage, using Emacs running on some other operating system. | |
690 | |
691 @node MS-DOS Processes | |
692 @section Subprocesses on MS-DOS | |
693 | |
694 @cindex compilation under MS-DOS | |
695 @cindex inferior processes under MS-DOS | |
696 @findex compile @r{(MS-DOS)} | |
697 @findex grep @r{(MS-DOS)} | |
698 Because MS-DOS is a single-process ``operating system,'' | |
699 asynchronous subprocesses are not available. In particular, Shell | |
700 mode and its variants do not work. Most Emacs features that use | |
701 asynchronous subprocesses also don't work on MS-DOS, including | |
31060
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
702 Shell mode and GUD. When in doubt, try and see; commands that |
24095 | 703 don't work print an error message saying that asynchronous processes |
704 aren't supported. | |
705 | |
706 Compilation under Emacs with @kbd{M-x compile}, searching files with | |
707 @kbd{M-x grep} and displaying differences between files with @kbd{M-x | |
708 diff} do work, by running the inferior processes synchronously. This | |
709 means you cannot do any more editing until the inferior process | |
710 finishes. | |
711 | |
31060
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
712 Spell checking also works, by means of special support for synchronous |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
713 invocation of the @code{ispell} program. This is slower than the |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
714 asynchronous invocation on Unix. |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
715 |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
716 Instead of the Shell mode, which doesn't work on MS-DOS, you can use |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
717 the @kbd{M-x eshell} command. This invokes the Eshell package that |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
718 implements a Unix-like shell entirely in Emacs Lisp. |
d24cddac1e33
Document that ispell works, and mention Eshell as an alternative
Eli Zaretskii <eliz@gnu.org>
parents:
31057
diff
changeset
|
719 |
24095 | 720 By contrast, Emacs compiled as native Windows application |
721 @strong{does} support asynchronous subprocesses. @xref{Windows | |
722 Processes}. | |
723 | |
724 @cindex printing under MS-DOS | |
725 Printing commands, such as @code{lpr-buffer} (@pxref{Hardcopy}) and | |
27213 | 726 @code{ps-print-buffer} (@pxref{PostScript}), work in MS-DOS by sending |
24095 | 727 the output to one of the printer ports. @xref{MS-DOS Printing}. |
728 | |
729 When you run a subprocess synchronously on MS-DOS, make sure the | |
730 program terminates and does not try to read keyboard input. If the | |
731 program does not terminate on its own, you will be unable to terminate | |
732 it, because MS-DOS provides no general way to terminate a process. | |
733 Pressing @kbd{C-c} or @kbd{C-@key{BREAK}} might sometimes help in these | |
734 cases. | |
735 | |
736 Accessing files on other machines is not supported on MS-DOS. Other | |
737 network-oriented commands such as sending mail, Web browsing, remote | |
738 login, etc., don't work either, unless network access is built into | |
739 MS-DOS with some network redirector. | |
740 | |
741 @cindex directory listing on MS-DOS | |
742 @vindex dired-listing-switches @r{(MS-DOS)} | |
743 Dired on MS-DOS uses the @code{ls-lisp} package where other | |
744 platforms use the system @code{ls} command. Therefore, Dired on | |
745 MS-DOS supports only some of the possible options you can mention in | |
746 the @code{dired-listing-switches} variable. The options that work are | |
747 @samp{-A}, @samp{-a}, @samp{-c}, @samp{-i}, @samp{-r}, @samp{-S}, | |
748 @samp{-s}, @samp{-t}, and @samp{-u}. | |
749 | |
750 @node Windows Processes | |
751 @section Subprocesses on Windows 95 and NT | |
752 | |
753 Emacs compiled as a native Windows application (as opposed to the DOS | |
754 version) includes full support for asynchronous subprocesses. | |
755 In the Windows version, synchronous and asynchronous subprocesses work | |
756 fine on both | |
757 Windows 95 and Windows NT as long as you run only 32-bit Windows | |
758 applications. However, when you run a DOS application in a subprocess, | |
759 you may encounter problems or be unable to run the application at all; | |
760 and if you run two DOS applications at the same time in two | |
761 subprocesses, you may have to reboot your system. | |
762 | |
763 Since the standard command interpreter (and most command line utilities) | |
764 on Windows 95 are DOS applications, these problems are significant when | |
765 using that system. But there's nothing we can do about them; only | |
766 Microsoft can fix them. | |
767 | |
768 If you run just one DOS application subprocess, the subprocess should | |
769 work as expected as long as it is ``well-behaved'' and does not perform | |
770 direct screen access or other unusual actions. If you have a CPU | |
771 monitor application, your machine will appear to be 100% busy even when | |
772 the DOS application is idle, but this is only an artifact of the way CPU | |
773 monitors measure processor load. | |
774 | |
775 You must terminate the DOS application before you start any other DOS | |
776 application in a different subprocess. Emacs is unable to interrupt or | |
777 terminate a DOS subprocess. The only way you can terminate such a | |
778 subprocess is by giving it a command that tells its program to exit. | |
779 | |
780 If you attempt to run two DOS applications at the same time in separate | |
781 subprocesses, the second one that is started will be suspended until the | |
782 first one finishes, even if either or both of them are asynchronous. | |
783 | |
784 If you can go to the first subprocess, and tell it to exit, the second | |
785 subprocess should continue normally. However, if the second subprocess | |
786 is synchronous, Emacs itself will be hung until the first subprocess | |
787 finishes. If it will not finish without user input, then you have no | |
788 choice but to reboot if you are running on Windows 95. If you are | |
789 running on Windows NT, you can use a process viewer application to kill | |
790 the appropriate instance of ntvdm instead (this will terminate both DOS | |
791 subprocesses). | |
792 | |
793 If you have to reboot Windows 95 in this situation, do not use the | |
794 @code{Shutdown} command on the @code{Start} menu; that usually hangs the | |
795 system. Instead, type @kbd{CTL-ALT-@key{DEL}} and then choose | |
796 @code{Shutdown}. That usually works, although it may take a few minutes | |
797 to do its job. | |
798 | |
799 @node Windows System Menu | |
800 @section Using the System Menu on Windows | |
801 | |
802 Emacs compiled as a native Windows application normally turns off the | |
803 Windows feature that tapping the @key{ALT} | |
804 key invokes the Windows menu. The reason is that the @key{ALT} also | |
805 serves as @key{META} in Emacs. When using Emacs, users often press the | |
806 @key{META} key temporarily and then change their minds; if this has the | |
807 effect of bringing up the Windows menu, it alters the meaning of | |
808 subsequent commands. Many users find this frustrating. | |
809 | |
810 @vindex w32-pass-alt-to-system | |
811 You can reenable Windows's default handling of tapping the @key{ALT} key | |
812 by setting @code{w32-pass-alt-to-system} to a non-@code{nil} value. | |
813 |