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

Error detected while processing function nerdtree#ui_glue#invokeKeyMap #1102

Closed
9 tasks done
scrawld opened this issue Apr 14, 2020 · 0 comments · Fixed by #1103
Closed
9 tasks done

Error detected while processing function nerdtree#ui_glue#invokeKeyMap #1102

scrawld opened this issue Apr 14, 2020 · 0 comments · Fixed by #1103
Labels

Comments

@scrawld
Copy link

scrawld commented Apr 14, 2020

Self-Diagnosis

  • I have searched the issues for an answer to my question.
  • I have reviewed the NERDTree documentation. :h NERDTree
  • I have reviewed the Wiki.
  • I have searched the web for an answer to my question.

Environment (for bug reports)

  • Operating System: Ubuntu 18.04.2 LTS
  • Vim/Neovim version :echo v:version: 800
  • NERDTree version, found on 1st line in NERDTree quickhelp ?: NERDTree (6.7.5) quickhelp
  • vimrc settings
    My Vimrc: https://github.com/scrawld/vimrc/blob/master/.vimrc
    • I've verified the issue occurs with only NERDTree installed.

Steps to Reproduce the Issue

  1. This error occurs when you modify a file without saving it and then press s through NERD_tree

Current Result (Include screenshots where appropriate.)

With version 6.6.1 there is no such problem.
This problem only appeared after the update today.


Error detected while processing function nerdtree#ui_glue#invokeKeyMap[1]..80[33]..79[3]..<SNR>30_openVSplit[1]..109[1]..125[3]..181[6]..182[17]..16:
line    1:
E37: No write since last change (add ! to override)
Press ENTER or type command to continue
```

image

Expected Result

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

Successfully merging a pull request may close this issue.

1 participant