Next: Signals to Processes, Previous: Process Information, Up: Processes
Asynchronous subprocesses receive input when it is sent to them by Emacs, which is done with the functions in this section. You must specify the process to send input to, and the input data to send. The data appears on the “standard input” of the subprocess.
Some operating systems have limited space for buffered input in a pty. On these systems, Emacs sends an EOF periodically amidst the other characters, to force them through. For most programs, these EOFs do no harm.
Subprocess input is normally encoded using a coding system before the
subprocess receives it, much like text written into a file. You can use
set-process-coding-system
to specify which coding system to use
(see Process Information). Otherwise, the coding system comes from
coding-system-for-write
, if that is non-nil
; or else from
the defaulting mechanism (see Default Coding Systems).
Sometimes the system is unable to accept input for that process, because the input buffer is full. When this happens, the send functions wait a short while, accepting output from subprocesses, and then try again. This gives the subprocess a chance to read more of its pending input and make space in the buffer. It also allows filters, sentinels and timers to run—so take account of that in writing your code.
In these functions, the process argument can be a process or
the name of a process, or a buffer or buffer name (which stands
for a process via get-buffer-process
). nil
means
the current buffer's process.
This function sends process the contents of string as standard input. It returns
nil
. For example, to make a Shell buffer list files:(process-send-string "shell<1>" "ls\n") ⇒ nil
This function sends the text in the region defined by start and end as standard input to process.
An error is signaled unless both start and end are integers or markers that indicate positions in the current buffer. (It is unimportant which number is larger.)