I’ve been using Linux as my main driver for a couple of years now but I didn’t know the list of reserved file name characters is so short.
I didn’t believe ‘*’ is allowed. That alone is so error-prone, it’s insane. Backslash is allowed too - how do you escape that? Sometimes I think they giggled while writing the specs.
Never create a file named “-rf *” unless you really plan on keeping it.
rm ./-rf
if you use fish you can tab-cycle tour way to the file
I’ve been using Linux as my main driver for a couple of years now but I didn’t know the list of reserved file name characters is so short.
I didn’t believe ‘*’ is allowed. That alone is so error-prone, it’s insane. Backslash is allowed too - how do you escape that? Sometimes I think they giggled while writing the specs.
It’s backslashes all the way down
Just use double backslashes for each backslash
rm ./—rf\ \*Am I missing something?
I’m not going to try it but… rm “./-rf *” would do the same? rm “./-rf \*” maybe?
If you do want to try, just start a docker container and try inside there. That should negate all risk
Couldn’t get single quotes to type on my phone, but best to always use them for problems like that, to completely get rid of shell interference.
I always forget about the single quotes.
I’m not sure that you belong in this thread :)