All my folders have ?~V? before them and I cannot enter into directories with the enter key. Any ideas? I installed via pathogen. Here is a screenshot of what I'm experiencing: http://screencast.com/t/X9jarQ9W
nerdtree uses a couple of unicode arrow chars next to directories and it looks like your version of vim cant handle those chars. The fix is to stick this in your vimrc: let g:NERDTreeDirArrows=0. This makes the tree use a more old school looking ui with no unicode chars.
Can you paste the results of :version here? I want to know if there any vim compile time options that indicate it cant handle unicode. Assuming it is vim and not the terminal thats the problem :-/
Thanks, dude! That fixed it = )
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jan 5 2012 20:58:08)
MacOS X (unix) version
I had this problem too, and your solution fixed it for me as well using the same version as calvin.
If you'd still like to try to get the arrow characters to work, here is my answer from http://stackoverflow.com/questions/7375198/why-does-my-nerd-tree-have-these-odd-characters. I run Arch Linux, so your mileage may vary.
I had this exact same problem and was able to fix it by uncommenting UTF-8 and leaving ISO-8879-1 commented out in /etc/locale.gen. Then I ran locale-gen and restarted. Also added 'export LANG=en_US.UTF-8' to my .bashrc. Here are the results of my locale settings once it started working:
[lysistrata@(none) ~]$ locale -a
I would like to get the arrows to work as well, but I'm on Windows. Any ideas?
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
MS-Windows 32-bit GUI version with OLE support
I had almost the same problem on Mountain Lion 10.8.4 and Vim 7.3
Setting vim encoding to utf-8 with set encoding=utf-8 fixed it.
This happens with Putty on Windows ssh'ed into an Ubuntu box.
The export LANG=en_US.UTF-8 suggestion didn't help, and in fact makes the cursor "consume" characters as you move around. let g:NERDTreeDirArrows=0 does fix it, but then I'm looking like a grandpa stuck in ASCII days.
This is broken again.
Don't know what happened, but it fixed itself, nvmd