Closed dnlgrv closed 9 years ago
What is the default keybinding to toggle Nerdtree? I personally toggle it a lot.
I don't think it sets any keybinds for you at all, so there isn't a default keybind for toggle.
I'm not opposed to changing the keybinding. I am opposed to outright removing it.
@saterus Totally agree, that's why I changed it to
+1 to keep gt
to vim's default keybind of :tabnext. If we want to use a different mapping instead of removing it completely, I'm fine with that.
I agree. I'm a macvim guy but for a terminal user it's probably a bit maddening. I say we bind nerdtree to F2
, which I could swear used to be the nerdtree default.
I don't mind changing it, but :-1: to using F-keys.
Considering I made this PR in March someone should either close it or merge it.
But for the love of god don't use an F-key binding.
+1 leader g
I support reverting gt
and gT
back to vim's defaults.
In my own config, I map leader-t
to :NERDTree
and leader-T
to :NERDTreeFind
.
In cbus we use leader-t
to invoke CtrlP, and it' s pretty entrenched.
Oh yeah, that's right. I use Ctrl+P
to invoke CtrlP.
There's gotta be another free key which can be used with the leader to toggle NERDTree.
Well my PR actually changes it to
I think we've come to the conclusion that gt and gT should be restored to defaults nad leader g will be nerdtree. We're going to use leader-G for nerdtreefind
Opened a new PR that's more up to date with this config change: https://github.com/neo/vim-config/pull/46
I think we should avoid overriding any of the default vim keybinds, unless it is adding something that works similar to the original.
Something that has always bugged me is that the Neo vim-config changed gt to toggle NERDTree, rather than leaving it as the default :tabnext.
Does anyone else feel the same? I'll always run with this config in my own fork but I'd prefer not to have to!