Missing feature: log the communication

[GoogleCodeExporter]

A small but very useful addition would be the possibility to keep a log of
the communication with the terminal device.

Original issue reported on code.google.com by j.pommn...@gmail.com on 5 Oct 2009 at 3:28

[GoogleCodeExporter]

Whenever I have to log terminal sessions, I just use "script" to record the 
terminal
session (script -f -c "picocom /dev/ttyS0" session.log).  This also logs the 
comms
parameters into the top of the log file.  I hope this helps.

-- Benjamin Holmes

Original comment by d3...@optusnet.com.au on 28 Jan 2010 at 12:13

[GoogleCodeExporter]

If the "script(1)" solution suggested by Benjamin Holmes is not adequate, 
please reopen.

Original comment by nick.pat...@gmail.com on 21 Feb 2012 at 6:45

• Changed state: WontFix
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

(It would be nice if the tip with "script" would be documented in the man page.
It took me a while to find this)

I'd like to have better control over the output though. Both when in starts and 
stops and the filename.

Current workflow for capturing fragments of a session into separate files is 
somewhat awkward:

- Starting picocom with a "script" command logging the session into a logfile,

- waiting for the end of an interesting interval,

- leaving picocom,

- renaming the logfile with a meaningful name
  (the name is not known at start of the workflow),

- opening editor to remove unneeded lines at the
  beginning of the log file, close,

- starting again (living with lost serial data as there
  is no handshake).

I would like to reopen this issue (but not being the original reporter I 
probably can't).

Original comment by Frieder....@web.de on 12 Oct 2012 at 8:19