Jared Casper - 2014-01-31

See this StackOverflow question for an explanation of why xclip does not exit/close stdout until another selection is made:

http://stackoverflow.com/questions/19254114/xclip-does-not-terminate-when-tracing-it

Basically, it seems the only place the text buffer exists for other X clients to copy from is xclip itself, so if it exits the text goes with it. To stay alive, xclip fork's and daemonizes. I'm not sure how xsel handles this.

I guess maybe xclip could close stdout when it knows it has nothing else to write to it?