Issue 323 - Potentially fix Custom Bundle Keyboard Shortcuts require (re)activation after update #383
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
…uire-reactivation-after-Update * main: Perfect alignment Move bracket highlighting setting to sit next to syntax highlighting setting Adjust about version display
…uire-reactivation-after-Update * main: Fix wrong imports and warnings on XCode 12 Add complexity script Move file to match XCode organizer
…uire-reactivation-after-Update
…uire-reactivation-after-Update
Jason-Morcos
deleted the
323-fix-Custom-Bundle-Keyboard-Shortcuts-require-reactivation-after-Update
branch
This was referenced Oct 6, 2020
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.
What does this implement/fix? Explain your changes.
Attempted to fix issue 323 regarding third-party bundles not getting keyboard shortcuts applied on upgrade. Still possibly a hole and needs some testing, but thought I would open PR in case someone has a chance to give this thorough review and some solid testing.
Does this close any currently open issues?
Attempt at fixing #323
This needs more testing before we should merge it.