-
Notifications
You must be signed in to change notification settings - Fork 120
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
tweak a couple commands in VS code #477
Conversation
This is working on my personal branch, but when I tried to tested on a branch equivalent to the latest dictation tools/caster/develop everything worked except for a a couple commands such as 'settings'.I think everything should be okay but would you mind testing this because I think there was something weird going on on my computer? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - just need to tidy up the rdescripts. Please tidy any others you see as well that don't conform to the style.
Take a moment to resolve the conflicts and will see about getting this merged. |
It looks like the merge conflicts are basically me adding rdescripts. In a few cases those are unnecessary, but in a few of the merge conflicts I think they are important since the command does not make it obvious what the command does and how it differs from other similar commands. When I resolve the merge conflict, do I need to side with dictation toolbox/caster or can I merge in favor of my changes? In VS code I believe I have the option to accept either my changes or the dictation toolbox/caster changes |
Merge conflicts exist simply because you your pull request was issued on a version that has had changes. The idea is to respect changes made since by others while integrating your own. In terms of rdescripts feel free adapt that as needed to explain commands in a concise few words or to remove them altogether the command is self-explanatory. |
I think this is done,I would remove the "waiting for user reply" tag |
This doesn't work. The non-CCR rule needs to be created first and then referenced in the |
Sorry about that. I just fixed the problem as Mike directed. I also added one command "comment" and moved another "copy path". I tested some command from both rules and they work. I believe this pull request is now done. |
Mike's requested we hold off on changes to applications as he's working in a re-factor. Once that's done this will merge. |
All right @alexboche #604 has been merged. Merged conflicts we should be good to go, |
Okay I think this one is done now. |
No description provided.