Surprised PeepOpen hasn't been mentioned yet. I use it exclusively with MacVim on OSX. It is a bit unconventional but works amazingly well: http://peepcode.com/products/peepopen
Vim is hard, I just want to click around
31–40 of 98 posts
Re: Vim is hard, I just want to click around
#32Surprised PeepOpen hasn't been mentioned yet. I use it exclusively with MacVim on OSX. It is a bit unconventional but works amazingly well: http://peepcode.com/products/peepopen
I've got this, and I find it's better than Command-T, better than Jamis Buck's now-antiquated FuzzyFinder, and even better than Textmate's own command-t functionality!
At this point, basically, if an editor doesn't support PeepOpen, I won't use that editor.
Re: Vim is hard, I just want to click around
#33Command-T[1] solved this 'problem' for me very nicely. [1]: https://wincent.com/products/command-t
I agree completely about Command-T. I don't use any type of file drawer at all, I tried NerdTree and found it really annoying. The way I see it, you either know where something is already, in which case Command-T does the job, or you don't, in which case you may as well use a console, or just use :edit . in vim to open up the file & folder browser to start browsing around.
Command-T forces you to think: where is this file? And then you type in a handful of characters and retrieve it immediately. To me, that is very vim-like, because it's similar to the editing experience, where you think: what is the most efficient way to do X?
Re: Vim is hard, I just want to click around
#34To me the title reads "I just want to dick around", because ultimately, that's what you're doing.
yeah whole post is kind annoying, he wants to do it, but he will not, maybe he will, no he will not, like a girl.
I didn't find vim that hard at all, just learn it and use it, that is all.
Re: Vim is hard, I just want to click around
#35I'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…
Or even
alias vimtab="gvim -f --remote-tab-silent"
in your .bashrc, .zshrc or equivalent
Re: Vim is hard, I just want to click around
#36VIM defender rushing in. I wrote a post which translates 100 Textmate features into VIM, and vice-versa. In particular, I included a section on getting used to the NERDTree.
Re: Vim is hard, I just want to click around
#37Surprised PeepOpen hasn't been mentioned yet. I use it exclusively with MacVim on OSX. It is a bit unconventional but works amazingly well: http://peepcode.com/products/peepopen
I actually used PeepOpen a lot when I was still on TextMate, but I totally forgot about it after using Command-T for a while. I'll check it out again if I run into any issues. :)
Re: Vim is hard, I just want to click around
#38I 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…
Oddly enough, despite the title, the author of the post switched precisely to this, because the new config he found included the Cmd-T plugin, which mimics TextMate's Cmd-T functionality, which is basically what you're talking about here.
Re: Vim is hard, I just want to click around
#39Earlier quoted context omitted.
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…
I think I will give this a try. Thank you for writing this and taking the time to release it.
Browsing codebases that I am not familiar with is the exact use case for me. For navigating my own project, I do fine with MacVim + Terminal + "mvim in new tab in existing window conf" [1]. But for exploring an unfamiliar codebase, it's too cumbersome.
---[1]---
alias mvim="open -a MacVim.app"
In MacVim Preferences set "Open files from applications" to:
"in the current window"
"with a tab for each file"
Re: Vim is hard, I just want to click around
#40I 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.
One of the biggest shortcomings of vim is the lack of a good ido-mode style file-opener. People seem to rave about command-t, although getting it set up on Windows proved too annoying for me.
FuzzyFinder is nice, but graphically it's a mess. Like everything else in vim, really.