http:^^www.cs.washington.edu^homes^voelker^ntemacs.html

来自「This data set contains WWW-pages collect」· HTML 代码 · 共 1,495 行 · 第 1/5 页

</dl>

<hr>
<h3><a name="subproc">Subprocesses under Emacs</h3>

Emacs on NT and Win95 can utilize subprocesses just like Unix Emacs.
However, the behavior of subprocesses with Emacs may be unintuitive in
some situations.  This section discusses these situations, and how you
might work around them. <p>

<h4><a name="subproc-console">Programs reading input hang</h4>

Programs that explicitly use a handle to the console ("CON" or "CON:")
instead of stdin and stdout cannot be used as subprocesses to Emacs,
and they will also not work in shell-mode (the default ftp clients on
Win95 and NT are examples of such programs).  There is no convenient
way for either Emacs or any shell used in shell-mode to redirect the
input and output of such processes from the console to input and
output pipes.  The only workaround is to use a different
implementation of the program that does not use the console directly
(see the discussion on <!WA113><!WA113><!WA113><a href="#ange-ftp">ange-ftp</a> for a
replacement for the default ftp clients). <p>

<h4><a name="subproc-buffer">Buffering in shells</h4>

You may notice that some programs, when run in a shell in shell-mode,
have their output buffered (e.g., people have found this happening to
them with sql-mode).  When the program has a lot of output, it
overflows the buffering and gets printed to the shell buffer; however,
if the program only outputs a small amount of text, it will remain
buffered and won't appear in the shell buffer. <p>

Although it may at first seem like the shell is buffering the output
from the program, it is actually the program that is buffering output.
The C runtime typically decides how to buffer output based upon
whether stdout is bound to a handle to a console window or not.  If
bound to a console window, output is buffered line by line; if bound
to a block device, such as a file, output is buffered block by block. <p>

In a shell buffer, stdout is a pipe handle and so is buffered in
blocks.  If you would like the buffering behavior of your program to
behave differently, the program itself is going to have to be changed;
you can use setbuf and setvbuf to manipulate the buffering semantics.
<p>

<h4><a name="subproc-dos">DOS subprocesses</h4>

You can run DOS subprocesses under Emacs, but with the limitation that
you run only one at a time.  The implication of this is that, if you
use command.com under Win95 as your shell, then you can only run one
shell process at a time (command.com is still a DOS process even under
Win95).  You can use other shells, such as bash, tcsh, or 4NT, instead
of command.com; see the <!WA114><!WA114><!WA114><a href="#other-tools">section below on other
tools</a> for pointers to other sites. <p>

Andrew Innes is working on removing this limitation.  If all goes
well, it should be available in 19.35. <p>

<hr>
<h3><a name="shell">How do I use a shell in Emacs?</h3>

You can use an interactive subshell in Emacs by typing "M-x shell".
Emacs uses the SHELL configuration variable to determine which program
to use as the shell.  If you installed Emacs using the addpm.exe
program, then addpm.exe will associate the value %COMSPEC% with SHELL
in the registry.  Emacs will then use the value of the COMSPEC
environment variable when it starts up, <i>unless</i> the SHELL
environment variable is explicitly defined (as when using the
emacs.bat batch file). <p>

If you would like to specify a different shell for Emacs to use, then
you should do one of two things.  You should either explicitly set the
environment variable SHELL to be the shell you want to use, or, if you
want to have the COMSPEC environment variable determine the shell,
then you need to install Emacs using the addpm.exe program and ensure
that the SHELL environment variable is <i>not</i> defined when you
start up Emacs. <p>

<h4><a name="shell-echo">How do I prevent shell commands from being echoed?</h4>

Some shells echo the commands that you send to them, and the echoed
commands appear in the output buffer.  In particular, the default
shells, command.com on Win95 and cmd.exe on NT, have this
behavior. <p>

To prevent echoed commands from being printed, you can place the
following in your startup file: <p>

<blockquote><pre>
(setq comint-process-echoes t)
</pre></blockquote>

If shell-mode still is not stripping echoed commands, then you'll have
to explicitly tell the shell to not echo commands.  You can do this by
setting the <tt>explicit-<i>SHELL</i>-args</tt> variable
appropriately, where <tt><i>SHELL</i></tt> is the value of your shell
environment variable (do a "M-: (getenv "SHELL")" to see what it is
currently set to).  Assuming that you are on NT and that your SHELL
environment variable is set to cmd.exe, then placing the following in
your startup file will tell cmd.exe to not echo commands: <p>

