Commit | Line | Data |
---|---|---|
ca2565b0 | 1 | @c This is part of the Emacs manual. |
b65d8176 | 2 | @c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2000, 2001, |
8d99e09d | 3 | @c 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. |
ca2565b0 | 4 | @c See file emacs.texi for copying conditions. |
e691d082 KB |
5 | @node Emacs and Microsoft Windows, Manifesto, Mac OS, Top |
6 | @appendix Emacs and Microsoft Windows | |
c6b30bd2 | 7 | @cindex Microsoft Windows |
270c6692 | 8 | @cindex MS-Windows, Emacs peculiarities |
ca2565b0 | 9 | |
e691d082 | 10 | This section describes peculiarities of using Emacs on Microsoft |
270c6692 EZ |
11 | Windows. Some of these peculiarities are also relevant to Microsoft's |
12 | older MS-DOS ``operating system'' (also known as ``MS-DOG''). | |
13 | However, Emacs features that are relevant @emph{only} to MS-DOS are | |
fb041819 | 14 | described in a separate manual (@inforef{MS-DOG,, emacs-xtra}). |
ca2565b0 | 15 | |
270c6692 EZ |
16 | The behavior of Emacs on MS-Windows is reasonably similar to what is |
17 | documented in the rest of the manual, including support for long file | |
18 | names, multiple frames, scroll bars, mouse menus, and subprocesses. | |
19 | However, a few special considerations apply, and they are described | |
20 | here. | |
ca2565b0 AI |
21 | |
22 | @menu | |
e691d082 | 23 | * Text and Binary:: Text files use CRLF to terminate lines. |
270c6692 EZ |
24 | * Windows Files:: File-name conventions on Windows. |
25 | * Windows HOME:: Where Emacs looks for your @file{.emacs}. | |
ca2565b0 | 26 | * Windows Processes:: Running subprocesses on Windows. |
270c6692 | 27 | * Windows Printing:: How to specify the printer on MS-Windows. |
ca2565b0 AI |
28 | * Windows System Menu:: Controlling what the ALT key does. |
29 | @end menu | |
30 | ||
ca2565b0 AI |
31 | @node Text and Binary |
32 | @section Text Files and Binary Files | |
33 | @cindex text and binary files on MS-DOS/MS-Windows | |
34 | ||
35 | GNU Emacs uses newline characters to separate text lines. This is the | |
270c6692 | 36 | convention used on GNU, Unix, and other Posix-compliant systems. |
ca2565b0 AI |
37 | |
38 | @cindex end-of-line conversion on MS-DOS/MS-Windows | |
270c6692 EZ |
39 | By contrast, MS-DOS and MS-Windows normally use carriage-return linefeed, |
40 | a two-character sequence, to separate text lines. (Linefeed is the same | |
ca2565b0 AI |
41 | character as newline.) Therefore, convenient editing of typical files |
42 | with Emacs requires conversion of these end-of-line (EOL) sequences. | |
43 | And that is what Emacs normally does: it converts carriage-return | |
44 | linefeed into newline when reading files, and converts newline into | |
45 | carriage-return linefeed when writing files. The same mechanism that | |
46 | handles conversion of international character codes does this conversion | |
47 | also (@pxref{Coding Systems}). | |
48 | ||
1ca54e68 EZ |
49 | @cindex cursor location, on MS-DOS |
50 | @cindex point location, on MS-DOS | |
ca2565b0 AI |
51 | One consequence of this special format-conversion of most files is |
52 | that character positions as reported by Emacs (@pxref{Position Info}) do | |
53 | not agree with the file size information known to the operating system. | |
54 | ||
ca2565b0 AI |
55 | In addition, if Emacs recognizes from a file's contents that it uses |
56 | newline rather than carriage-return linefeed as its line separator, it | |
8e375db2 RS |
57 | does not perform EOL conversion when reading or writing that file. |
58 | Thus, you can read and edit files from GNU and Unix systems on MS-DOS | |
59 | with no special effort, and they will retain their Unix-style | |
60 | end-of-line convention after you edit them. | |
ca2565b0 | 61 | |
ca2565b0 | 62 | The mode line indicates whether end-of-line translation was used for |
1ca54e68 | 63 | the current buffer. If MS-DOS end-of-line translation is in use for the |
270c6692 EZ |
64 | buffer, the MS-Windows build of Emacs displays a backslash @samp{\} after |
65 | the coding system mnemonic near the beginning of the mode line | |
66 | (@pxref{Mode Line}). If no EOL translation was performed, the string | |
67 | @samp{(Unix)} is displayed instead of the backslash, to alert you that the | |
68 | file's EOL format is not the usual carriage-return linefeed. | |
1ca54e68 EZ |
69 | |
70 | @cindex DOS-to-Unix conversion of files | |
8e375db2 | 71 | To visit a file and specify whether it uses DOS-style or Unix-style |
fef4d6a6 | 72 | end-of-line, specify a coding system (@pxref{Text Coding}). For |
8e375db2 RS |
73 | example, @kbd{C-x @key{RET} c unix @key{RET} C-x C-f foobar.txt} |
74 | visits the file @file{foobar.txt} without converting the EOLs; if some | |
75 | line ends with a carriage-return linefeed pair, Emacs will display | |
76 | @samp{^M} at the end of that line. Similarly, you can direct Emacs to | |
77 | save a buffer in a specified EOL format with the @kbd{C-x @key{RET} f} | |
78 | command. For example, to save a buffer with Unix EOL format, type | |
79 | @kbd{C-x @key{RET} f unix @key{RET} C-x C-s}. If you visit a file | |
80 | with DOS EOL conversion, then save it with Unix EOL format, that | |
81 | effectively converts the file to Unix EOL style, like @code{dos2unix}. | |
ca2565b0 AI |
82 | |
83 | @cindex untranslated file system | |
84 | @findex add-untranslated-filesystem | |
270c6692 EZ |
85 | When you use NFS, Samba, or some other similar method to access file |
86 | systems that reside on computers using GNU or Unix systems, Emacs | |
87 | should not perform end-of-line translation on any files in these file | |
88 | systems---not even when you create a new file. To request this, | |
89 | designate these file systems as @dfn{untranslated} file systems by | |
90 | calling the function @code{add-untranslated-filesystem}. It takes one | |
91 | argument: the file system name, including a drive letter and | |
92 | optionally a directory. For example, | |
ca2565b0 AI |
93 | |
94 | @example | |
95 | (add-untranslated-filesystem "Z:") | |
96 | @end example | |
97 | ||
98 | @noindent | |
99 | designates drive Z as an untranslated file system, and | |
100 | ||
101 | @example | |
102 | (add-untranslated-filesystem "Z:\\foo") | |
103 | @end example | |
104 | ||
105 | @noindent | |
106 | designates directory @file{\foo} on drive Z as an untranslated file | |
107 | system. | |
108 | ||
109 | Most often you would use @code{add-untranslated-filesystem} in your | |
270c6692 | 110 | @file{.emacs} file, or in @file{site-start.el} so that all the users at |
ca2565b0 AI |
111 | your site get the benefit of it. |
112 | ||
113 | @findex remove-untranslated-filesystem | |
114 | To countermand the effect of @code{add-untranslated-filesystem}, use | |
115 | the function @code{remove-untranslated-filesystem}. This function takes | |
116 | one argument, which should be a string just like the one that was used | |
117 | previously with @code{add-untranslated-filesystem}. | |
118 | ||
8e375db2 RS |
119 | Designating a file system as untranslated does not affect character |
120 | set conversion, only end-of-line conversion. Essentially, it directs | |
121 | Emacs to create new files with the Unix-style convention of using | |
122 | newline at the end of a line. @xref{Coding Systems}. | |
1ca54e68 EZ |
123 | |
124 | @vindex file-name-buffer-file-type-alist | |
125 | @cindex binary files, on MS-DOS/MS-Windows | |
126 | Some kinds of files should not be converted at all, because their | |
270c6692 | 127 | contents are not really text. Therefore, Emacs on MS-Windows distinguishes |
1ca54e68 | 128 | certain files as @dfn{binary files}. (This distinction is not part of |
270c6692 | 129 | MS-Windows; it is made by Emacs only.) Binary files include executable |
1ca54e68 EZ |
130 | programs, compressed archives, etc. Emacs uses the file name to decide |
131 | whether to treat a file as binary: the variable | |
132 | @code{file-name-buffer-file-type-alist} defines the file-name patterns | |
133 | that indicate binary files. If a file name matches one of the patterns | |
134 | for binary files (those whose associations are of the type | |
135 | @code{(@var{pattern} . t)}, Emacs reads and writes that file using the | |
136 | @code{no-conversion} coding system (@pxref{Coding Systems}) which turns | |
137 | off @emph{all} coding-system conversions, not only the EOL conversion. | |
138 | @code{file-name-buffer-file-type-alist} also includes file-name patterns | |
270c6692 | 139 | for files which are known to be Windows-style text files with |
1ca54e68 | 140 | carriage-return linefeed EOL format, such as @file{CONFIG.SYS}; Emacs |
270c6692 | 141 | always writes those files with Windows-style EOLs. |
1ca54e68 EZ |
142 | |
143 | If a file which belongs to an untranslated file system matches one of | |
144 | the file-name patterns in @code{file-name-buffer-file-type-alist}, the | |
145 | EOL conversion is determined by @code{file-name-buffer-file-type-alist}. | |
146 | ||
270c6692 EZ |
147 | @node Windows Files |
148 | @section File Names on MS-Windows | |
149 | @cindex file names on MS-Windows | |
150 | ||
151 | MS-Windows and MS-DOS normally use a backslash, @samp{\}, to | |
152 | separate name units within a file name, instead of the slash used on | |
153 | other systems. Emacs on MS-DOS/MS-Windows permits use of either slash or | |
154 | backslash, and also knows about drive letters in file names. | |
155 | ||
156 | @cindex file-name completion, on MS-Windows | |
157 | On MS-DOS/MS-Windows, file names are case-insensitive, so Emacs by | |
158 | default ignores letter-case in file names during completion. | |
159 | ||
160 | @node Windows HOME | |
161 | @section HOME Directory on MS-Windows | |
162 | @cindex @code{HOME} directory on MS-Windows | |
163 | ||
164 | The MS-Windows equivalent of the @code{HOME} directory is the | |
165 | @dfn{user-specific application data directory}. The actual location | |
166 | depends on your Windows version and system configuration; typical values | |
167 | are @file{C:\Documents and Settings\@var{username}\Application Data} on | |
168 | Windows 2K/XP and later, and either @file{C:\WINDOWS\Application Data} | |
169 | or @file{C:\WINDOWS\Profiles\@var{username}\Application Data} on the | |
170 | older Windows 9X/ME systems. | |
171 | ||
172 | @cindex init file @file{.emacs} on MS-Windows | |
173 | The home directory is where your init file @file{.emacs} is stored. | |
174 | When Emacs starts, it first checks whether the environment variable | |
175 | @env{HOME} is set. If it is, it looks for the init file in the | |
176 | directory pointed by @env{HOME}. If @env{HOME} is not defined, Emacs | |
177 | checks for an existing @file{.emacs} file in @file{C:\}, the root | |
178 | directory of drive @file{C:}@footnote{ | |
179 | The check in @file{C:\} is in preference to the application data | |
180 | directory for compatibility with older versions of Emacs, which didn't | |
181 | check the application data directory. | |
182 | }. If there's no such file in @file{C:\}, Emacs next uses the Windows | |
183 | system calls to find out the exact location of your application data | |
184 | directory. If that fails as well, Emacs falls back to @file{C:\}. | |
185 | ||
186 | Whatever the final place is, Emacs sets the value of the @env{HOME} | |
187 | environment variable to point to it, and it will use that location for | |
188 | other files and directories it normally creates in the user's home | |
189 | directory. | |
190 | ||
191 | You can always find out where Emacs thinks is your home directory's | |
192 | location by typing @kbd{C-x d ~/ @key{RET}}. This should present the | |
193 | list of files in the home directory, and show its full name on the | |
194 | first line. Likewise, to visit your init file, type @kbd{C-x C-f | |
195 | ~/.emacs @key{RET}}. | |
196 | ||
197 | @cindex @file{_emacs} init file, MS-Windows | |
198 | Because MS-DOS does not allow file names with leading dots, and | |
199 | because older Windows systems made it hard to create files with such | |
200 | names, the Windows port of Emacs supports an alternative name | |
201 | @file{_emacs} as a fallback, if such a file exists in the home | |
202 | directory, whereas @file{.emacs} does not. | |
203 | ||
ca2565b0 | 204 | @node Windows Processes |
270c6692 EZ |
205 | @section Subprocesses on Windows 9X/ME and Windows NT/2K/XP |
206 | @cindex subprocesses on MS-Windows | |
ca2565b0 | 207 | |
270c6692 | 208 | @cindex DOS applications, running from Emacs |
049224f6 | 209 | Emacs compiled as a native Windows application (as opposed to the DOS |
ca2565b0 AI |
210 | version) includes full support for asynchronous subprocesses. |
211 | In the Windows version, synchronous and asynchronous subprocesses work | |
212 | fine on both | |
270c6692 | 213 | Windows 9X/ME and Windows NT/2K/XP as long as you run only 32-bit Windows |
ca2565b0 AI |
214 | applications. However, when you run a DOS application in a subprocess, |
215 | you may encounter problems or be unable to run the application at all; | |
216 | and if you run two DOS applications at the same time in two | |
217 | subprocesses, you may have to reboot your system. | |
218 | ||
219 | Since the standard command interpreter (and most command line utilities) | |
270c6692 | 220 | on Windows 9X are DOS applications, these problems are significant when |
ca2565b0 AI |
221 | using that system. But there's nothing we can do about them; only |
222 | Microsoft can fix them. | |
223 | ||
224 | If you run just one DOS application subprocess, the subprocess should | |
225 | work as expected as long as it is ``well-behaved'' and does not perform | |
226 | direct screen access or other unusual actions. If you have a CPU | |
227 | monitor application, your machine will appear to be 100% busy even when | |
228 | the DOS application is idle, but this is only an artifact of the way CPU | |
229 | monitors measure processor load. | |
230 | ||
231 | You must terminate the DOS application before you start any other DOS | |
232 | application in a different subprocess. Emacs is unable to interrupt or | |
233 | terminate a DOS subprocess. The only way you can terminate such a | |
234 | subprocess is by giving it a command that tells its program to exit. | |
235 | ||
236 | If you attempt to run two DOS applications at the same time in separate | |
237 | subprocesses, the second one that is started will be suspended until the | |
238 | first one finishes, even if either or both of them are asynchronous. | |
239 | ||
270c6692 | 240 | @cindex kill DOS application |
ca2565b0 AI |
241 | If you can go to the first subprocess, and tell it to exit, the second |
242 | subprocess should continue normally. However, if the second subprocess | |
243 | is synchronous, Emacs itself will be hung until the first subprocess | |
244 | finishes. If it will not finish without user input, then you have no | |
ff43a665 | 245 | choice but to reboot if you are running on Windows 9X. If you are |
270c6692 EZ |
246 | running on Windows NT/2K/XP, you can use a process viewer application to kill |
247 | the appropriate instance of NTVDM instead (this will terminate both DOS | |
ca2565b0 AI |
248 | subprocesses). |
249 | ||
ff43a665 | 250 | If you have to reboot Windows 9X in this situation, do not use the |
ca2565b0 AI |
251 | @code{Shutdown} command on the @code{Start} menu; that usually hangs the |
252 | system. Instead, type @kbd{CTL-ALT-@key{DEL}} and then choose | |
253 | @code{Shutdown}. That usually works, although it may take a few minutes | |
254 | to do its job. | |
255 | ||
270c6692 EZ |
256 | @node Windows Printing |
257 | @section Printing and MS-Windows | |
258 | ||
259 | Printing commands, such as @code{lpr-buffer} (@pxref{Printing}) and | |
260 | @code{ps-print-buffer} (@pxref{PostScript}) work in MS-DOS and | |
261 | MS-Windows by sending the output to one of the printer ports, if a | |
262 | Posix-style @code{lpr} program is unavailable. The same Emacs | |
263 | variables control printing on all systems, but in some cases they have | |
264 | different default values on MS-DOS and MS-Windows. | |
265 | ||
266 | Emacs on Windows automatically determines your default printer and | |
267 | sets the variable @var{printer-name} to that printer's name. But in | |
268 | some rare cases this can fail, or you may wish to use a different | |
269 | printer from within Emacs. The rest of this section explains how to | |
270 | tell Emacs which printer to use. | |
271 | ||
272 | @vindex printer-name@r{, (MS-DOS/MW-Windows)} | |
273 | If you want to use your local printer, then set the Lisp variable | |
274 | @code{lpr-command} to @code{""} (its default value on Windows) and | |
275 | @code{printer-name} to the name of the printer port---for example, | |
276 | @code{"PRN"}, the usual local printer port or @code{"LPT2"}, or | |
277 | @code{"COM1"} for a serial printer. You can also set | |
278 | @code{printer-name} to a file name, in which case ``printed'' output | |
279 | is actually appended to that file. If you set @code{printer-name} to | |
280 | @code{"NUL"}, printed output is silently discarded (sent to the system | |
281 | null device). | |
282 | ||
283 | You can also use a printer shared by another machine by setting | |
284 | @code{printer-name} to the UNC share name for that printer---for | |
285 | example, @code{"//joes_pc/hp4si"}. (It doesn't matter whether you use | |
286 | forward slashes or backslashes here.) To find out the names of shared | |
287 | printers, run the command @samp{net view} from the command prompt to | |
288 | obtain a list of servers, and @samp{net view @var{server-name}} to see | |
289 | the names of printers (and directories) shared by that server. | |
290 | Alternatively, click the @samp{Network Neighborhood} icon on your | |
291 | desktop, and look for machines which share their printers via the | |
292 | network. | |
293 | ||
294 | @cindex @samp{net use}, and printing on MS-Windows | |
295 | @cindex networked printers (MS-Windows) | |
296 | If the printer doesn't appear in the output of @samp{net view}, or | |
297 | if setting @code{printer-name} to the UNC share name doesn't produce a | |
298 | hardcopy on that printer, you can use the @samp{net use} command to | |
299 | connect a local print port such as @code{"LPT2"} to the networked | |
300 | printer. For example, typing @kbd{net use LPT2: \\joes_pc\hp4si}@footnote{ | |
301 | Note that the @samp{net use} command requires the UNC share name to be | |
302 | typed with the Windows-style backslashes, while the value of | |
303 | @code{printer-name} can be set with either forward- or backslashes.} | |
304 | causes Windows to @dfn{capture} the @code{LPT2} port and redirect the | |
305 | printed material to the printer connected to the machine @code{joes_pc}. | |
306 | After this command, setting @code{printer-name} to @code{"LPT2"} | |
307 | should produce the hardcopy on the networked printer. | |
308 | ||
309 | With some varieties of Windows network software, you can instruct | |
310 | Windows to capture a specific printer port such as @code{"LPT2"}, and | |
311 | redirect it to a networked printer via the @w{@code{Control | |
312 | Panel->Printers}} applet instead of @samp{net use}. | |
313 | ||
314 | If you set @code{printer-name} to a file name, it's best to use an | |
315 | absolute file name. Emacs changes the working directory according to | |
316 | the default directory of the current buffer, so if the file name in | |
317 | @code{printer-name} is relative, you will end up with several such | |
318 | files, each one in the directory of the buffer from which the printing | |
319 | was done. | |
320 | ||
321 | @findex print-buffer @r{(MS-DOS)} | |
322 | @findex print-region @r{(MS-DOS)} | |
323 | @vindex lpr-headers-switches @r{(MS-DOS)} | |
324 | The commands @code{print-buffer} and @code{print-region} call the | |
325 | @code{pr} program, or use special switches to the @code{lpr} program, to | |
326 | produce headers on each printed page. MS-DOS and MS-Windows don't | |
327 | normally have these programs, so by default, the variable | |
328 | @code{lpr-headers-switches} is set so that the requests to print page | |
329 | headers are silently ignored. Thus, @code{print-buffer} and | |
330 | @code{print-region} produce the same output as @code{lpr-buffer} and | |
331 | @code{lpr-region}, respectively. If you do have a suitable @code{pr} | |
332 | program (for example, from GNU Coreutils), set | |
333 | @code{lpr-headers-switches} to @code{nil}; Emacs will then call | |
334 | @code{pr} to produce the page headers, and print the resulting output as | |
335 | specified by @code{printer-name}. | |
336 | ||
337 | @vindex print-region-function @r{(MS-DOS)} | |
338 | @cindex lpr usage under MS-DOS | |
339 | @vindex lpr-command @r{(MS-DOS)} | |
340 | @vindex lpr-switches @r{(MS-DOS)} | |
341 | Finally, if you do have an @code{lpr} work-alike, you can set the | |
342 | variable @code{lpr-command} to @code{"lpr"}. Then Emacs will use | |
343 | @code{lpr} for printing, as on other systems. (If the name of the | |
344 | program isn't @code{lpr}, set @code{lpr-command} to specify where to | |
345 | find it.) The variable @code{lpr-switches} has its standard meaning | |
346 | when @code{lpr-command} is not @code{""}. If the variable | |
347 | @code{printer-name} has a string value, it is used as the value for the | |
348 | @code{-P} option to @code{lpr}, as on Unix. | |
349 | ||
350 | @findex ps-print-buffer @r{(MS-DOS)} | |
351 | @findex ps-spool-buffer @r{(MS-DOS)} | |
352 | @vindex ps-printer-name @r{(MS-DOS)} | |
353 | @vindex ps-lpr-command @r{(MS-DOS)} | |
354 | @vindex ps-lpr-switches @r{(MS-DOS)} | |
355 | A parallel set of variables, @code{ps-lpr-command}, | |
356 | @code{ps-lpr-switches}, and @code{ps-printer-name} (@pxref{PostScript | |
357 | Variables}), defines how PostScript files should be printed. These | |
358 | variables are used in the same way as the corresponding variables | |
359 | described above for non-PostScript printing. Thus, the value of | |
360 | @code{ps-printer-name} is used as the name of the device (or file) to | |
361 | which PostScript output is sent, just as @code{printer-name} is used | |
362 | for non-PostScript printing. (There are two distinct sets of | |
363 | variables in case you have two printers attached to two different | |
364 | ports, and only one of them is a PostScript printer.) | |
365 | ||
366 | The default value of the variable @code{ps-lpr-command} is @code{""}, | |
367 | which causes PostScript output to be sent to the printer port specified | |
368 | by @code{ps-printer-name}, but @code{ps-lpr-command} can also be set to | |
369 | the name of a program which will accept PostScript files. Thus, if you | |
370 | have a non-PostScript printer, you can set this variable to the name of | |
371 | a PostScript interpreter program (such as Ghostscript). Any switches | |
372 | that need to be passed to the interpreter program are specified using | |
373 | @code{ps-lpr-switches}. (If the value of @code{ps-printer-name} is a | |
374 | string, it will be added to the list of switches as the value for the | |
375 | @code{-P} option. This is probably only useful if you are using | |
376 | @code{lpr}, so when using an interpreter typically you would set | |
377 | @code{ps-printer-name} to something other than a string so it is | |
378 | ignored.) | |
379 | ||
380 | For example, to use Ghostscript for printing on the system's default | |
381 | printer, put this in your @file{.emacs} file: | |
382 | ||
383 | @example | |
384 | (setq ps-printer-name t) | |
385 | (setq ps-lpr-command "D:/gs6.01/bin/gswin32c.exe") | |
386 | (setq ps-lpr-switches '("-q" "-dNOPAUSE" "-dBATCH" | |
387 | "-sDEVICE=mswinpr2" | |
388 | "-sPAPERSIZE=a4")) | |
389 | @end example | |
390 | ||
391 | @noindent | |
392 | (This assumes that Ghostscript is installed in the | |
393 | @file{D:/gs6.01} directory.) | |
394 | ||
ca2565b0 AI |
395 | @node Windows System Menu |
396 | @section Using the System Menu on Windows | |
270c6692 | 397 | @cindex @code{Alt} key invokes menu (Windows) |
ca2565b0 AI |
398 | |
399 | Emacs compiled as a native Windows application normally turns off the | |
270c6692 EZ |
400 | Windows feature that tapping the @key{ALT} key invokes the Windows |
401 | menu. The reason is that the @key{ALT} serves as @key{META} in Emacs. | |
402 | When using Emacs, users often press the @key{META} key temporarily and | |
403 | then change their minds; if this has the effect of bringing up the | |
404 | Windows menu, it alters the meaning of subsequent commands. Many | |
405 | users find this frustrating. | |
ca2565b0 AI |
406 | |
407 | @vindex w32-pass-alt-to-system | |
696c94e9 | 408 | You can re-enable Windows' default handling of tapping the @key{ALT} key |
ca2565b0 AI |
409 | by setting @code{w32-pass-alt-to-system} to a non-@code{nil} value. |
410 | ||
ab5796a9 MB |
411 | @ignore |
412 | arch-tag: f39d2590-5dcc-4318-88d9-0eb73ca10fa2 | |
413 | @end ignore |