• Termight@lemmy.ml
    link
    fedilink
    English
    arrow-up
    22
    ·
    edit-2
    2 months ago

    Mastering the command line? A few observations. First, consult and take notes (yes, even seasoned terminal veterans forget syntax.) Secondly, embrace tab completion. It’s your friend, and a surprisingly effective substitute for remembering every single command. Third, the true test: procure a VPS or remote server and exclusively use the command line. No GUI crutches allowed. It’s a digital wilderness, and you’ll learn to navigate it.

    Lastly, and this is non-negotiable: keep a terminal window permanently resident on your desktop. Consider it a vital organ, deserving of its space. It’s a constant reminder of the power you wield, and a readily available portal to a world beyond the pretty buttons.

    • WalnutLum@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      On that front: to developers-

      Please make sure you include bash completions for your tools

    • N0x0n@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      Hehe, I’m doing this all the time now ! 3 years ago when I started my linux/self-hosted server journey with debian: CLI only !

      Was difficult at times and had a few breakdowns (most got fixed the next day… Sleep/taking some time off really helps !!!)

      One thing I’m still bad at… Is taking notes. Haven’t found a good way take IT notes. And I tried sooo many different approaches…

  • A_norny_mousse@feddit.org
    link
    fedilink
    arrow-up
    16
    ·
    2 months ago

    Colors. And a nice, readable font. Make your terminal pretty so you feel good every time you interact with it. Think about window dimensions (I personally always find the standard 80x24 too small), maybe set up some manual tiling so you can have two terminal windows fill your screen. Use the keyboard to move around your desktops.

    But mostly, colors.

  • 33manat33@feddit.org
    link
    fedilink
    arrow-up
    13
    ·
    2 months ago

    Okay, this is not Linux-specific, but it’s about a transferable skill:

    What helped me get comfortable and learn a lot of basics was setting up NetBSD. The basic install throws you into a basic command line, with no graphical interface installed and not even the internet configured. But the online guide for setting the system up is incredibly well-written and teaches you all the concepts you need to know.

    After doing this, I was familiar with a larger set of terminal commands, knew how to use vi, had a bunch of practice setting up config files in CLI and even finally learned how pipes work. It’s a very enjoyable experience, the guide is so good I didn’t feel overwhelmed once and anything you have to look up is tied to a problem you’re solving (like cursor movement in vi).

    It also teaches you how NetBSD is structured. It’s not Linux, but similar enough to understand a lot of how and why things are done in Linux systems

  • southsamurai@sh.itjust.works
    link
    fedilink
    arrow-up
    8
    ·
    2 months ago

    Really specific here, but font control.

    Us folks with dyslexia in its various expressions have trouble with command line. If you can’t read a specific command, good luck ever getting comfortable with it. You can’t error check yourself, so until you build up memory, you’re kinda screwed if you can’t use the fonts that are available.

  • lordnikon@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    2 months ago

    To things that helps no mater your skill level the tab key is your best friend and man pages are great but if those are overwhelming install the package tldr then you can use the command tldr and the command you are trying to run to give you helpful examples of how to use that command.

    Also old users don’t remember long commands if we use a command more than once. You save it to your bash alias file to create your own commands.

    • N0x0n@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Also old users don’t remember long commands if we use a command more than once. You save it to your bash alias file to create your own commands.

      A good example for this is docker compose -f when you work alot if compose files ! Having an alias for docker compose -f as dcf saves hours a month xD

  • Tekhne@sh.itjust.works
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    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.

  • applemao@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    2 months ago

    I think just doing it more, and thinking it’s cool to interact more directly. At least that helps me. I do feel bad for dyslexic peiple though, it’s a lot harder for them to use CLI.

    • Random Dent@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      Yeah that was it for me. Just keep regular backups and bear in mind that you’ll probably break stuff at first. But once you get the hang of it, it’s like a whole other level of control over your system.

      Also I’m not dyslexic but would things like tab completion and aliases help maybe? I sometimes shorten often-used commands with aliases just for convenience (as an example, I use rsync a lot, particularly the command rsync --ignore-existing -ravwhich I just shorten to rs to save time) so maybe that could also be used to avoid mis-spelling?

      • applemao@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        Thats a good idea, i have not made any aliases yet. Also remembering all of those aliases is another challenge ha. I keep a text file named commands on my desktop with a whole bunch of commands I forget.

        • Random Dent@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 months ago

          I have some mapped to super simple aliases too like e1 to reboot, e2 to shutdown etc. I don’t remember why I started doing that, but that way I only have to remember which number does what lol.

  • Shayeta@feddit.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 months ago

    Knowing:

    • pwd, ls, cd, cat/less, cp, mv, rm, rmdir, rm -rf, ls -lah
    • command --help
    • man command | grep thing I care about
    • bonus points if you have tldr command installed
  • AndrewZabar@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    As someone who started with nothing but command line - Timex Sinclair, Apple IIe, DOS, I can’t even relate to the concept of being scared of command line.

  • yesman@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    2 months ago

    I am a Linux noob as far as the desktop goes. But I’m quite comfortable in the terminal because for years I’ve maintained a home server running Debian. After I install the OS, I unplug the keyboard and monitor and the only way to talk to that box is through SSH.

    • phantomwise@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      using tldr instead of man 90% of the time to preserve your sanity

      🎉 COLORS ! READABILITY ! CONCISION ! CONCRETE EXAMPLES ! 🎉

      • FauxLiving@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 months ago

        tldr is very useful

        Also, knowing vim keys is useful because a lot of terminal programs use them.