akrennmair/newsbeuter — pull request #138 by mrabault (2014-05-24 20:55:02+00:00)
Title: Nonblocking browser open

Hello,

Previously, newsbeuter needed the browser command to be nonblocking (i.e the process had to spawn, fork and the parent process to terminate). However, by default, chromium (it's the only example I had) doesn't fork itself if no instances are alreadyopen. That makes newsbeuter block until chromium is done. I didn't like this behavior, because typically, I open interesting feeds in the browser, to read them more in detail later.
These commits circumvent the problem: a new process is created, and this child process executes whatever the browser command is. That way, we don't assume anything about the browser command and everyone is happy (i.e newsbeuter doesn't block). The child process exits after the browser process exits.

Thanks in advance for your consideration, and sorry for any English errors I might have made, as it's not my mother tongue.