comparison lispref/processes.texi @ 82406:f59dca8510d0

(Asynchronous Processes): Clarify doc of start-file-process.
author Richard M. Stallman <rms@gnu.org>
date Thu, 16 Aug 2007 02:22:40 +0000
parents 38bfa1de0aca
children aaccdab0ee26
comparison
equal deleted inserted replaced
82405:907505b33af3 82406:f59dca8510d0
501 @end smallexample 501 @end smallexample
502 @end defun 502 @end defun
503 503
504 @defun start-file-process name buffer-or-name program &rest args 504 @defun start-file-process name buffer-or-name program &rest args
505 Like @code{start-process}, this function starts a new asynchronous 505 Like @code{start-process}, this function starts a new asynchronous
506 subprocess running @var{program} in it. The corresponding process 506 subprocess running @var{program} in it, and returns its process
507 object is returned. 507 object---when @code{default-directory} is not a magic file name.
508 508
509 If @code{default-directory} corresponds to a file handler, that 509 If @code{default-directory} is magic, the function invokes its file
510 handler is invoked. @var{program} runs then on a remote host which is 510 handler instead. This handler ought to run @var{program}, perhaps on
511 identified by @code{default-directory}. The local part of 511 the local host, perhaps on a remote host that corresponds to
512 @code{default-directory} is the working directory of the subprocess. 512 @code{default-directory}. In the latter case, the local part of
513 513 @code{default-directory} becomes the working directory of the process.
514 @var{program} and @var{program-args} might be file names. They are not 514
515 objects of file handler invocation. 515 This function does not try to invoke file name handlers for
516 @var{program} or for the @var{program-args}.
516 517
517 Depending on the implementation of the file handler, it might not be 518 Depending on the implementation of the file handler, it might not be
518 possible to apply @code{process-filter} or @code{process-sentinel} to 519 possible to apply @code{process-filter} or @code{process-sentinel} to
519 the resulting process object (@pxref{Filter Functions}, @pxref{Sentinels}). 520 the resulting process object (@pxref{Filter Functions}, @pxref{Sentinels}).
520 521
521 Some file handlers may not support @code{start-file-process} (for 522 Some file handlers may not support @code{start-file-process} (for
522 example @code{ange-ftp-hook-function}). It returns then @code{nil}. 523 example @code{ange-ftp-hook-function}). In such cases, the function
524 does nothing and returns @code{nil}.
523 @end defun 525 @end defun
524 526
525 @defun start-process-shell-command name buffer-or-name command &rest command-args 527 @defun start-process-shell-command name buffer-or-name command &rest command-args
526 This function is like @code{start-process} except that it uses a shell 528 This function is like @code{start-process} except that it uses a shell
527 to execute the specified command. The argument @var{command} is a shell 529 to execute the specified command. The argument @var{command} is a shell