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

Why you might want to use tome instead #50

Open
markstos opened this issue Jun 2, 2023 · 0 comments
Open

Why you might want to use tome instead #50

markstos opened this issue Jun 2, 2023 · 0 comments

Comments

@markstos
Copy link
Contributor

markstos commented Jun 2, 2023

The sub project is stable and effective as it is, but it also several issues that haven't been addressed over the past 10 years and there's been no activity at all for a couple of years.

tome was inspired by sub and addresses several of outstanding issues with sub including:

  • Support for sub-sub-commands
  • Fixed ZSH completion
  • Implemented Fish completion
  • Ability to take advantage of updates to the upstream project (because it doesn't use code-generation).

Tome is written in Rust, which means it starts up and runs faster as well. If the above issues are important to you, tome may be better choice. But there are also some issues with Tome. I've linked to issues discussing their possible resolution with Tome:

Despite the lack of activity in this repo, if the current feature set works for you, sub continues to work, as it only uses rather stable bash features which will continue to work for years to come.

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

1 participant