Show ContentSchiffsmädchenjunge@sh.itjust.works181·2 months agoI just load bash.history in Kate or whatever and ctrl-f the command, copy the line, insert that in the terminal, adapt if necessary and go. Unless it’s one of the last ten or so I used, then it’s just ⬆️⬆️⬇️⬇️⬅️➡️⬅️➡️🅱️🅰️
Show Contentfmstrat@lemmy.nowsci.comEnglish6·2 months agoUse control r, and press control r repeatedly after the first find. It will cycle through every result.
Show Contentkernelle@0d.gs2·2 months agoYeah that’s what I’m trying to avoid, using grep displays all of my options at once.
Show ContentWhyJiffie@sh.itjust.worksEnglish4·2 months agoalso, put a space before history so the useless searches don’t end up in the history
Show ContentSchiffsmädchenjunge@sh.itjust.works1·2 months agoI’m too brain lazy to look up how to properly use grep
Show Contentkernelle@0d.gs3·2 months agoYou can use regular strings! Can’t tell you how often* I use: history | grep docker
Show ContentSchiffsmädchenjunge@sh.itjust.works6·2 months agoTIL history is a thing (I will have forgotten everything about it about 10seconds after closing this tab)
I just load bash.history in Kate or whatever and ctrl-f the command, copy the line, insert that in the terminal, adapt if necessary and go. Unless it’s one of the last ten or so I used, then it’s just ⬆️⬆️⬇️⬇️⬅️➡️⬅️➡️🅱️🅰️
history | grep <search>
I like seeing different usages
Use control r, and press control r repeatedly after the first find. It will cycle through every result.
Yeah that’s what I’m trying to avoid, using grep displays all of my options at once.
also, put a space before history so the useless searches don’t end up in the history
I alias h to history | grep
This is the way
I’m too brain lazy to look up how to properly use grep
You can use regular strings! Can’t tell you how often* I use:
history | grep dockerTIL history is a thing (I will have forgotten everything about it about 10seconds after closing this tab)
curl cht.sh/grep