xkill :-(
I have a script named
din my PATH and it contains this:("$@" > /dev/null 2>&1 &)It allows me to run any program in a fully detached state in a way that works even if the terminal that started the program closes, and it’s as simple as
d <command>.good idea, I’ve been manually typing out variations of this as needed for years.
Shouldn’t you end with
& disownto fully detach?IIRC
disownis a shell built-in command, so its use is a bit limited. Not sure if&is also a built-in, but I founddisownto not work in some situations. Besides, it’s shorter.shell built-in command
After looking into it a bit more, its at least a builtin for
bashbut is otherwise not POSIX. I guessnohup ... &would be the POSIX compliant equivalent, though still not a builtin.Its my understanding that
&backgrounds, not necessarily detaches, a process – if the parent process closes, I think the background tasks would still bewait()ed on, if only using&.
How does this even work? I get the redirection part, but how is the command executed in a detached state?
()creates a subshell, and&runs the command in background. The$@means everything after the first argument, so the<command>is executed like a normal command. I am not sure why this works, but it has worked more consistently thannohup,disown, and it’s a lot shorter than most other solutions.
grep, sed, awk, and find
What do y’all use awk for really? 20 of using Linux, I’ve never had to use awk. And I’ve done a looot of scripting in my days. Anything from building my own clone of polybar using eww (with loads of scripts underneath), to automated systems for bulk handling of student assignments back at uni when I used to help out with grading and such.
What’s awk good for that other standard utilities can’t do?
I’ve been using Linux for 25 years,
awkis a more recent addition to my arsenal, but rapidly becoming more and more useful.For example,
awkis extremely helpful if you want to rearrange columns, do math on columns, essentially do things that would take multiple lines ofbashwithcutandread.
