Quote:
Originally Posted by DiapDealer
Oh, OK. That's the expected behavior with Sigil and the Windows command prompt, then. As I mentioned, Sigil is not a Windows terminal program. There is nothing for the terminal to wait on after Sigil launches. After it checks to see whether an epub was passed to Sigil as an argument. It detaches itself and becomes its own process. The terminal can be closed, or left open, it has no effect on the GUI Windows application after launch.
|
At this stage, I'm not even going to guess why Sigil doesn't detach then from a cygwin shell! And then lets me see that warning on opening an image. I guess in the normal Windows environment, those warnings just go nowhere?
As I mentioned, I'm a Unix guy so almost never use CMD. Cygwin almost makes Windows usable
.
EDIT: Already switched to Calibre's built-in Open with
