Add option to disable terminal input

[BebeSparkelSparkel]

Sometimes it is nice to multitask in a single shell and run stack build --file-watch & to run stack in the background. However, stack will ask for terminal input and that brings it to the foreground.

Could a flag be added to disable the command input between builds?

[mpilgrem]

@BebeSparkelSparkel, thanks for the report. May I clarify first what you are experiencing? For example, I'm on Windows, using VS Code as the editor and running stack build --file-watch in a Windows Terminal pane. With that setup, there is no problem with the Windows Terminal pane coming to the foreground.

[BebeSparkelSparkel]

This question explains what is going on exactly with a different program https://stackoverflow.com/questions/42361200/why-do-i-get-the-information-of-suspended-tty-input-when-i-run-my-script-in

From man bash

     To facilitate the implementation of the user interface to job control,
     the operating system maintains the notion of a current terminal process
     group ID.  Members of this process group (processes whose process group
     ID is equal to the current terminal process group ID) receive keyboard-
     generated signals such as SIGINT.  These processes are said to be in the
     foreground.  Background processes are those whose process group ID
     differs from the terminal's; such processes are immune to keyboard-
     generated signals.  Only foreground processes are allowed to read from
     or, if the user so specifies with stty tostop, write to the terminal.
     Background processes which attempt to read from (write to when stty
     tostop is in effect) the terminal are sent a SIGTTIN (SIGTTOU) signal by
     the kernel's terminal driver, which, unless caught, suspends the process.