<blockquote><pre>
(setq explicit-cmd.exe-args '("/q"))
</pre></blockquote>

The comint package will use the value of this variable as an argument
to cmd.exe every time it starts up a new shell (as in shell-mode); the
<tt>/q</tt> is the argument to cmd.exe that stops the echoing (in a
shell, invoking "cmd /?" will show you all of the command line
arguments to cmd.exe).  <p>

Note that this variable is case sensitive; if the value of your SHELL
environment variable is CMD.EXE instead, then this variable needs to
be named <tt>explicit-CMD.EXE-args</tt> instead. <p>

<h4><a name="shell-command_com">Why is a "Specified COMMAND search directory bad" message printed?</h4>

The function <tt>shell</tt> in shell.el automatically invokes the
shell program with the argument "-i", and parses this as the directory
in which the shell program resides (which, of course, is invalid).  To
prevent this message from being printed, you can create a variable
named according to the form specified in the help message of
<tt>shell</tt> (to look at the help message, type "C-h f shell").  For
the default shells, then, you could place the following in your
startup file to prevent this message (these will eventually get into
winnt.el so you don't have to do this):

<blockquote><pre>
(setq explicit-command.com-args nil)
(setq explicit-COMMAND.COM-args nil)
(setq explicit-cmd.exe-args nil)
(setq explicit-CMD.EXE-args nil)
</pre></blockquote>

Multiple lines for each shell are given since variable names are case
sensitive and shell names can be any case (so this only handles the
most common situations).  If you have an entirely different shell that
also complains about being given the "-i" switch, you can initialize a
similarly named variable to prevent the "-i" switch from being sent to
the shell. <p>

Note that, if you would like to always pass arguments to an
interactive shell when it starts up, you would change the nil value in
the appropriate assignment above to the list of arguments you would
like to use with your shell.  For example, if you would like to invoke
command.com and tell it which directory its executable resides, you
could place something like the following in your startup file: <p>

<blockquote><pre>
;; Determine the directory containing the shell program, explicitly making
;; certain that the directory separator is a backslash when doing so.
(let ((directory-sep-char ?\\))
  (setq shell-directory (file-name-directory (getenv "SHELL"))))

(setq explicit-command.com-args (list shell-directory))
(setq explicit-COMMAND.COM-args (list shell-directory))
</pre></blockquote>

<h4><a name="shell-invalid">When I run programs within a shell I get
"Incorrect DOS version" messages.  Why?</h4>

This might happen if, for example, you invoke nmake in a shell and it
tries to create subshells.  The problem is related to the one above
where, again, when the shell is initially created, the first argument
to the shell is not the directory in which the shell program resides.
When this happens, command.com fabricates a value for its COMSPEC
environment variable that is incorrect.  Then, when other programs go
to use COMSPEC to find the shell, they are given the wrong value. <p>

The fix for this is to either prevent any arguments from being sent to
the shell when it starts up (in which case command.com will use a
default, and correct, value for COMSPEC), or to have the first
argument be the directory in which the shell executable resides.
Examples of how to do both of these are in shown in the <!WA115><!WA115><!WA115><a
href="#shell-command_com">previous subsection</a>. <p>

<hr>
<h3><a name="mail">How do I use mail with Emacs?</h3>

You do not need to do much to use mail with Emacs under Win32, but you
do need to be able to communicate with local mail daemons and mail
servers (they do most of the work) to both receive and send mail from
your system.  These daemons and servers are typically running on the
machines in your local network that are already handling mail for you
and/or other users on other systems. <p>

I've only tested the outgoing and incoming RMAIL setups.  If you find
that the suggested code for any of the other incoming mail
configurations is inaccurate, please let me know. <p>

<h4><a name="mail-outgoing">Outgoing</h4>

For outgoing mail, you need an elisp file, <!WA116><!WA116><!WA116><a
href="http://www.cs.washington.edu/homes/voelker/ntemacs/contrib/smtpmail.el">smtpmail.el</a>, that enables Emacs
to talk SMTP with mail daemons (smtpmail.el was written by Tomoji
Kagatani &[e-mail]&gt and has been submitted to
be included in future distributions).  You also need to add the
following to your startup file (be sure to customize for you and your
system): <p>

<blockquote><pre>
(setq user-full-name <i>"Your full name"</i>)
(setq user-mail-address <i>"Your email address"</i>)

(setq smtpmail-default-smtp-server <i>"Domain name of machine with SMTP server"</i>)
(setq smtpmail-local-domain nil)
(setq send-mail-function 'smtpmail-send-it)

(load-library "smtpmail")
</pre></blockquote>

<h4><a name="mail-rmail">Incoming: RMAIL and POP3</h4>

For incoming mail using the RMAIL package and a POP3 mail server, you
need only place the following in your startup file (again, be sure to
customize): <p>

<blockquote><pre>
(setenv "MAILHOST" <i>"Domain name of machine with POP3 server"</i>)
(setq rmail-primary-inbox-list '("po:<i>Your login</i>") rmail-pop-password-required t)
</pre></blockquote>

Note that you will need to customize the <i>Domain name of machine
with POP3 server</i> and <i>Your login</i> fields to be the name of
your POP server and your login name. <p>

<h4><a name="mail-vm-pop3">Incoming: VM and POP3</h4>

For incoming mail using the VM package and a POP3 mail server, you
first need the vm package (check any elisp archive) and then you need
to place the following in your .vm configuration file: <p>

<blockquote><pre>
(setq vm-spool-files 
      (list 
       (list "~/INBOX"
             "<i>POP3 server</i>:110:pass:<i>POP user name</i>:<i>*</i>"
             "~/INBOX.CRASH")))
</pre></blockquote>

Note that you will need to customize the <i>POP3 server</i> and <i>POP
user name</i> fields to be your login name and the name of your POP
server.  You will also probably want to customize the name of your
inbox and crash files (<tt>~/INBOX</tt> and <tt>~/INBOX.CRASH</tt> in
the example above.) <p>

<h4><a name="mail-gnus">Incoming: GNUS</h4>

You should be able to use Gnus 5.2 and above as a mail reader.  The
following was sent as an example by Marc Fleischeuers
&[e-mail]&gt:

<blockquote><pre>
;; For sending mail
(setq message-send-mail-function 'smtpmail-send-it)

;; For reading mail (other backends can be substituted for nnml)
(setq gnus-secondary-select-methods '((nnml "")))
(setq nnmail-spool-file "po:<i>POP user name</i>")
(setq nnmail-pop-password-required t)
</pre></blockquote>

Be sure to customize the <i>POP user name</i> field appropriately. <p>

<h4><a name="mail-tm">tm</h4>

I don't know of any complete ports of tm to the Win32 environment, but
Fabrice POPINEAU &[e-mail]&gt has made some
modifications to the OS2 version of tm.  See <!WA117><!WA117><!WA117><a
href="http://www.cs.washington.edu/homes/voelker/ntemacs/contrib/tm-support">his description</a> of what he has
done for more info.  The support programs mentioned can be found in <!WA118><!WA118><!WA118><a
href="http://www.cs.washington.edu/homes/voelker/ntemacs/contrib/mm.zip">mm.zip</a> (note that they have only
been tested on NT 4.0, though). <p>

<hr>
<h3><a name="ange-ftp">How do I use ange-ftp with Emacs?</h3>

You will need some additional files before ange-ftp will work with
Emacs.  Partly this is due to the unfortunate fact that the ftp
program shipped with Win95 and NT does not accept a password from a
pipe or a redirected file, and partly this is due to some
incompatibilities in the ange-ftp.el lisp file when used on
Windows. <p>

Chris Szurgot &[e-mail]&gt has been working on both of
these problems.  He has a version of ftp that solves the password
problem, and a version of ange-ftp that deals with the
incompatibilities.  You can find both on his ftp server: <p>

<ul>
<li><!WA119><!WA119><!WA119><a href="ftp://ftp.itribe.net/pub/virtunix/ftp.zip">ftp://ftp.itribe.net/pub/virtunix/ftp.zip</a>
<li><!WA120><!WA120><!WA120><a href="http://www.itribe.net/virtunix/files/emacs/ange-ftp.el">http://www.itribe.net/virtunix/files/emacs/ange-ftp.el</a>
</ul>


Place the ftp.exe executable in a directory where you keep your local
executables, and the ange-ftp.el file in whatever directory you keep
custom and personalized elisp files (you will probably also w