• papertowels@lemmy.one
    71·
    10 months ago

    sudo !! to rerun last command as sudo.

    history can be paired with !5 to run the fifth command listed in history.

    • communism@lemmy.ml
      6·
      10 months ago

      Fifth as in fifth most recent command or fifth oldest?

      • papertowels@lemmy.one
        8·
        10 months ago

        I believe it’s the fifth oldest - I think !-5 will get you the fifth impost recent, but I was shown that and haven’t put it into practice.

        The most common usecase I do is something like history | grep docker to find docker commands I’ve ran, then use ! followed by the number associated with the command I want to run in history.

    • Kelly Aster 🏳️‍⚧️@lemmy.worldEnglish
      5·
      10 months ago

      @[email protected] I’ve been working in the bash shell since 1993 and did not know sudo !! was a thing. Good lord, I no longer have to press up, press crtl-left a bunch of times, then type sudo enter space anymore. And I can give it an easy-to-remember alias like ‘resu’ or ‘redo’! Ahahaha, this changes everything! Thank you!!

      • papertowels@lemmy.one
        2·
        10 months ago

        We’re all learning tricks in this thread! Grateful for all y’all nerds.

    • Caveman@lemmy.world
      1·
      10 months ago

      Love these, I used a terminal select from history with fuzzy finding to do the !5 as redo

  • LazaroFilm@lemmy.worldEnglish
    56·
    10 months ago

    cd then ls then cd then ls maybe I’ll throw a ls -a

  • emb@lemmy.world
    45·
    10 months ago

    I really like that cd command. :P

            • unknowing8343@discuss.tchncs.de
              5·
              10 months ago

              It’s in the official docs for zoxide, you are supposed to use the z alias, and many distros just set it up directly like that. I love doing z notes from wherever I am.

              • 7dev7random7@suppo.fi
                32·
                10 months ago

                Description fifth point (5.)

                That doesn’t require a separate package, especially one which uses eval on every new shell. And isn’t messing with my distros or personal aliases (and doesn’t introduce cargo-packaging).

                Simply adding one to two (you get the gist) directories and a keybind for cd .. is more slick. There are cases where you might use pushd . but even then other tooling should already cover your needs.

                It’s also so easy that you can temporarly append to $CDPATH for a specific session. But again, then a second pane or pushd is already available.

                Now downvote me, lemmy.

        • alsimoneau@lemmy.ca
          3·
          10 months ago

          When you set it up you tell it which command you want. Default is “cdi” but I changed it to “cd” immediately.

    • Jeena@piefed.jeena.netEnglish
      61·
      10 months ago

      Hm I wonder, is it really a command? I thought it is just a function of the shell to change the working directory.

  • Jess@lemmy.world
    41·
    10 months ago

    tldr because I am too impatient to read through man pages or google the exact syntax for what I want to do.

    • pixelscript@lemm.eeEnglish
      27·
      10 months ago

      There are exactly three kinds of manpages:

      1. Way too detailed
      2. Not nearly detailed enough
      3. There is no manpage

      I will take 1 any day over 2 or 3. Sometimes I even need 1, so I’m grateful for them.

      But holy goddamn is it awful when I just want to use a command for aguably its most common use case and the flag or option for that is lost in a crowd of 30 other switches or buried under some modal subcommand. grep helps if you already know the switch, which isn’t always.

      You could argue commands like this don’t have “arguably most common usecases”, so manpages should be completely neutral on singling out examples. But I think the existence of tl;dr is the counterargument.

      Tangent complaint: I thought the Unix philosophy was “do one thing, and do it well”? Why then do so many of these shell commands have a billion options? Mostly /s but sometimes it’s flustering.

      • wuphysics87@lemmy.ml
        8·
        10 months ago

        tldr is the first of 4 ways I rtfm. Then -h, man, and then the arch wiki

          • wuphysics87@lemmy.ml
            5·
            10 months ago

            I can appreciate that. Appologies if you know this already, but just don’t like them. Here are some tips.

            It helps a lot to get title/subtitle/flag highlighting. By default man pages are hard to use simply because of how dense they are. It’s much easier to skim when you can separate the parts you are looking for up front from the text.

            Don’t forget ‘/’, ‘n’, and ‘N’. First way to use man pages more effectively is to search them easily. And you can search via regex. Often I’m looking for more info on a particular flag. So I’ll press ‘/’ followed by ‘^ *-g’. For a g flag.

            Take notes on the side. It saves you time later. Your future self will thank you. And you learn a lot by skimming them.

            Man pages can be intimidating/confusing, but, imho, it’s worth training that skill. Even if you are slower up front, it’s totally worth it.

            • vrighter@discuss.tchncs.de
              2·
              10 months ago

              thanks for the advice. I knew about the search feature, but sometimes the stuff you need isn’t even on the page. I have no idea how to find what I need when it’s not in “man cmdname” how am I supposed to know that the feature i want has a dedicated page?

              how could I find certain commands if i didn’t already know it was a shell builtin and not a command? It’s not like you get a manpage saying “this is not a command”. And even if i did have the idea to open the bash page, it’s still useless, because builtins are their own dedicated page. That sort of stuff. It rarely ever makes things easier for me.

              edit, it is occasionally useful phen I have already found what I want on google and just want some more in depth details.

              • wuphysics87@lemmy.ml
                1·
                10 months ago

                Unfortunately, sometimes (often) there is no man page for what you are looking for. So if you get a page not found, that’s usually the case. You can usually find associated pages all the way at the bottom. That helps when what you are looking for isn’t a command, but a reference. I don’t remember exactly where it is, but man pages are stored in a directory. Probably /etc or /usr. You can always dump that list into fzf or use grep to search to see if there is a page for what you are looking for. It’s not a perfect system by any means, but it’s a good one to have in your toolbelt.

              • JackbyDev@programming.devEnglish
                1·
                10 months ago

                If something is a bash built-in run help blah for it’s “man page”

                But yeah, man pages tick me off. Wait until you learn that there are sometimes more than one per command. I have to Google which page is which because they’re all for specific things. man foo is the equivalent of man 1 foo. What’s annoying is that the few times I’ve seen something referenced on another page the entry usually just says something like it’s on “the relevant man page” rather than just telling you exactly which.

                • vrighter@discuss.tchncs.de
                  1·
                  10 months ago

                  ok but that still entails trying random things until i find it. If I didn’t already know it was a builtin i wouldn’t know to search there. The bash thing was just an example. I have learned this stuff since i encountered the problem. This is just me recollecting my experience of trying to use man

  • renzev@lemmy.world
    38·
    10 months ago

    tldr is great. Basically a crowd-sourced alternative to man with much more concise entries. Example:

    $ tldr dhcpcd
    
      DHCP client.
      More information: <https://roy.marples.name/projects/dhcpcd>.
    
      Release all address leases:
    
          sudo dhcpcd --release
    
      Request the DHCP server for new leases:
    
          sudo dhcpcd --rebind
    
  • I_Miss_Daniel@lemmy.worldEnglish
    38·
    10 months ago

    sudo udevadm monitor

    Figuring out which usb device went on holiday.

    • tetris11@lemmy.ml
      8·
      10 months ago

      Wow, super useful command. Starring this comment

  • SinkingLotus@lemmy.worldEnglish
    37·
    10 months ago

    Sudo !!

    It reruns the last command as sudo.

    Pretty useful since I’m always forgetting.

  • pemptago@lemmy.mlEnglish
    371·
    10 months ago

    I went a little overboard and wrote a one-liner to accurately answer this question

    history|cut -d " " -f 5|sort|uniq -c|sort -nr|head -5
    

    Note: history displays like this for me 20622 2023-02-18 16:41:23 ls I don’t know if that’s because I set HISTTIMEFORMAT='%F %T ' in .bashrc, or if it’s like that for everyone. If it’s different for you change -f 5 to target the command. Use -f 5-7 to include flags and arguments.

    My top 5 (since last install)

       2002 ls
       1296 cd
        455 hx
        427 g
        316 find
    

    g is an alias for gitui. When I include flags and arguments most of the top commands are aliases, often shortcuts to a project directory.

    Not to ramble, but after doing this I figured I should alias the longest, most-used commands (even aliasing ls to l could have saved 2002 keystrokes :P) So I wrote another one-liner to check for available single characters to alias with:

    for c in a b c d e f g h i j k l m n o p q r s t u v w x y z; do [[ ! $(command -v $c) ]] && echo $c; done
    

    In .bash_aliases I’ve added alias b='hx ${HOME}/.bash_aliases' to quickly edit aliases and alias r='source ${HOME}/.bashrc' to reload them.

      • pemptago@lemmy.mlEnglish
        6·
        10 months ago

        Yup! Migrated from VSCodium; wanted to learn a modal editor but didn’t have the time or confidence to configure vim or neovim. It’s been my go-to editor for 2+ years now.

        • MigratingtoLemmy@lemmy.worldEnglish
          4·
          10 months ago

          I’ve been using vi (just the basics) for ~4 years, I don’t think I could be arsed to pick up the keybindings the other way around lol. I’ve heard very good things about Helix, of course

          • HeartyOfGlass@lemm.eeEnglish
            3·
            10 months ago

            As another longtime Vi user - I had a hell of a time & wound up switching back lol

            I think for a lot of folks Helix would be intuitive. Vi has her hooks in me, though.

      • huf [he/him]@hexbear.netEnglish
        2·
        10 months ago

        i rely on this in my job. if i really need it, i’ll be using it often enough that it’ll always be in ^R distance :)

  • notfromhere@lemmy.ml
    331·
    10 months ago

    Since nobody has said yet, I use screen pretty heavily. Want to run a long running task, starting it from your phone? Run screen to create a detachable session then the long running command. You can then safely close out of your terminal or detach with ctrl a, d and continue in your terminal doing something else. screen -r to get back to it.

      • huf [he/him]@hexbear.netEnglish
        8·
        10 months ago

        no, tmux is a newer screen. some of us havent switched cos we’re too lazy i guess? i think the common wisdom is that it’s better. i havent tried cos i already know enough of screen and it’s fine for me

      • naught@sh.itjust.works
        1·
        10 months ago

        gnu screen is just a different program than tmux. they do the same thing though

    • gitamar@feddit.orgDeutsch
      8·
      10 months ago

      I recently switched to tmux and boy, it’s way better. I basically use only tmux now anymore. Creating panes to have two processes in one glance, multiple windows, awesome. Plus all the benefits of screen.

      • krash@lemmy.ml
        4·
        10 months ago

        Try zellij. Not as popular as tmux, but very intuitive to use.

      • 7dev7random7@suppo.fi
        2·
        10 months ago

        Maybe someone reading wants to now about prefix+s. This doubles your excitement.

    • papertowels@lemmy.one
      7·
      10 months ago

      In a similar vein, nohup lets you send tasks to the background and seems to be everywhere.

      • pyr0ball@sh.itjust.works
        3·
        10 months ago

        You can’t mention nohup without at least mentioning kill -9 or pkill to slay the monster you created you madman

        • papertowels@lemmy.one
          2·
          10 months ago

          Sometimes I’ll just reboot the entire damn machine just to be safe ;)

        • Caveman@lemmy.world
          1·
          10 months ago

          Eyyy, don’t hate, this is how I start all my work programs. That command is really nice and creates all work programs as children of a single terminal session for easy closing later.

          • pyr0ball@sh.itjust.works
            2·
            10 months ago

            No hate! Just need to make sure people know so they don’t create a bazillion threads without realizing it, or how to stop them effectively

    • tetris11@lemmy.ml
      4·
      10 months ago

      Also, screen can connect to an UART device or serial or anything that offers up a TTY

    • muzzle@lemm.ee
      2·
      10 months ago

      I Always forget to run screen first, so I just rely heavily on dtach

      • 7dev7random7@suppo.fi
        1·
        10 months ago

        Simply change your terminal command to execute the terminal multiplexer of your choice.

        man terminal_of_choice, look for (start) command.

    • krash@lemmy.ml
      1·
      10 months ago

      How does screen / tmux work when detached from a session, how does it keep the session alive (both when running locally, and while ssh:ing to a server)? Is there a daemon involved?

      • darvit@lemmy.darvit.nl
        1·
        10 months ago

        You can find out by running screen and executing pstree, that way you can see how the screen process is run.

  • zlatiah@lemmy.world
    31·
    10 months ago

    clear because apparently I am too scatterbrained to comprehend more than one full page of text in the terminal

    • feddylemmy@lemmy.world
      6·
      10 months ago

      I like using CRTL+L to clear. It’s nice because you can have a command typed out and still be able to press CTRL+L to clear the screen and keep the command typed out.

    • mexicancartel@lemmy.dbzer0.comEnglish
      4·
      10 months ago

      I almost never use clear because i’m afraid if i will need the text later.(just like infinity tab number on firefox)

        • zlatiah@lemmy.world
          1·
          10 months ago

          Oh god I also do this… See the comment below, I ran history|cut -d " " -f 5|sort|uniq -c|sort -nr|less on my personal laptop, my third most commonly used command (behind ls and cd) is just typing in nothing…

        • mexicancartel@lemmy.dbzer0.comEnglish
          1·
          10 months ago

          100 tabs is in mobile. I don’t even scroll back to clutter my brain but its there. Tabs are history for me… So I use firefox focus and if there is anything important, i open with firefox.

          What script are you reffering to? To log all output? I don’t wanna store that but need an assurance that its there till i close terminal window lol

  • BougieBirdie@lemmy.blahaj.zoneEnglish
    271·
    10 months ago

    Not a specific command, but I learned recently you can just dump any executable script into ~/bin and run it from the terminal.

    I suffer greatly from analysis paralysis, I have a very hard time making decisions especially if there’s many options. So I wrote a script that reads a text file full of tasks and just picks one. It took me like ten minutes to write and now I spend far more time doing stuff instead of doing nothing and feeling badly that I can’t decide what to do.

    • friend_of_satan@lemmy.worldEnglish
      23·
      10 months ago

      This is because $HOME/bin is in your $PATH environment variable. You can add more paths that you’d like to execute scripts from, like a personal git repo that contains your scripts.

  • itsame@lemmy.world
    25·
    10 months ago

    pushd and popd to change directory and go back when done there.

      • lluki@feddit.org
        29·
        10 months ago

        cd - undoes the last cd. Not quite push/popd but still useful. Pro tip, works also: git checkout -

        • med@sh.itjust.works
          4·
          10 months ago

          Hell yeah. Every one of these threads makes me more inclined to read man pages

      • HeartyOfGlass@lemm.eeEnglish
        26·
        10 months ago

        Oh. I know. But you don’t understand - I’m compelled to type it out. I must.

        • ripcord@lemmy.world
          1·
          10 months ago

          I used to, but the terminal clear is better, so I don’t.

        • 7dev7random7@suppo.fi
          1·
          10 months ago

          Someone who doesn’t know the benefits of dedicated, unlimited scrollback buffers. This command is useful but has a bad effect (when unintentionally).

          • ripcord@lemmy.world
            2·
            10 months ago

            No, I do. Clearing the scrollback because I want a new, very clear start point for a new activity and don’t care about the rest is frequently the goal.

            If I do care about the history I’ll do something else or possibly been saving history to disk, although that’s far more rare.

    • Pup Biru@aussie.zoneEnglish
      1·
      10 months ago

      i’d like to introduce you to your new best friend: reset… it doesn’t everything clear does and a LOT more

    • carg@feddit.orgEnglish
      1·
      10 months ago

      haha, I can relate to that :). formerly I had the compulsion to execute sync frequently. Now my compulsion is to push Ctrl-C like 4 times every time I need it. I read somewhere that’s common because of ^C has a lack of feedback to the user, so, a script showing an alert that the clipboard received some information helped with this compulsion.