Greg Wooledge wrote: > Now, this is where I get confused about your goals. It sounds like > you've written a program that interacts with a user via the terminal. > If something else runs your program as a background command, then your > program won't work. It'll be stopped when it tries to read the user's > responses from the terminal. > > In that situation, the error is not in your program. It's in the other > program that tried to run an interactive process in the background. > > It's not your *job* to work around the errors in other programs. That > way lies madness.
Having crossed into madness, I appreciate your perspective. Thank you!
