fix: refer to "ocv" instead of "opencode" in session continue messages and help text - #248
Open
devkev wants to merge 2 commits into
Open
fix: refer to "ocv" instead of "opencode" in session continue messages and help text#248devkev wants to merge 2 commits into
devkev wants to merge 2 commits into
Conversation
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
1 participant
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.
The
opencode -s ...problem has been biting me since I started using opencode-vim - every few weeks I will absent-mindedly forget and copy-paste the "opencode -s ses_..." to reload a session with new config (or whatever), and then be confused for a while when things aren't quite the same as they were... because I should have done "ocv -s ses_..." instead. This fixes that problem by adjusting the message to instead sayocv -s .... It also updates theocv helpandocv --helpoutput so that the commands are listed as "ocv foo", rather than "opencode foo", which is another source of potential confusion.