3. Attempt to scroll the terminal window using the up arrow key
4. Noticing this is just scrolling through prior commands used in this session, change your mind, enter a "cd", and without seeing the command you happened to scroll to was "rm -rf", hit "enter".
1. ssh into your server, do some stuff
2. forget that you sshed into your server
3. some time later use pacman to install some (graphical) program
4. spend a good 10 minutes searching for the program on the local machine and a further hour or two researching whether anyone else has experienced this 'bug'
And:
1. use a US-layout keyboard and delete an entire folder instead of a single file inside it because [enter] is too close to \ and you hit [enter] when you meant to escape a space in a path
I hosed about half the .config files on the main user account for my development machine. *So far* manual restoration by cloning the lost files from another account appears to be the better of two evils, vs. a file system archiver volume backup made > a year ago. I suppose I could 'restore' the fsa to an empty partition, and just copy back the config files for the account, if I had a couple of hours to kill.
Don't show the new team member details of the main live payments database on the afternoon before the office closes for Christmas, explain that all the tables are created with 'RESTRICT ON DROP' to prevent accidents, attempt to prove it, discover the one table that wasn't created with 'RESTRICT ON DROP', and launch into 'and this is how we do a recovery...'