10 ms·

If you believe mkdir -p is completely unnecessary for normal users and only exists for scripting, you probably want to think about how it might fit into your wo

by oefrha 7y ago

If you believe mkdir -p is completely unnecessary for normal users and only exists for scripting, you probably want to think about how it might fit into your workflow again. In fact, my mkdir is simply aliased to mkdir -p, and I have a self evidently-named wrapper function called mkcd which I use even more often than mkdir.

AnIdiotOnTheNet 7y ago
Since one can alias commands to functions, that does suggest that in fact mkdir -p is actually unnecessary.
- pas 7y ago
  But then you would have to bring your own aliases everywhere. And common aliases just got upstreamed.
- oefrha 7y ago
  High level languages aren’t necessary because you can program in assembly too.
tclancy 7y ago
I immediately second-guessed my use of "Obviously completely"-- what I meant was "We can get by without it" whereas a standalone script cannot.
- oefrha 7y ago
  Well a script can do path parsing too, it’s just rather painful. Similar (actually more complex) real world task that does get implemented in POSIX sh: realpath(1) replacement, when it doesn’t exist.
jmmcd 7y ago
Wait, what does mkcd do?
- zimbu668 7y ago
  I'm guessing makes a directory, with paths, then cds into it.
- twanvl 7y ago
  I assume `mkdir $@ && cd $@`
- Joker_vD 7y ago
  function mkcd() { mkdir -p -- "$1" && cd -P -- "$1" }