this post was submitted on 04 Jul 2023

1103 points (98.7% liked)

linuxmemes

26317 readers

22 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 users for any reason. This includes using blanket terms, like "every user of thing".

Don't get baited into back-and-forth insults. We are not animals.

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.

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, no politics, no trolling or ragebaiting.

4. No recent reposts

Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.

5. 🇬🇧 Language/язык/Sprache

This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸

Comments written in other languages are allowed.

The substance of a post should be comprehensible for people who only speak English.

Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.

6. (NEW!) Regarding public figures

We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.

Keep discussions polite and free of disparagement.

We are never in possession of all of the facts. Defamatory comments will not be tolerated.

Discussions that get too heated will be locked and offending comments removed.

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 remove France.

founded 2 years ago

MODERATORS

poopsmith@lemmy.world

zephyr@lemmy.world

rtxn@lemmy.world

1103

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

submitted 2 years 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 50 points 2 years ago (7 children)

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 2 years ago (1 children)

Use fzf for a more visual search.

[–] LeanFemurs@lemmy.world 5 points 2 years ago

This is the way.

[–] brakenium@lemm.ee 8 points 2 years ago (1 children)

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

[–] wandering_nomad@lemmy.world 8 points 2 years ago

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

[–] spoopyking@lemmy.fmhy.ml 6 points 2 years ago (1 children)

Or history | grep 'command'

[–] m15otw@feddit.uk 3 points 2 years ago (1 children)

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

[–] rufus@lemmy.world 7 points 2 years ago

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

load more comments (4 replies)

[–] HorreC@kbin.social 44 points 2 years ago (7 children)

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

[–] LobsterDog@frig.social 15 points 2 years ago (1 children)

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

[–] count_duckula@discuss.tchncs.de 6 points 2 years ago (1 children)

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

[–] tsukassa@lemmynsfw.com 3 points 2 years ago

Thanks for clearing up this mystery.

[–] mrmanager@lemmy.today 12 points 2 years ago (3 children)

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

[–] lungdart@lemmy.ca 3 points 2 years ago (3 children)

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 2 years ago

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

[–] whofearsthenight@kbin.social 4 points 2 years ago (1 children)

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...

load more comments (1 replies)

[–] fuckstick@lemmy.world 2 points 2 years ago (4 children)

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 2 years ago

fzf masterrace

[–] tobier@lemmy.world 10 points 2 years ago (3 children)

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

[–] amos@lemmy.world 7 points 2 years ago (4 children)

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)

[–] skomposzczet@vlemmy.net 10 points 2 years ago

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

[–] Aceticon@lemmy.world 8 points 2 years 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 2 years ago (4 children)

[deleted]

[–] Skyler@kbin.social 7 points 2 years ago (1 children)

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 2 years ago (1 children)

Yall are missing out on autocomplete.

[–] bustrpoindextr@lemmy.world 4 points 2 years ago (1 children)

I got that as hgrep

load more comments (1 replies)

[–] notasandwich1948@sh.itjust.works 3 points 2 years ago (2 children)

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 2 years ago (1 children)

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 2 years ago

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

[–] Ignacio@kbin.social 7 points 2 years ago (1 children)

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

[–] Teeetris@feddit.nl 2 points 2 years ago

Still noup

[–] Socsa@sh.itjust.works 5 points 2 years ago (1 children)

We will history | grep docker until morale improves

[–] JasonDJ@vlemmy.net 4 points 2 years ago* (last edited 2 years 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.

[–] vimdiesel@lemmy.world 5 points 2 years ago

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

[–] Ephur@lemmy.world 5 points 2 years 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