chris kcat wrote:
Not sure if this is the best place to bring this up, but I'm not sure it's "ready". The problem is it runs through the terminal the Wine was exec'd from. When Wine is run from the desktop manager's menu, or started in the background (eg. wine foo.exe &), if wcmd is subsequently exec'd, it will become completely unuseable since it has no input, and potentially no output, terminal. It then has to be killed through the kill or killall command.
Have you ever seen this be a problem in the real world?
To be "ready", wouldn't it need to open up its own terminal window for input and output in Wine's desktop space (eg. the virtual desktop if it's in use, or the standard desktop)?
No. That would destroy its usefulness in background applications. - Dan