1
0
mirror of https://github.com/UzixLS/picocom.git synced 2025-07-19 07:21:18 +03:00

Standard input handling

- Allow stdin to be a non-tty (print a warning, though). Some things may
  not work as expected in this case, but most will, and it's useful in
  several occasions.

- If picocom reads zero bytes from stdin, then:

  - If --exit-after is set, then keep operating (without reading from
    stdin) until the idle timeout expires, or we are killed by a signal

  - Otherwise, exit picocm, but only after transmitting the contens of
    the output queue.
This commit is contained in:
Nick Patavalis
2017-12-15 00:13:40 +02:00
parent a5ea42b616
commit 5ccc25ad94
2 changed files with 35 additions and 13 deletions

View File

@ -323,6 +323,15 @@ Picocom accepts the following command-line options.
when it becomes idle. When exiting with **--exit-after**, picocom
observes the **--noreset** setting as usual. (Default: not set).
NOTICE: If **--exit-after** is set, reading zero bytes from the
standard input (which usually means that whatever was connected
there has been closed), will not cause picocom to exit. Instead,
picocom will keep running without reading from stdin, and will
exit only when it becomes idle for the specified time, or if
killed by a signal. If **--exit-after** is *not* set, then reading
zero bytes from the standard input causes picocom to exit, after
the contents of its output queue have been transmitted.
**--quiet** | **-q**
: Forces picocom to be quiet. Suppresses the output of the initial