Skip to content

Commit

Permalink
Fix broken links in README.md (#3842)
Browse files Browse the repository at this point in the history
Fixes broken links regarding logging level settings. As far as
I can tell, these links have never been valid, and should direct
to the information regarding VSCodeVim's settings.
  • Loading branch information
aquova authored and jpoon committed Jun 22, 2019
1 parent 6612f7b commit d76f13a
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -317,7 +317,7 @@ Custom remappings are defined on a per-mode basis.

1. Are your configurations correct?

Adjust the extension's [logging level](#vimdebuglogginglevel) to 'debug', restart VS Code. As each remapped configuration is loaded, it is outputted to console. In the Developer Tools console, do you see any errors?
Adjust the extension's [logging level](#vscodevim-settings) to 'debug', restart VS Code. As each remapped configuration is loaded, it is outputted to console. In the Developer Tools console, do you see any errors?

```console
debug: Remapper: normalModeKeyBindingsNonRecursive. before=0. after=^.
Expand All @@ -329,7 +329,7 @@ Custom remappings are defined on a per-mode basis.

2. Does the extension handle the keys you are trying to remap?

VSCodeVim explicitly instructs VS Code which key events we care about through the [package.json](https://github.com/VSCodeVim/Vim/blob/1a5f358a1a57c62d5079093ad0dd12c2bf018bba/package.json#L53). If the key you are trying to remap is a key in which vim/vscodevim generally does not handle, then it's most likely that this extension does not receive those key events from VS Code. With [logging level](#vimdebuglogginglevel) adjusted to 'debug', as you press keys, you should see output similar to:
VSCodeVim explicitly instructs VS Code which key events we care about through the [package.json](https://github.com/VSCodeVim/Vim/blob/1a5f358a1a57c62d5079093ad0dd12c2bf018bba/package.json#L53). If the key you are trying to remap is a key in which vim/vscodevim generally does not handle, then it's most likely that this extension does not receive those key events from VS Code. With [logging level](#vscodevim-settings) adjusted to 'debug', as you press keys, you should see output similar to:

```console
debug: ModeHandler: handling key=A.
Expand Down

0 comments on commit d76f13a

Please sign in to comment.