3 ms·
Tab-completion is somewhat obnoxious in directories with lots of files sharing a common prefix, for example. Also, if you accidentally tab-complete the same fi
by loeg 7y ago
Tab-completion is somewhat obnoxious in directories with lots of files sharing a common prefix, for example.
Also, if you accidentally tab-complete the same file for output and input, depending on how clever the program is, you may end up deleting the source file.
- em-bee 7y agoi always run mv -i to make sure i don't accidentally overwrite an existing file. i don't alias mv to mv -i either, to avoid getting used to the idea that just mv is going to ask me, because i might work on a server where the alias is not set.
- loeg 7y agoI double check the filenames instead, because many of the tools I work with don't have -i flags.
- saagarjha 7y agoI’ve done gcc foo.c -o foo.c far too many times :(
- loeg 7y agoSeems like gcc should be smart enough to reject that mistake nowadays, right?!
- saagarjha 7y agoI should write a shell frontend to gcc to warn if I do this…
- lopsidedBrain 7y agoI work in exactly two modes of `gcc` usage. I either accept `./a.out` as the name I deserve, or I write a `CMakeLists.txt`. There nothing in between.