Skip to content
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

ModeHandler: error handling key=<C-a>, err=TypeError: Cannot read property 'match' of undefined #3332

Closed
kenorb opened this issue Jan 5, 2019 · 3 comments

Comments

@kenorb
Copy link

kenorb commented Jan 5, 2019

Describe the bug

The following error popup.

To Reproduce

It's not clear to what file it relates to.

Expected behavior

No error.

Screenshots

image

Environment (please complete the following information):

  • Extension (VsCodeVim) version: v1.0.0
  • VSCode version: 1.30.0
  • Electron: 2.0.12
  • Chrome: 61.0.3163.100
  • Node.js: 8.9.3
  • V8: 6.1.534.41
  • OS: Ubuntu Linux x64 4.18.0-13-generic
@jpoon
Copy link
Member

jpoon commented Jan 5, 2019

To provide context on why you are now seeing this error, is that with v1.0.0, we've decided to show vim extension errors as these alerts so that it would be easier for users to identify errors when vscodevim is misconfigured (ie. remappings, neovim) or when things are not working as expected. We've always logged it to the console, but this wasn't very discoverable. The related configurations are below if you would like to go back to the old behaviour of living in bliss/ignorance of these errors 😅 :

Setting Description Type Default Value
vim.debug.suppress Boolean indicating whether log messages will be suppressed. Boolean false
vim.debug.loggingLevelForConsole Maximum level of messages to log to console. Logs are visible in the developer tools. Supported values: 'error', 'warn', 'info', 'verbose', 'debug'). String error
vim.debug.loggingLevelForAlert Maximum level of messages to present as VS Code information window. Supported values: 'error', 'warn', 'info', 'verbose', 'debug'). String error

Now, in terms of this particular error, what were the series of keypresses that you did to generate this error?

@kenorb
Copy link
Author

kenorb commented Jan 5, 2019

I don't know what keypresses I used, noticed the error after a while. If this happen again, I'll update.

@xconverge
Copy link
Member

xconverge commented Jan 6, 2019

I can repro this if I am at the end of the document! G<c-a> or any empty line

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants