Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Info: Ranger plugin #71

Open
rc2dev opened this issue Dec 16, 2022 · 5 comments
Open

Info: Ranger plugin #71

rc2dev opened this issue Dec 16, 2022 · 5 comments

Comments

@rc2dev
Copy link

rc2dev commented Dec 16, 2022

First of all, thanks for this great tool.

I just switched from zoxide and missed a plugin for ranger. So I started to put one together here. Feel free to comment and suggest improvements.

Best regards.

@rc2dev rc2dev changed the title Info Info: Ranger plugin Dec 16, 2022
@agkozak
Copy link
Owner

agkozak commented Dec 16, 2022

Good to hear from you! I don't use ranger, but I remember trying it a while back and being impressed. There was another person who developed a plugin for zsh-z; you can find it here (we discussed it in issue #55). I don't have time to play around with either this week, but perhaps you can tell me how the two plugins compare? Thanks!

@rc2dev
Copy link
Author

rc2dev commented Dec 16, 2022

Hi Alexandros,

Good to hear from you.

I'm aware of the plugin you mentioned, but it seems to have dropped zsh-z support. The README now only mentions rupa/z, and when trying to use it with zsh-z it throws an error (as it calls _z instead of zshz).

As for other differences, for now my plugin has these extra features:

  • Automatically adds the directories you visit in ranger to zsh-z database.
  • Tab completion (:z foo<TAB>).
  • Some error handling in case zsh-z is not found.

Best regards. :)

@agkozak
Copy link
Owner

agkozak commented Dec 16, 2022

That sounds great. In about a week I'll be finished with a big project, and then I'll give your plugin a try.

@mhagnumdw
Copy link

I just switched from zoxide

Hi @rc2dev , can you say why? I'm exploring these plugins. Tks!

@rc2dev
Copy link
Author

rc2dev commented Mar 31, 2024

Hi @mhagnumdw,

At that time (as I remember) my reasons were mainly:

  • Version. Some distros shipped older versions of Zoxide that missed important features to me. So on some of my devices I had to compile zoxide manually with cargo to be usable. On other hand, zsh-z would have the exact same version on each of my machines, with no hassle.

  • Organization. The zsh-z installation could be done directly by my zsh plugin manager, together with the other plugins I used. This was neater than having to install the zoxide package on each system. It also made sense as I considered zsh-z part of my shell experience, and just deploying my dotfiles would take care of installing it.

Having said that, I've gone back to zoxide for the following reasons:

  • I'm also using Bash on some machines, and zoxide works on both Zsh and Bash.
  • Zoxide version is not a problem anymore (for me).
  • I dropped most zsh plugins (now I mostly use a theme plugin) and I don't use a plugin manager anymore.

I hope this helps you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants