Installation instruction's function code snippet should be different for installed with go & mention add env variable for editor permanently in bashrc #72
Replies: 1 comment 8 replies
-
10000
-
|
This is just linux 101. Don’t think README should teach *nix basics. |
Beta Was this translation helpful? Give feedback.
-
|
So what exactly you think will be nice to add? I also want to keep readme clean and minimalistic. |
Beta Was this translation helpful? Give feedback.
-
|
Here's two potential ideas: Add the golang case as a comment in the code block, like function ll {
cd "$(llama "$@")"
#cd "$(~/go/bin/llama "$@")" if you installed with go
}and change Or, you could move the entire |
Beta Was this translation helpful? Give feedback.
-
Maybe better explain what is $PATH var and how *nix systems lookup binaries with some docs on how go install work? |
Beta Was this translation helpful? Give feedback.
-
|
That would work, so maybe like: Use |
Beta Was this translation helpful? Give feedback.
-
|
I don’t like it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I think the installation instructions should include:
~/go/bin/llama, then the function code snippet added to.bashrcshould becd "$(~/go/bin/llama "$@")"instead ofcd "$(llama "$@")". At least that's how it was for me..bashrc(works with micro) like "You can permanently add it by adding theexport LLAMA_EDITOR=microline to your.bashrc", etcMy environment is WSL - ubuntu, if that makes a difference
PS: I like llama, pretty intuitive to use
Beta Was this translation helpful? Give feedback.
All reactions