@Skirmisher either you cancel it and run it in a 'screen' session instead, or you hit ctrl+z to pause it, then type 'bg' to run it in the background, then 'nohup' to disown it. you won't see the output when doing the latter so I'd recommend screen when possible. screen is kinda unintuitive to use at first but you can find guides
@zigg @Skirmisher i've never considered that before! i should look into it…
@notwa For @Skirmisher either will work 😊 But yeah, figured I’d mention it in case it’s already there
@zigg Okay, I got tmux because I'm frustrated and I want to do this a good way. What do I do now?
@zigg Never mind, I understand how it works now. I'm up way later than I should, though, so I'm mad about it for no reason. :(
@Skirmisher Yeah, sorry, and I have to go to work 😞
@zigg Don't worry about it! It worked out in the end, I'm just stressed about being up late. ^^;
@notwa Yeah, I looked up the bg thing. I need to figure out how to use screen or tmux or something sometime...
@notwa Wait, how do I use nohup on a running process? If I don't, does the process still die if I close the session?
@Skirmisher oh no wait, i meant 'disown', sorry! i put too much thought into it…
@Skirmisher also yeah, background processes close with your session. your shell might even warn you about it, i know zsh does.
@notwa Turns out bash is configured by default to not send SIGHUP to running jobs when a shell exits. Anyway, I guess I'll let this go and scream at it in the morning when the compile inevitably fails, or something.
@notwa Wait, once all of my sessions logged out, then it did die. Oh well, all the objects are still there, so the make should pick up where it left off. Whatever.
@notwa @Skirmisher tmux is also an option that accomplishes similar things to Screen, if it’s available. Most people I know who use tmux day-to-day prefer it to Screen.