Live data from Hacker News

Vim is hard, I just want to click around

jeffkreeftmeijer.com

21–30 of 98 posts

Re: Vim is hard, I just want to click around

#21

Earlier quoted context omitted.

FuzzyFinder is the easiest file and buffer navigation plugin I've found. You should try it. Fuzzy matching is better than having to keep track of what files you have open and in what order.

:b completes on path. I found FuzzyFinder slow and it interrupted my workflow.

It is slow when it has to first index your files, yeah. Path completion is not really comparable.

Re: Vim is hard, I just want to click around

#22
I don't get it. When I am working on a project I just go to the root project directory and open up vim. NERDTree automatically loads the file structure of the project directory which is my current focus. Why should I need a file-drawer with the unnecessary folders showing?

Re: Vim is hard, I just want to click around

#23

I have a hard time watching people traditionally navigate filetrees and tabs with emacs and ido-mode enabled I press Ctrl+X B to open a buffer, Ctrl+X F to open a file, I typically type 2 or 3 characters from the filename and emacs gives me a list of matches (with autocomplete), usually the first suggestion is correct and I press return to open the file. I barely need to think while I do this, there is no visual clut…

The (admittedly not as good) equivalent to ido-mode in vim is FuzzyFinder.

Re: Vim is hard, I just want to click around

#24
A lot of people miss the issue of browsing through projects that you aren’t familiar with. Auto-completing/fuzzy matching takes more time than actual browsing in such a case, because you’re probably guessing half of the time. Maybe it’s just me, but I find that to be annoying within a minute.

Re: Vim is hard, I just want to click around

#25
post #22

I don't get it. When I am working on a project I just go to the root project directory and open up vim. NERDTree automatically loads the file structure of the project directory which is my current focus. Why should I need a file-drawer with the unnecessary folders showing?

You don’t “should” anything. If you don’t feel the need, then don’t install it.

Re: Vim is hard, I just want to click around

#26
post #22

I don't get it. When I am working on a project I just go to the root project directory and open up vim. NERDTree automatically loads the file structure of the project directory which is my current focus. Why should I need a file-drawer with the unnecessary folders showing?

You don’t “should” anything. If you don’t feel the need, then don’t install it.

A bit harsh response I think. Sorry I did not get my word right. But can you explain why it is useful to you?

Re: Vim is hard, I just want to click around

#27

I have a hard time watching people traditionally navigate filetrees and tabs with emacs and ido-mode enabled I press Ctrl+X B to open a buffer, Ctrl+X F to open a file, I typically type 2 or 3 characters from the filename and emacs gives me a list of matches (with autocomplete), usually the first suggestion is correct and I press return to open the file. I barely need to think while I do this, there is no visual clut…

[deleted]

Re: Vim is hard, I just want to click around

#28
post #26

Earlier quoted context omitted.

You don’t “should” anything. If you don’t feel the need, then don’t install it.

A bit harsh response I think. Sorry I did not get my word right. But can you explain why it is useful to you?

My response wasn't meant as harsh, it just lacked a smiley ;)

I work on a lot of OSS projects and our company does consultancy. This means I browse other’s projects on a daily basis (i.e. I don’t know the filenames yet). That, combined with the fact that I have a deep love for GUI design and platform consistency, has made me come to the conclusion that something like NERDTree wasn't working for me. I tried to keep on going for a few more weeks, but in the end I decided that writing a file browser would cost me less time than I lost during these few weeks.

I’m glad I wrote it, because now I’m perfectly happy with my MacVim setup, which I wasn't before. I’m also very glad I did not decide to revert to using TextMate or any of the other new closed source editors.

To conclude, it’s a bit of a feeling-thing. I’d invite you to try it out for a while to see if it works for or against your flow. No hard feelings either way :)

PS: It might not be apparent from the article, but the browser provides a few more functions that os x users might be used to in other apps. See the last screenshot: https://github.com/alloy/macvim/wiki/Screenshots.

Re: Vim is hard, I just want to click around

#29

I've always been a little puzzled by people who use a file-drawer or file-list or similar addon with Vim, and I now I think I know why: I'm guessing most of these people have Vim open as their One Tool, much like another programmer might have Xcode or Visual Studio open as their One Tool, and they want to get everything done in it. At work, I usually have at least two windows open at all times: Vim full-screen on one…

I do literally the exact same, I rock MacVim in fullscreen surrounded by Terminal sessions on the left and right, left for building/opening files, the right for tailing the syslog.

If only Lion supported multiple monitor full screen.. :S

Re: Vim is hard, I just want to click around

#30

I've always been a little puzzled by people who use a file-drawer or file-list or similar addon with Vim, and I now I think I know why: I'm guessing most of these people have Vim open as their One Tool, much like another programmer might have Xcode or Visual Studio open as their One Tool, and they want to get everything done in it. At work, I usually have at least two windows open at all times: Vim full-screen on one…

I do literally the exact same, I rock MacVim in fullscreen surrounded by Terminal sessions on the left and right, left for building/opening files, the right for tailing the syslog. If only Lion supported multiple monitor full screen.. :S

If you want the "old" MacVim fullscreen mode back (which supports multiple monitor full screen), just throw this into your terminal:

    defaults write org.vim.MacVim MMNativeFullScreen 0
Post reply on HN