#232 BOSS run from Bash has no visible CLI

BOSS's command line interface is potentially interactive, but when it is run from Bash's launcher bar, its command line interface is not displayed. When BOSS waits for user input, such as when an update is available, this makes it seem as though BOSS has hung.

The way in which Bash runs BOSS needs to be changed so that its command line window is visible.

[tox2ik]

'reiella', on 02 Oct 2012 - 02:22 AM, said:
Not quite sure what happened, but attempts to run boss through Wrye Smash now result in a freeze. I'm thinking it may be related to the update dialog that BOSS uses when it's out of date since upgrading to 2.1 seems to have fixed the problem.

'wrinkly ninja', soon thereafter
Yeah, known issue. link here.

Which interactive features are you talking about? The prompt for ENTER when an illegal argument value is passed*? E.g. BOSS.exe -f illegalArqumentValue. Perhaps this "interactive" behavior is a GUI dialog box? Was it removed in later versions of BOSS? If it is a GUI confirmation/notification then I don't even know what to say because the one I see never asks me for anything. If it is a real CLI prompt you are talking about, then it's really BOSS.exe's responsibility to check whether the stdin is a terminal. I haven't seen this prompt. It's not immediately obvious how to invoke it from the terminal. Perhaps this is documented in the git repo, Idk.

(Perhaps I should try running BOSS from WB to see what happens...)

* frankly, that "please confirm that I won't take bad arguments" is totally unnecessary. It's such a facepalm. No offense, just sharing my perspective as an avid terminal user.