11–20 of 98 posts
Earlier quoted context omitted.
You can click on NERDTree with a mouse-enabled vim, for the record.
I know, I've used it for a while, but somehow it just didn't feel right, if you know what I mean. :)
For me, vim is surprisingly similar to drinking scotch: I first tried it at age 19, and wasn't pleased with my experience at first. But a wise mentor informed me it took a little getting used to, showed me how to do it right, and after a month or two I loved it.
I too wanted to click around the first month (+/-) after switching to vim, I think we all did. However, it seems like the author learned the basics of vim, but stopped before he learned about powerful navigation keys, visual mode etc. I think the moral is: if you feel you don't get the hang of vim/nerdtree etc., don't give up - keep going, there is a reason why so many people use it.
Yes. All the tutos I have read recently insist on using hjkl, which is a matter of taste, but do not emphasize what I believe is the most important (for terminal use): cut and paste.
- Easy cut and paste in Vim is done with yy and p, avoid mouse and ctrl-c/v or any other trick that is not "inside" Vim.
- Good trick are to first select a block with .
- Don't forget P, which is pasting above current line or before cursor, often more logical than p.
- This implies to open different files inside the same Vim instance, using :Explore or :edit
- If you have to copy some outside text inside Vim, by all means, use the paste mode (:set paste), if you don't you'll mess up your text.
At work, I usually have at least two windows open at all times: Vim full-screen on one monitor, a terminal full-screen on the other—or sometimes one terminal taking up most of the screen and another smaller terminal tailing a logfile. The Vim window gets used for editing (of course), the terminal is used for running test suites and exploring the codebase and finding and opening files in Vim. The reason I've never felt the need for a file-browser plugin in Vim is because I've always used Vim with an external file-browser. :)
If anyone's interested in opening files in an existing gvim window from the terminal, here's the script I use in Linux:
gvim -f --remote-tab-silent "$@" &
The author mentions trying to get around this with the nerdtree plugin. I stay away from heavy plugins like this because I think they compete with the minimalism that is so nice to the feel of vi. But I can see why you'd be attracted to it given the difficulty of dealing with multiple files. I do this to get nice access to multiple files: set hidden " allows files to be opened in background nmap :bp " edit prev file…
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.
I found FuzzyFinder slow and it interrupted my workflow.
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 clutter on my screen, and I can usually finish the before someone could take their hand from the keyboard to the mouse and move to the filetree
I too wanted to click around the first month (+/-) after switching to vim, I think we all did. However, it seems like the author learned the basics of vim, but stopped before he learned about powerful navigation keys, visual mode etc. I think the moral is: if you feel you don't get the hang of vim/nerdtree etc., don't give up - keep going, there is a reason why so many people use it.
> don't give up Yes. All the tutos I have read recently insist on using hjkl, which is a matter of taste, but do not emphasize what I believe is the most important (for terminal use): cut and paste. - Easy cut and paste in Vim is done with yy and p, avoid mouse and ctrl-c/v or any other trick that is not "inside" Vim. - Good trick are to first select a block with . - Don't forget P, which is pasting above current lin…
I too wanted to click around the first month (+/-) after switching to vim, I think we all did. However, it seems like the author learned the basics of vim, but stopped before he learned about powerful navigation keys, visual mode etc. I think the moral is: if you feel you don't get the hang of vim/nerdtree etc., don't give up - keep going, there is a reason why so many people use it.
The way people work differs from person to person, the idea that someone should always just keep on trying, even if something doesn't feel right, is in my opinion useless. The real moral here is that people should accept that everybody is different and that it’s ‘ok’ for them to be different and how great it is that open-source software such as vim enables them to do so. Something that’s unfortunately always a bit harder for passionate users. (No insult intended!)
I definitely know that _I_ prefer to browse a project with a GUI that works like in the rest of my platform of choice, but I also know I’m very different from the average vim user :)
Earlier quoted context omitted.
> don't give up Yes. All the tutos I have read recently insist on using hjkl, which is a matter of taste, but do not emphasize what I believe is the most important (for terminal use): cut and paste. - Easy cut and paste in Vim is done with yy and p, avoid mouse and ctrl-c/v or any other trick that is not "inside" Vim. - Good trick are to first select a block with . - Don't forget P, which is pasting above current lin…
[deleted]