-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Digraph support #3407
Digraph support #3407
Conversation
Travis tests have failedHey @jbaiter, Node.js: 8if [[ $(git diff-index HEAD -- *.js *.ts *.md) ]]; then git diff; echo "Prettier Failed. Run `gulp forceprettier` and commit changes to resolve."; exit 1; fi
TravisBuddy Request Identifier: 8150f4a0-1f4d-11e9-aff3-67b9a3119b8a |
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.
This is dope!
@@ -491,7 +540,7 @@ class CommandNavigateAutocompleteDown extends BaseCommand { | |||
@RegisterAction | |||
class CommandNavigateAutocompleteUp extends BaseCommand { | |||
modes = [ModeName.Insert]; | |||
keys = [['<C-p>'], ['<C-k>']]; | |||
keys = ['<C-p>']; |
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.
This would be a breaking change. Not certain if this is ok...
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.
I couldn't get it to work otherwise, since the <C-k>
shortcut will always prevent the <C-k> <any> <any>
shortcut from firing.
I'm not even sure if <C-k>
is actually referenced anywhere in the original vim for navigating up in the omnicomplete popup. All references to <C-k>
in the neovim source code refer to digraphs. And the <C-k>
for digraphs is definitely in the muscle memory of a lot of vim users.
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.
I'm trying to figure out what the appropriate keybinding would be for CommandNavigateAutocompleteUp
and CommandNavigateAutocompleteDown
.
These were initially added as a part of #1980. Likewise, I don't see <c-j>
documented as autocompletedown in vim docs.
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.
It's defined here:
https://github.com/vim/vim/blob/d09091d4955c5f41de69928f2db85611ed54ed23/runtime/doc/index.txt#L157-L159
<C-n>
for down, <C-p>
for up.
Travis tests have failedHey @jbaiter, Node.js: 8if [[ $(git diff-index HEAD -- *.js *.ts *.md) ]]; then git diff; echo "Prettier Failed. Run `gulp forceprettier` and commit changes to resolve."; exit 1; fi
npm test --silent
TravisBuddy Request Identifier: 73c69b80-25a8-11e9-8e3a-a568437420b3 |
Travis tests have failedHey @jbaiter, Node.js: 8if [[ $(git diff-index HEAD -- *.js *.ts *.md) ]]; then git diff; echo "Prettier Failed. Run `gulp forceprettier` and commit changes to resolve."; exit 1; fi
npm test --silent
TravisBuddy Request Identifier: 30f79ff0-25af-11e9-8e3a-a568437420b3 |
Travis tests have failedHey @jbaiter, Node.js: 8if [[ $(git diff-index HEAD -- *.js *.ts *.md) ]]; then git diff; echo "Prettier Failed. Run `gulp forceprettier` and commit changes to resolve."; exit 1; fi
npm run build
npm test --silent
TravisBuddy Request Identifier: d0c3c440-2ec0-11e9-9ea4-33062c9ac3a7 |
What this PR does / why we need it:
This PR implements support for digraphs.
All of the digraphs available in the current neovim version can be entered with
<C-k> <any> <any>
.Additionally, users can configure custom digraphs with the
vim.customDigraphs
configuration key. It maps two-character shorthands to a pair of a descriptive string and one or more UTF16 code points:A filterable list of all available digraphs can be obtained with the ex command
:dig[raphs]
, same as in Vim.Which issue(s) this PR fixes: #3267
Special notes for your reviewer: Unfortunately I had to remove the
<C-k>
shortcut forCommandNavigateAutocompleteUp
, since it prevented the<C-k> <any> <any>
shortcut from being called.