Can’t imagine using my system without this.

  • WhyJiffie@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    56 minutes ago

    it gained 14k+ stars on github in a year (development started in 2023 july).

    isn’t it a bit suspicious?

    maybe it’s nothing, but this just caught my eye

    • Eyck_of_denesle@lemmy.zipOP
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      6 hours ago

      Yes. I switched to yazi from ranger. File previews is so much better. Image previews dont hog up ram or crash your manager. It has everything and more like opening encrypted archives, plugin support, themes. I use 2 plugins, one to compress files and the other to display present directory size.

      It’s not just the features but the app itself is magnificent. I have never seen such a goid looking tui app.

      • Eager Eagle@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        Same, ranger was painfully slow at times. For some reason it would take multiple seconds to start on a few machines I connected it to.

  • asap@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    7 hours ago

    As someone new to Linux, what would be a few reasons that you prefer this to using the built-in GUI file browser?

    • Eager Eagle@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      4 hours ago

      I can’t believe no one mentioned this, but: remote access.

      I spend most of my day connected to machines via SSH and yazi offers a great UX with file previews and all. Using kitty I even get image previews in the terminal.

    • Eyck_of_denesle@lemmy.zipOP
      link
      fedilink
      arrow-up
      14
      arrow-down
      1
      ·
      7 hours ago

      I can navigate without using my mouse. It’s faster for me. You can create tabs, copy and paste files, extract compressed files, run commands, and so much more without lofting my hand. My favorite feature is the ability to preview files without even opening them. I’m relatively new to linux too.

    • sloppy_diffuser@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      7 hours ago

      Download 5 seasons of some show from multiple sources or some artist’s entire discography, and want to normalize all the file names? It is way easier in the terminal.

      I’ll check this out, but I use https://github.com/stevearc/oil.nvim for such tasks as I have nvim’s full sweet of editor commands to rename all the files way faster than I could in a GUI. I’m sure there are GUI apps to perform a similar task, but I already know how to use nvim.

    • ninjaturtle@lemmy.today
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 hours ago

      You can probably do some more advance tasks via CLI. Also usually lists information faster. But honestly you will be overall fine with GUI a majority of the time.

      Some people just like being in the terminal.

    • Chewy@discuss.tchncs.de
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      7 hours ago
      • Terminal file manager are useful on a server over ssh.
      • ripgrep and fd support is better than any GUI file manager find and replace.
      • Some people like using vim keybindings
      • The three panel view is really useful. On the left is the parent folder, the middle the current and on the right a preview, e.g. the selected folder or the contents of a picture or a text file. It’s faster to navigate and pop back into the shell.
  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    6 hours ago

    I’ve installed it for a while and lot of stuff work out of the box, including images in the terminal. But I did not get around to use it more often. It’s pretty good and I think its a full replacement for the usual terminal file managers, but don’t take my word for it. I previously used vifm a little bit and have no other experience.

    • Eyck_of_denesle@lemmy.zipOP
      link
      fedilink
      arrow-up
      2
      ·
      6 hours ago

      I used ranger and it’s a solid improvement over it. If you are into tui apps you will love it, if you aren’t it’s ok. It also has plugin system, I use 2 plugins to compress files and get file size info. I love it.

      • thingsiplay@beehaw.org
        link
        fedilink
        arrow-up
        2
        ·
        5 hours ago

        I often use it to navigate into a directory, using it as a directory selector (auto cd on exit). An essential plugin to me is https://github.com/yazi-rs/plugins/tree/main/jump-to-char.yazi , to have a Vim like quick jump with f and a letter and n for next. The default f functionality to filter is now set to F, so I don’t lose that by overriding.

        Still need to handle archives too. I also want to write my own plugins someday if I get to use it more often.

        • Eyck_of_denesle@lemmy.zipOP
          link
          fedilink
          arrow-up
          2
          ·
          5 hours ago

          It does handles all types of archives by default. Encrypted ones too.

          How do you auto cd, I always wanted that but didn’t brother to check docs for it. If I remember correctly it’s by launching it as a shell script.

          • thingsiplay@beehaw.org
            link
            fedilink
            arrow-up
            1
            ·
            4 hours ago

            Yes, it’s a simple shell function; needs to be a function in your bashrc, not a script, because cd doesn’t work like that. Just copy the function from https://yazi-rs.github.io/docs/quick-start#shell-wrapper into your .bashrc:

            yy() {
                local tmp
                local cwd
                tmp="$(mktemp -t "yazi-cwd.XXXXXX")"
                yazi "${@}" --cwd-file="${tmp}"
                if cwd="$(cat -- "${tmp}")" && [ -n "${cwd}" ] && [ "${cwd}" != "${PWD}" ]; then
                    builtin cd -- "${cwd}" || return
                fi
                rm -f -- "${tmp}"
            }
            

            I use yy instead single y.