{"action":"opened","issue":{"url":"https://api.github.com/repos/Franciman/vabal/issues/9","repository_url":"https://api.github.com/repos/Franciman/vabal","labels_url":"https://api.github.com/repos/Franciman/vabal/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/Franciman/vabal/issues/9/comments","events_url":"https://api.github.com/repos/Franciman/vabal/issues/9/events","html_url":"https://github.com/Franciman/vabal/issues/9","id":394630286,"node_id":"MDU6SXNzdWUzOTQ2MzAyODY=","number":9,"title":"Circumvent the non portable behavior of xargs when input is empty","user":{"login":"Franciman","id":419177,"node_id":"MDQ6VXNlcjQxOTE3Nw==","avatar_url":"https://avatars1.githubusercontent.com/u/419177?v=4","gravatar_id":"","url":"https://api.github.com/users/Franciman","html_url":"https://github.com/Franciman","followers_url":"https://api.github.com/users/Franciman/followers","following_url":"https://api.github.com/users/Franciman/following{/other_user}","gists_url":"https://api.github.com/users/Franciman/gists{/gist_id}","starred_url":"https://api.github.com/users/Franciman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Franciman/subscriptions","organizations_url":"https://api.github.com/users/Franciman/orgs","repos_url":"https://api.github.com/users/Franciman/repos","events_url":"https://api.github.com/users/Franciman/events{/privacy}","received_events_url":"https://api.github.com/users/Franciman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-28T12:50:33Z","updated_at":"2018-12-28T12:50:33Z","closed_at":null,"author_association":"OWNER","body":"BSD xargs doesn't execute the command when the input is empty, while with GNU xargs we need to use the -r flag.\r\n\r\nA POSIX solution is available, but it's clumsy:\r\n> output=$(vabal) && printf %s \"$output\" | xargs cabal new-build\r\n\r\nAnother suggestion by @lortabac is to print an `--help` option so that cabal won't do anything but just print the help message, or a `--vabal-failed-see-stderr` to make purposely fail cabal, when vabal fails. These solutions are hackish but work fine portably (also it is really unlikely that cabal will start using that `--vabal-failed-see-stderr` option :P)."}}
{"actor":{"display_login":"Franciman"}}