1096

Look, I'm lazy, okay? (lemmy.world)

submitted 1 year ago by primaryuser@lemmy.world to c/linuxmemes@lemmy.world

82 comments fedilink hide all child comments

top 50 comments

sorted by: hot top controversial new old

[-] m15otw@feddit.uk 49 points 1 year ago

Ctrl+R

Then type any part of the command (filename, search string, etc)

Ctrl+R again to cycle through the matches.

(Best feature in bash)

[-] p0q@sh.itjust.works 12 points 1 year ago

Use fzf for a more visual search.

[-] LeanFemurs@lemmy.world 5 points 1 year ago

This is the way.

[-] brakenium@lemm.ee 8 points 1 year ago

I've been using this for a long time, never knew I could press Ctrl + R again. Thanks!

[-] wandering_nomad@lemmy.world 8 points 1 year ago

Ctrl + S to go the other way if you overshoot!

[-] spoopyking@lemmy.fmhy.ml 6 points 1 year ago

Or history | grep 'command'

[-] m15otw@feddit.uk 3 points 1 year ago

Can't just hit enter to run the one you want then, though.

[-] rufus@lemmy.world 7 points 1 year ago

Type: !1234 ... to run whatever history number of the command.

load more comments (3 replies)

[-] HorreC@kbin.social 42 points 1 year ago

control shift R, then start typing, it will search your bash history

[-] LobsterDog@frig.social 15 points 1 year ago

Is it not just Ctrl-R or is that platform dependent

[-] count_duckula@discuss.tchncs.de 6 points 1 year ago

I have always used ctrl-r but I just checked and both work. TIL.

[-] tsukassa@lemmynsfw.com 3 points 1 year ago

Thanks for clearing up this mystery.

[-] mrmanager@lemmy.today 12 points 1 year ago

Hmm, normally it's just ctrl - r... Are you sure the shift is needed on your system?

[-] lungdart@lemmy.ca 3 points 1 year ago

Don't forget fzf. That will really jazz up your history search!

load more comments (3 replies)

load more comments (2 replies)

[-] rikudou@lemmings.world 5 points 1 year ago

I recommend using mcfly for that, it makes it even better.

[-] whofearsthenight@kbin.social 4 points 1 year ago

Now if you had to guess how often I remember that there is a keyboard shortcut that does this, but don't remember what it is, and do remember that I can just press up 30-70 times...

[-] HorreC@kbin.social 2 points 1 year ago

you can hit it again after you are dialed in as much as you want and it will keep going back in time with the words you have in there and stuff that matches!

[-] fuckstick@lemmy.world 2 points 1 year ago

This. It took a while for it to sink in but now it’s muscle memory and a huge time saver

load more comments (4 replies)

load more comments (2 replies)

[-] ttk@feddit.de 10 points 1 year ago

fzf masterrace

[-] skomposzczet@vlemmy.net 10 points 1 year ago

up, up, up, up, up, cd .., ah there it is.

[-] tobier@lemmy.world 9 points 1 year ago

This is why I switched to fish; it seems to be much smarter understanding what I want to type.

[-] amos@lemmy.world 7 points 1 year ago

Yeah it's great how ctrl-r is kinda the default instead of something you have to go out of your way to use. Just start typing a command and the up arrow will only cycle through history that matches what you've typed so far.

load more comments (4 replies)

load more comments (2 replies)

[-] Aceticon@lemmy.world 8 points 1 year ago

It's like the bus-stop-paradigm: If I wait just a bit longer and it will come. Meanwhile it would've been faster to walk.

[+] runswithjedi@lemmy.world 8 points 1 year ago

[deleted]

[-] Skyler@kbin.social 7 points 1 year ago

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-run ls /tmp

load more comments (1 replies)

[-] pleb@discuss.tchncs.de 6 points 1 year ago

Yall are missing out on autocomplete.

load more comments (1 replies)

[-] bustrpoindextr@lemmy.world 4 points 1 year ago

I got that as hgrep

[-] notasandwich1948@sh.itjust.works 3 points 1 year ago

didn't know there was a comment for that, I just always used cat to read the bash history file

load more comments (2 replies)

[-] Sketchpad01@lemmy.world 7 points 1 year ago

Using the history command just to find the specific IP I need to ssh to

load more comments (1 replies)

[-] Badland9085@lemm.ee 7 points 1 year ago

To anyone who uses vim mode, ? lets you search through your stored command history, from normal mode ofc.

[-] Ignacio@kbin.social 7 points 1 year ago

It's even faster if you look for it inside .bash_history.

load more comments (1 replies)

[-] vimdiesel@lemmy.world 5 points 1 year ago

⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬇️ ⬇️

[-] Socsa@sh.itjust.works 5 points 1 year ago

We will history | grep docker until morale improves

[-] JasonDJ@vlemmy.net 4 points 1 year ago* (last edited 1 year ago)

Gah it's all docker container ps -a. OK, fine, history | grep "docker run".

Next time I'll put a file in the project directory that tells me how I ran it and .gitignore it. I promise. Next time.

[-] konakona@sh.itjust.works 5 points 1 year ago

"python3 -m http.server"

[-] Ephur@lemmy.world 5 points 1 year ago

I create so many aliases with the notion of how much time I’ll save… never use ‘em. Works out okay though because a much richer history to fzf through

[-] corytheboyd@kbin.social 4 points 1 year ago

https://github.com/junegunn/fzf

[-] MavTheHack@lemmy.fmhy.ml 4 points 1 year ago

I just use the 'fuck' command after lazily typing letters that somewhat match the command I want to run

[-] titey@programming.dev 4 points 1 year ago

This is the way!

[-] LandedGentryOnlyClub@lemmy.fmhy.ml 3 points 1 year ago

Yeah but last time I typed it, it worked. Who knows what ridiculous typos I'd make right now?

[-] billygoat@lemmy.fmhy.ml 3 points 1 year ago

I’ve always used set -o vi. Let’s you use vi commands on the bash prompt.

[-] desmosthenes@lemmy.world 3 points 1 year ago

https://github.com/marlonrichert/zsh-autocomplete Autocomplete for Zsh

load more comments

this post was submitted on 04 Jul 2023

1096 points (98.7% liked)

linuxmemes

21282 readers

455 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

Instance-wide TOS: https://legal.lemmy.world/tos/
Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html

2. Be civil

Understand the difference between a joke and an insult.

Do not harrass or attack members of the community for any reason.

Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.

Bigotry will not be tolerated.

These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.

3. Post Linux-related content

Including Unix and BSD.

Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.

No porn. Even if you watch it on a Linux machine.

4. No recent reposts

Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

Please report posts and comments that break these rules!

Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

founded 1 year ago

MODERATORS

poopsmith@lemmy.world

zephyr@lemmy.world

rtxn@lemmy.world