refactor: add official init command for plugging inshellisense into shell config startups #229
Conversation
This file contains 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
…o shell config startups Signed-off-by: Chapman Pendery <cpendery@vt.edu>
Signed-off-by: Chapman Pendery <cpendery@vt.edu>
cpendery
changed the title
cpendery
changed the title
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.
I noticed that #202 wasn't working as expected and #222 caused some infinite looping if a user adds inshellisense to their shell startup configuration. This creates an official way for users to setup inshellisense to start in every session. I'm just starting with bash, but I'll expand to the full shell scope shortly like kaldo.