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

Navi cheats for Navi itself #380

Closed
unknowledgeable opened this issue Aug 17, 2020 · 3 comments · Fixed by #599
Closed

Navi cheats for Navi itself #380

unknowledgeable opened this issue Aug 17, 2020 · 3 comments · Fixed by #599
Labels
new feature New feature or request

Comments

@unknowledgeable
Copy link

I'm finding it amusing/ironic when I can't remember the commands for navi itself. Would be great to have navi cheats in the main repo by default instead of having to do navi --help.

@unknowledgeable unknowledgeable added the new feature New feature or request label Aug 17, 2020
@welcome
Copy link

welcome bot commented Aug 17, 2020

Thanks for opening your first issue here! In case you're facing a bug, please update navi to the latest version first. Maybe the bug is already solved! :)

@denisidoro
Copy link
Owner

denisidoro commented Aug 17, 2020

Normally one shouldn't use too many different commands for navi. Could you explain your use-case?

I, for one, only use navi as-is and once in a while navi best <query>.

@unknowledgeable
Copy link
Author

Just seeing as I use it for a cheatsheet for uncommon tasks that I don't feel the need to create aliases for, the uncommon task for adding new cheats from a repo escaped me. I fired up ctrl-g, as I've become accustomed to for things like weird git issues, expecting a reminder to do "navi repo browse" and to my surprise there wasn't anything there.

I feel it would be quite a good introduction on how to use and configure navi too.

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

Successfully merging a pull request may close this issue.

2 participants