Reasons to use your shell's job control

learnbyexample@programming.dev to Linux@lemmy.ml – 61 points –
jvns.ca
6

Had a little spark of glee looking at a fellow nix user in the wild

Defined in /nix/store/vicfr

I had a spark of glee seeing another fish shell user.

I used "job control" a lot but never called it that. And I mostly would background or foreground tasks. I didn't know about a few of those additional commands talked about. Disown will be pretty handy.

Hello fellow fish user.

Disown is. I even have a fish function written so I can do 'launch foo' and it'll run foo, redirect everything to /dev/null (not sure that's necessary, but doesn't hurt), and then disowns the process. Mostly because I have a habit of running stuff using whatever terminal I happen to have in front of me.

Good idea to write a function, I'll do that right now. Over the last few weeks I've been regularly doing the Ctrl+Z, bg, disown, which does get old pretty quickly. At least I now remember the terms and don't have to search for them each time I need it :D

ut never called it that. And I mostly would background or foreground tasks. I didn’t

yeah I had no idea about disown, Jesus the number of times I could have used that, I might have never learned tmux or screen :)

Gonna have to disagree with #3 - stopping Vim is not necessary for this. There's the builtin :! command.

1 more...