• 26 Posts
  • 87 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle



  • Maybe controversial, but the fish shell. I know it’s not strictly bash syntax, but the OOTB features are just so user-friendly. The most helpful features for learning: the autocomplete (with descriptions of subcommands and flags!) and the fuzzy history search.

    I write bash scripts all the time, and am significantly more knowledgeable than anyone else on my team (admittedly frontend) because I got comfortable in fish.






  • Another really helpful tool is to use the fish shell instead of bash. It has tons of useful features, but my favorite is by far the autocomplete. It parses man pages to provide suggestions for flags, subcommands, even passed arguments, and each item in the results list has a description, and it’s all searchable by hitting shift+tab.

    fish autocomplete subcommands

    fish autocomplete git

    That’s what leveled up my cli game from 0-100. It’s a massive difference in usability and discoverability. And unlike things like nushell, it’s close enough to bash that you won’t feel confused if you have to use bash instead.













  • Tekhne@sh.itjust.workstoProgrammer Humor@lemmy.mlgot him
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    In a world where your IDE and maybe also compiler should warn you about using unicode literals in source code, that’s not much of a concern.

    VSCode (and I’m sure other modern IDEs, but haven’t tested) will call out if you’re using a Unicode char that could be confused with a source code symbol (e.g. i and ℹ️, which renders in some fonts as a styled lowercase i without color). I’m sure it does the same on the long equals sign.

    Any compiler will complain (usually these days with a decent error message) if someone somehow accidentally inserts an invalid Unicode character instead of typing ==.