Open
Conversation
|
I like the idea of allowing flexibility, but I also really like the one-letter default commands. Have you considered revising this patch to instead set a bashmarks prefix var (if one isn't already set in the sourcing environment), and defaulting it to an empty value to preserve the existing commands for everyone else? Perhaps something like this: Then, in your .zshrc, all you'd need is this: |
Author
|
I,ll try ! |
|
The solution proposed by @briancline is a very elegant one. I've submitted a pull request, but I'm not sure how active this repo is anymore; in case you're interested, my fork has this update: https://github.com/bachya/bashmarks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When i use it in my zsh,I found some command conflicts,i guess others face this problem,
so i change all command to add prefix 'bm' .