diff options
Diffstat (limited to 'doc/lispref/processes.texi')
| -rw-r--r-- | doc/lispref/processes.texi | 29 |
1 files changed, 24 insertions, 5 deletions
diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi index e3eee3d0719..ea3fe738f69 100644 --- a/doc/lispref/processes.texi +++ b/doc/lispref/processes.texi @@ -134,7 +134,7 @@ but all the 3 primitives allow optionally to direct the standard error stream to a different destination. @cindex program arguments - All three of the subprocess-creating functions allow to specify + All three of the subprocess-creating functions allow specifying command-line arguments for the process to run. For @code{call-process} and @code{call-process-region}, these come in the form of a @code{&rest} argument, @var{args}. For @code{make-process}, both the @@ -185,6 +185,25 @@ respective remote host. In case of a local @code{default-directory}, the function returns just the value of the variable @code{exec-path}. @end defun +@cindex programs distributed with Emacs, starting +@vindex ctags-program-name +@vindex etags-program-name +@vindex hexl-program-name +@vindex emacsclient-program-name +@vindex movemail-program-name +@vindex ebrowse-program-name +@vindex rcs2log-program-name + When starting a program that is part of the Emacs distribution, you +must take into account that the program may have been renamed in order +to comply with executable naming restrictions present on the system. + + Instead of starting @command{ctags}, for example, you should specify +the value of @code{ctags-program-name} instead. Likewise, instead of +starting @command{movemail}, you must start +@code{movemail-program-name}, and the same goes for @command{etags}, +@command{hexl}, @command{emacsclient}, @code{rcs2log}, and +@command{ebrowse}. + @node Shell Arguments @section Shell Arguments @cindex arguments for shell commands @@ -501,7 +520,7 @@ This user option indicates whether a call of @code{process-file} returns a string describing the signal interrupting a remote process. When a process returns an exit code greater than 128, it is -interpreted as a signal. @code{process-file} requires to return a +interpreted as a signal. @code{process-file} requires returning a string describing this signal. Since there are processes violating this rule, returning exit codes @@ -662,7 +681,7 @@ This function is the basic low-level primitive for starting asynchronous subprocesses. It returns a process object representing the subprocess. Compared to the more high-level @code{start-process}, described below, it takes keyword arguments, is more flexible, and -allows to specify process filters and sentinels in a single call. +enables you to specify process filters and sentinels in a single call. The arguments @var{args} are a list of keyword/argument pairs. Omitting a keyword is always equivalent to specifying it with value @@ -1762,7 +1781,7 @@ program was running when the filter function was started. However, if This makes it possible to use the Lisp debugger to debug filter functions. @xref{Debugger}. If an error is caught, Emacs pauses for @code{process-error-pause-time} seconds so that the user sees the -error. @xref{Asynchronous Processes} +error. @xref{Asynchronous Processes}. Many filter functions sometimes (or always) insert the output in the process's buffer, mimicking the actions of the default filter. @@ -2168,7 +2187,7 @@ programs was running when the sentinel was started. However, if This makes it possible to use the Lisp debugger to debug the sentinel. @xref{Debugger}. If an error is caught, Emacs pauses for @code{process-error-pause-time} seconds so that the user sees the -error. @xref{Asynchronous Processes} +error. @xref{Asynchronous Processes}. While a sentinel is running, the process sentinel is temporarily set to @code{nil} so that the sentinel won't run recursively. |