Yes! But -u is for undefined variables. It won't stop a defined variable with an empty value. E.g foo="".
Also ? and :? have the advantage of telling you right then and there where the variable use is that it must be defined or not empty... having to trek back to (likely) the top of the script to check is easily forgotten.
rm -rf ${var}/ is a disaster waiting to happen.
Always do rm -rf "${var:?}/" so that the script aborts if the variable is empty. Or better yet rm -rf "./${var:?}/".
Edited to add quotes. Always quote a path: it might have spaces in it, without quotes that will become multiple paths! Which would also have avoided the particular bug in question.
Sweet, a win-win then!
I detest that meme, but you made me snort.
Lol, down votes from chumps who can't tell the difference between NVIDIA's excellent hardware and Nvidia's shitty business practice.
One of which is French, yes.
They just need to gate-keep harder. It'll work next time.
Imagine being that invested in a corporate brand.
Rather, I bought from the vendor who contributed their GPU drivers to the Linux Kernel. It just so happened that's AMD.
NVIDIA sycophants hate that one weird trick.
I use them for additional network adaptors in one host.
In another I use them for NVMe adaptors for an ancient MB that predates the existence of the m.2 interface.
It's cheaper to install malware.
That's all there is to it: cost.
"A joke everyone liked"
"Chums"
Protects you from accidentally changing the variable within the block too!