{"action":"closed","issue":{"url":"https://api.github.com/repos/npat-efault/picocom/issues/29","labels_url":"https://api.github.com/repos/npat-efault/picocom/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/npat-efault/picocom/issues/29/comments","events_url":"https://api.github.com/repos/npat-efault/picocom/issues/29/events","html_url":"https://github.com/npat-efault/picocom/issues/29","id":101097165,"number":29,"title":"Standard input must be a terminal","user":{"login":"mrkline","id":493463,"avatar_url":"https://avatars.githubusercontent.com/u/493463?v=3","gravatar_id":"","url":"https://api.github.com/users/mrkline","html_url":"https://github.com/mrkline","followers_url":"https://api.github.com/users/mrkline/followers","following_url":"https://api.github.com/users/mrkline/following{/other_user}","gists_url":"https://api.github.com/users/mrkline/gists{/gist_id}","starred_url":"https://api.github.com/users/mrkline/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrkline/subscriptions","organizations_url":"https://api.github.com/users/mrkline/orgs","repos_url":"https://api.github.com/users/mrkline/repos","events_url":"https://api.github.com/users/mrkline/events{/privacy}","received_events_url":"https://api.github.com/users/mrkline/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/npat-efault/picocom/labels/needs%20more%20input","name":"needs more input","color":"fef2c0"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-08-14T20:24:31Z","updated_at":"2015-08-18T05:09:36Z","closed_at":"2015-08-18T05:09:36Z","body":"Why does picocom enforce that stdin _must_ be a terminal? As far as I can tell, picocom's interaction with stdin (a simple `select`/`read` loop) shouldn't care what it is, and feeding picocom with a file or pipe would allow it to act as a general-purpose relay to and from a serial device. This would be incredibly useful for test scripts and other automation."}}