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

Bindings with backslash causes error #735

Closed
ecly opened this issue Aug 13, 2017 · 6 comments
Closed

Bindings with backslash causes error #735

ecly opened this issue Aug 13, 2017 · 6 comments
Labels

Comments

@ecly
Copy link

ecly commented Aug 13, 2017

Running vim 8.0.851 on linux, newest nerdtree.
I'm trying to make '' open the selected file in a new vertical split.
I got it working just fine with Backspace, but can't seem to get '' working.

It actually registers the bind but merely crashes. The backslash seems to be perhaps escaping a quotation mark?

My bind in my .vimrc looks like this.

let NERDTreeMapOpenSplit='<BS>'
let NERDTreeMapOpenVSplit='\'

When '' is pressed on on a file in nerdtree the following error occurs:

E114: Missing quote: "\")
E116: Invalid arguments for function nerdtree#ui_glue#invokeKeyMap

Is there an alternative way for me to make this bind, or is it not possible with the current interpretation?

@lifecrisis
Copy link
Contributor

I was able to confirm this bug. I would say avoid doing this for now. This is pretty low priority... we've never seen anyone complain about this before.

@lifecrisis lifecrisis added the bug label Aug 29, 2017
@ecly
Copy link
Author

ecly commented Sep 1, 2017

Definitely not a dealbreaker. I'm merely trying to attain some sort of consistency with split binds for all places applicable. Backspace and backslash are the ones I've gone with, so it's only a slight nuisance. Thanks for confirming for starts!

@undg
Copy link

undg commented Feb 4, 2019

Is there any workaround for it? I'm using this key for spiting in many places of my system.

@ecly
Copy link
Author

ecly commented Feb 4, 2019

@und3rdg I am using for many things as well - never managed to find a workaround.

@undg
Copy link

undg commented Feb 4, 2019

I will need to live with that. :/

@ecly
Copy link
Author

ecly commented Feb 18, 2019

Thank you for this @PhilRunninger it works great.

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

No branches or pull requests

3 participants