Carly™@lemmy.world to linuxmemes@lemmy.worldEnglish · 1 year agoLook, I'm lazy, okay?lemmy.worldimagemessage-square89fedilinkarrow-up11.22Karrow-down118
arrow-up11.2Karrow-down1imageLook, I'm lazy, okay?lemmy.worldCarly™@lemmy.world to linuxmemes@lemmy.worldEnglish · 1 year agomessage-square89fedilink
minus-squareSkyler@kbin.sociallinkfedilinkarrow-up7·1 year agoThis is my approach, and for those who don’t know, you can use those line numbers that come back from history to rerun the command. Like if your output is something like this: $ history | grep tmp 501 ls /tmp 502 history | grep tmp You can run !501 and it will just re-run ls /tmp
This is my approach, and for those who don’t know, you can use those line numbers that come back from
history
to rerun the command. Like if your output is something like this:$ history | grep tmp 501 ls /tmp 502 history | grep tmp
You can run
!501
and it will just re-runls /tmp
Woah! I had no clue!