Fish once again undefeated. If I want to find that weird image magick command I used earlier with foo.png in it I just type
foo.png, hit up and its usually the first one. It doesnt matter where foo.png occurs in the command, fish will find it.I write part of the command then ctrl+r. Using FZF mind you. Such a great utility.
I typed it once, I’m not typing it again
Ctrl R
holy fucking shit 🤌💪🤯❤️💯
- zsh-autosuggestions
history | fzfalias cat="bat --plain --theme=gruvbox-dark"
Aliasing
cator any other ubiquitous shell utility to a replacement is a mistake. Garuda did this, and it was driving me crazy whycatwas giving me errors. Turns out that they had aliasedbattocat, and sincebatis a different program, it didn’t work in exactly the same way, and an update had introduced some unexpected behavior.Drop-in replacements are dumb. Just learn to use a different command.
I think it’s ok to add this in a personal
.zshrc, not on a distro level:If it breaks something - I’d probably know why and can easily fix it by removing alias/calling cat directly.
Also, scripts almost always use bash or sh in shebang, not zsh. So it only triggers if I type
catin terminal.
or documentation.To use ctrl-r I have to remember something about the command. To use up arrow I just have to know about how many commands ago I used it.
Not if you have fzf you don’t: https://github.com/junegunn/fzf
Like an interactive fuzzy finding history. It’s sick.
So how well you know which command it is of you won’t recognize it when you see it…
The number of people who don’t reverse-I-search is too damn high
CTRL+R for those unitiated
reverse-i-search + fzf = <3
It was quite a while before I realised that was possible.
Then not long after starting to use it, that I got fed up and just started opening up the history file and searching in it.why not
history | grep -iand the search term?even if there are several, you can use ! and the command’s line number to run it again
historyis shell dependent.
I’ve been using
ctrl + Rmore now :3… though I definitely used to ↑↑↑↑↑↑↑Woah Ctrl R looks super cool, never knew that I could do that before…
check out fzf (install fzf and add (assuming bash)
eval "$(fzf --bash)"to your .bashrc) Makes ctrl+r a superpowerIt’s awesome until you want to put the cursor in a specific spot of a previous command.
$ rm -f delete-me.txt ctrl-r "me", ctrl-b, ctrl-k $ rm -f deleteBut I still use fzf because while I used to do the above, fzf offered more advantage that made switching worth it.
I’ll try it if I don’t forget it by the next time I have access to my PC lol :3
Ctrl + r with fzf and you’ll never go back.
…until you press up one too many times and enter the same command but with a typo. Again.
There is an option you can set in .zshrc or .bashrc which only includes lines that exit 0 (success)
Infuriatingly that would omit things like unit test runners from the history in case they don’t pass. As a developer I tend to re-run failed commands quite often, not sure how widely that applies, though.
Oh, stuff like
git diffandgit logwill end up being omitted pretty often.
And a lot of times, the commands that end with piping intoless
Been there, done that.
You have to be a linux user to use the console now?
I knew there was an
lsIn there somewhere
ctrl + r, l, s
Much faster than simply typing
ls!Now I don’t have to type that in again. Phew!
ls … enter ↑ enter ↑ enter
You may consider using
watch lsI can’t even keep apart ls and cd it seems.
^r
Ctrl-r, l ctrl-r, ctrl-r, ctrl-r, ctrl-r, ctrl-r, ctrl-r, ctrl-r, ctrl-r. To get ls.
No way! I didn’t know you could cycle through the results like that… awesome!
It’s basically emacs incremental search.
and whenever you forget to sudo:
sudo !!You need this: https://github.com/nvbn/thefuck
I just use mcfly
Not sure I understand the point of mcfly. zsh and fish have this functionality built in, where pressing Up with a command partially typed will give auto-completions to that partial match.
Yeah. I also use auto-completions for that. McFly does fuzzy finding and because it’s a different separate db, for me it works better across many sessions to find commands I had just recently used in another session.
cat ~/.bash_history | grepUseless use of cat?
Yes, it was meant to be a self deprecating admission that I have used this unnecessarily verbose command.
Ah. Well. I can not be blameless on this. I also probably use cat unnecessarily still. But less so with grep these days. I’m getting better… I swear!
You saying I can just skip cat in that command and it works?
history | grep 'cat'My output was empty for that command.
Guess why?
Becausehistoryonly gives the last few lines in my system.
grep ~/.bash_historyHow did I not know this. Thank you!
it’s
grep STRING FILEto be preciseor
awk '/STRING/′ FILEif you prefer that for some reason
Relevant xkcd: https://xkcd.com/1168/
tar --helptar -xvf <archive-name>
but only because I had to look it up twice so now my brain has committed it to memory
I don’t even know what it doesi just use unar (unarchive) nowadays, since that works with all file formats iirc
Extract a tarball with verbose output from the specified file.
And learn how to use the ‘z’ option
tar - h
Unfortunately that’s not valid.
$ tar -h tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options Try 'tar --help' or 'tar --usage' for more information.From man-page:
-h, --dereference follow symlinks; archive and dump the files they point toDamn.
Thanks, we all died.
:)
