• Executive Chimp@discuss.tchncs.de
    link
    fedilink
    arrow-up
    14
    ·
    11 months ago

    Good article. Rather than aliasing `cd …/…" etc. I’ve got this function in my setup:

    up () {
    	local x='' 
    	for i in $(seq ${1:-1})
    	do
    		x="$x../" 
    	done
    	cd $x
    }
    

    This lets me do up 4 to go up 4 directories.

    • Caveman@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      11 months ago

      You could also do a “up” for one up “upp” for 2 and “upppp” for 4 because of fun

    • ENipo@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      11 months ago

      Oh I really like this. I never had an alias for this since I need to do multiple backwards cds very rarely, but I might just copy this

    • Astaroth@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      11 months ago

      I use Fish and have keybinds for previous and next directory, 99% of the time when going up in a directory it’s to (one of) the previous directory/ies I was in

    • beeng@discuss.tchncs.de
      link
      fedilink
      arrow-up
      2
      ·
      11 months ago

      Look into zoxide.

      z direc

      Will take you to the most used directory starting with “direc” eg “/home/me/random/directory”

      • Executive Chimp@discuss.tchncs.de
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        I’ve tried things like that before but never got on with them. I found when I had many projects with similar directory structures it was easy to end up in the wrong place and took more thought to get to the right place than just cding

        • beeng@discuss.tchncs.de
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          11 months ago

          The dir’s are the same names or similar? A few extra key strokes to get the fullname should be easier than cd’ing back and forth.

          There’s also z foo “space” “tab” as per docs to get interactive list for matches.

          But, just a suggestion!

    • PlexSheep@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      What I use to automatically extend stuff like ls .... to ls ../../../..

      function expand-dots() {
          local MATCH
          if [[ $LBUFFER =~ '(^| )\.\.\.+' ]]; then
              LBUFFER=$LBUFFER:fs%\.\.\.%../..%
          fi
      }
      
      function expand-dots-then-expand-or-complete() {
          zle expand-dots
          zle expand-or-complete
      }
      
      function expand-dots-then-accept-line() {
          zle expand-dots
          zle accept-line
      }
      
      zle -N expand-dots
      zle -N expand-dots-then-expand-or-complete
      zle -N expand-dots-then-accept-line
      bindkey '^I' expand-dots-then-expand-or-complete
      bindkey '^M' expand-dots-then-accept-line
      

      (for zsh)

  • TunaCowboy@lemmy.world
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    11 months ago

    Is there a community for people that actually know and use linux or is this just like 'programmer’humor where morons can’t exit vim, use a debugger, or RTFM?

    • Chewy@discuss.tchncs.de
      link
      fedilink
      arrow-up
      6
      arrow-down
      3
      ·
      11 months ago

      How would you define “knowing” and “using” linux? Many people here don’t use Linux professionally and only on the desktop, so they probably aren’t too familiar with all the features of different cli programs.

      Reading a blog post is more accessible than reading a man page. I didn’t know cd -, so reading the post was worth it I’d say.

      • ouch@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        Reading a blog post is more accessible than reading a man page.

        I don’t agree with that assessment at all. People should learn to read manpages, instead of being spoon-fed pieces of manpages in inferior form.

        • Chewy@discuss.tchncs.de
          link
          fedilink
          arrow-up
          3
          ·
          11 months ago

          Any program should have a man page, even if it only lists all options. My point is that a blog post helps some people to learn about a program. For example a post often highlights the most important options of a software.

        • IAm_A_Complete_Idiot@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          11 months ago

          manpages aren’t guides though - they don’t help much in learning new tools, especially complicated ones. They’re comprehensive references, some can literally span hundreds of pages. Useful when you know what you’re doing and what you’re looking for, not great for learning new tools.

  • Synthead@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 months ago

    Some of these tips are dangerous. You generally don’t want cause insensitivity in your shell. Also, ls should never be used as a subshell to find files as a part of commands.

  • hallettj@beehaw.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 months ago

    I use that r function regularly to go to the git project root. But I call it gtop. I mostly use that and zoxide to get around.