Earlier quoted context omitted.
All of that can be done much more efficiently without the mouse: - scrolling with a mouse wheel :h scroll.txt - selecting/resizing a split window :h window-resize :h window-move-cursor - jumping to a specific place in the code /foo or the myriad of cool things in :h motion.txt - making a selection v{motion}
> All of that can be done much more efficiently without the mouse: Surely we don't need to get into this sort of thing here. If you don't know how to do it without the mouse, then it's more efficient to do it with the mouse. If you don't remember how to do it without the mouse, then it's more efficient to do it with the mouse. If you just like using the mouse better, then …. Anyway, and perhaps more importantly, it d…
Vim After 11 Years
121–130 of 254 posts
Re: Vim After 11 Years
#122> With a modern, 256-color terminal like iTerm2 or Gnome Terminal, it will even look like gVim Uh, I use xterm... It's obsolete, I know, but it's still the fastest.
Re: Vim After 11 Years
#123> With a modern, 256-color terminal like iTerm2 or Gnome Terminal, it will even look like gVim Uh, I use xterm... It's obsolete, I know, but it's still the fastest.
Re: Vim After 11 Years
#124netrw comes by default. No need to install NERDTree.
Re: Vim After 11 Years
#125The author mentioned CtrlP for fuzzy filename matching. Its great because it's in pure Vimscript, but in my experience it becomes unusably slow for moderately sized projects. A month or two ago, I switched back to CommandT (requires Vim to be compiled with Ruby support, engine written in C) and haven't thought twice about it since then.
I've been meaning to try out matcher[0] for usage with CtrlP, I'm not sure how well it works but it's written in C and is purported to speed up search. Not sure if it's still being maintained, however... [0] https://github.com/burke/matcher
Re: Vim After 11 Years
#126> With a modern, 256-color terminal like iTerm2 or Gnome Terminal, it will even look like gVim Uh, I use xterm... It's obsolete, I know, but it's still the fastest.
Fastest? Like I'd realize the speed difference between xterm, urxvt or even Gnome Terminal.
Re: Vim After 11 Years
#127https://github.com/alanhamlett/Alan-vimrc
Some features in my vimrc file:
* Code folding for bracket or indention based languages
* Edit multiple files in tabs using minibufexpl plugin
* Using the Solarized color scheme
* Using Vundle for plugin management (apt-get for Vim plugins)
* Common swp, backup, & view directories (No more ~ files left around)
* Useful defaults (spaces instead of tabs, remove trailing newlines, etc.)
Re: Vim After 11 Years
#128Minor nitpick, but can any terminals do squiggly underlines or is that still a gVim only feature?
1 class Hello
~
~
~
~
~
--INSERT--
Like that? Of course; heck, even xterm does that fine. If you were referring to something else, I'm not too sure...EDIT:
Never mind, now I know what you're talking about. No, I don't think you can get those in terminal vim, but I'm pretty sure there is a plugin for it.
Re: Vim After 11 Years
#129Why do people keep suggesting iTerm2? The built-in terminal app on the Mac does Unicode and 256 colors just fine.
iTerm2 has few other fancy features, like horizontal and vertical splitting or Guake-like top-down terminal [0]. [0] http://ivanvillareal.com/osx/setup-iterm2-to-behave-like-gua...
Re: Vim After 11 Years
#130Earlier quoted context omitted.
I agree on most points, but there is no way that wacking Ctrl-W +/-/>/ You can of course make nicer mappings, but even then it isn't as nice.
All these commands take a count: 10 But I tend to keep windows at equal width anyway.
I also resize often, particularly when using vimdiff, because I often use smaller screens (either because I am watching other things in tmux panes at the same time, or because I am working on my eeepc).