this post was submitted on 12 Jan 2026
364 points (89.6% liked)

linuxmemes

28899 readers
1927 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

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.
  • Don't come looking for advice, this is not the right community.
    • 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 figuresWe 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
    364
    it's just the worst (lemmy.world)
    submitted 3 days ago by kali_fornication@lemmy.world to c/linuxmemes@lemmy.world
    186 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] prole@lemmy.blahaj.zone 5 points 3 days ago (2 children)

    Fish is great if you can't remember a specific command, or don't want to type out long filenames/locations, but I dunno if I'd use it as the default.

    I just type "fish" in the terminal if I ever run into a situation where I might get some use from it.

    [–] null@piefed.nullspace.lol 10 points 3 days ago (1 children)

    I used to do that, until I realized I never had a usecase for plain bash over fish

    [–] Ephera@lemmy.ml 3 points 3 days ago (1 children)

    I have that occasionally when I want to copy a complex bash command from somewhere. But yeah, I can then just run bash, run the command in there and then exit back out of there.

    [–] 1rre@discuss.tchncs.de 2 points 2 days ago (1 children)

    that's what bass is for

    [–] Ephera@lemmy.ml 2 points 2 days ago

    I'm guessing, you mean this then: https://github.com/edc/bass

    But well, I was rather thinking of when it's using Bash-scripting-syntax to combine multiple commands.
    Like, maybe there's a for-loop in there. You just can't paste that directly into Fish and have it work. Granted, you should probably put that into a script file, even if you're using Bash, but yeah, just temporarily launching bash is also an option.

    [–] Digit@lemmy.wtf 2 points 2 days ago (1 children)

    in my ~/.bashrc

    # if interactive, launch fish
[[ $- != *i* ]] && return || fish

    and

    alias f='fish'

    So fish is my default, and if I ever need bash, it's already there underneath, just a Ctrl-d keybind away to fall back on, and if I want to get back into fish, it's just a f & RETURN away.

    Seems better to have all the convenience of fish up front. All the completion magic. I so rarely have to type much at all.

    [–] PM_me_your_doggo@lemmy.world 1 points 1 day ago (1 children)

    Why not just set it as the default then?

    [–] Digit@lemmy.wtf 1 points 1 day ago* (last edited 1 day ago)

    Can cause issues (with things that expect bash or other nearer POSIX compliant shells as the system shell).

    And then I'd lose those other benefits described, like having bash just a keybind away.

    [Edit: I could have swore I got that interactive check in bashrc thing from https://fishshell.com/docs/current/faq.html or other documentation on fishshell.com, but, seems not. Can't find it even in older copies. Not sure where I picked up that idea from then. Plausibly from someone on irc. I was sure I got that as official advice from fish... which I've been using and doing that method with since around 2014.]