I've tried to use vim for a while but I've given up pretty quickly. Yes I'm aware that the learning curve for any new editor is steep but that's not why I've given up on vim.
I do all my source code editing in a Windows environment and my choice of editor is Source Insight[1].
I haven't found any editor that allows me to navigate the source three so elegant and fast. I only do embedded development so I can't speak for it's abilities outside C.
One with Vim
111–120 of 129 posts
Re: One with Vim
#112I am waiting for the retro-fashion to go back to ed (http://www.gnu.org/fun/jokes/ed.msg.html).
Re: One with Vim
#113Earlier quoted context omitted.
You should instead consider switching to the mainline FuzzyFinder instead of the FFTextmate fork. FuzzyFinder is undergoing lots of activity. You can also try using tabs to represent views of several buffers at once -- for example, I use one tab per app when working on Django code. I have the views, models, templates etc. in split buffers inside one tab.
he's better off switching to command-t, FuzzyFinder is pretty limited in comparison
Care to elaborate?
I just glanced over the Command-T docs and it seems to be a one-trick-pony ("search in path") whereas FuzzyFinder supports a wide range of scopes (path, buffers, tags, etc.).
Re: One with Vim
#114Vim is easier on the hands, but Emacs (with ido-mode) still feels better for working with multiple files: (length (remove-if (lambda (b) (not (buffer-file-name b))) (buffer-list))) 42
There are multiple similar plugins for vim.
There are multiple vim emulation packages for Emacs too, it just ain't the real thing.
Re: One with Vim
#115Am I foolish for not believing the vi/vim hype? I understand that it's been around for as long as rocks, and that it's quite handy since it's available everywhere. I use it daily, in fact, but rarely for more than basic editing. I'll just come out and say it: my favorite editor is Visual Studio. Sure, it's slow to load and rather fat now, but I'm talking solely about the editing functionality. With vim, I have to cli…
Your comments about Vim's learning curve are spot on, and I don't think any vimmer will disagree with you, but the argument they make (which I agree with) is that the cost/benefit ratio is worth it. If you only code every now and then, so you've got a lot of time between sessions to forget things, and not a whole lot of time in total, then something like Visual Studio which has good 'discoverability' is going to be b…
> Your comments about Vim's learning curve are spot on, and I don't think any vimmer will disagree with you
I would disagree with the gp's assertion that there is an extreme amount to learn to obtain basic editing efficiency. A dozen commands or so and gvim so you can use the mouse should take you 20 minutes and a bit of practice to feel comfortable with.
Re: One with Vim
#116Earlier quoted context omitted.
And don't forget eclim, a Vim front-end for Eclipse (or an Eclipse back-end for Vim): http://eclim.org/
Sounds exciting but a little scary. Have you used it?
I have used it in order to develop an eclipse plugin for vim. It took some time to set up, but then it worked as advertised. I could use vim inside eclipse. It exposes all the mistake detection and completion stuff of the regular Eclipse editor, but triggered by keybindings instead of automatically.
Re: One with Vim
#117selfish question here: Does anybody know how to setup vim so that :! recognises aliases? something like... set shellcmdflag=-O\ expand_aliases\ -c
I always start vim from within xterm (bashrc has already run and aliases are already set up). It just works. I can use :!ll (or ctrl-z and 'll' in the sub-shell) and it just works. Not sure why it wouldn't for you.
ctrl-z doesn't start a sub-shell, it backgrouns vim and returns you to the parent shell.
And maybe he's running gvim or from a login shell that hasn't sourced his bashrc.
Re: One with Vim
#118Am I foolish for not believing the vi/vim hype? I understand that it's been around for as long as rocks, and that it's quite handy since it's available everywhere. I use it daily, in fact, but rarely for more than basic editing. I'll just come out and say it: my favorite editor is Visual Studio. Sure, it's slow to load and rather fat now, but I'm talking solely about the editing functionality. With vim, I have to cli…
I'll just come out and say it: my favorite editor is Visual Studio Not to be overly pedantic, but your favorite IDE is Visual Studio, and you just happen to use whatever crappy editor component comes bundled with it. If we could have full-blown Vim embedded inside IDEs instead of good-but-incomplete plugins which merely give you some of the key mappings, I'd be elated and couldn't see why anyone would stick with the…
I use Visual Studio with ViEmu and Visual Assist X.
While I really hated Visual Studio (and still do), this combination of tools really makes it worthwhile. It is an awesome marriage of a mediocre IDE, some substantial refinements to make it usable, and a phenomenal text editor. The nice thing about ViEmu is that is extremely full-featured. It even reads my entire .vimrc with all my customizations and personal magic!
So, I guess what I want to say is that instead of deciding between using an IDE and a text editor, you should actually use both! Real progress lies in synthesis, not analysis!
Re: One with Vim
#119Earlier quoted context omitted.
That's all very interesting. I'm primarily a desktop C++ developer, so I don't run into the headaches of things like VS's database connectivity. I recommend giving 2010 a go. If I recall correctly, 2010 was the version where they drastically reworked Intellisense. In previous versions, even my moderately-sized projects would break Intellisense upon reaching x lines of code. I don't think the multi-monitor support is…
If the intellisense is the complaint, nothing beats the Visual Assist plugin. VS10's intellisense is better than what it used to be but still nowhere near VA. Also, VS10's WPF-based UI is a nightmare, but that's another discussion...
Finally took a look at Visual Assist, as I've heard about it but never looked at it. That's very impressive. How much does it affect VS's speed on a fairly normal system?
Re: One with Vim
#120Earlier quoted context omitted.
you can copy and paste from the system clipboard as the + register - use "+y to yank to the system clipboard and "+p to paste from it (depending on OS, you may need to use * instead of +). This allows cutting and pasting between vim and other applications (including other instances of vim). For editing multiple docs with vim, I find it's easier to use multiple buffers in the same window. Use :b to jump back and forth…
Thanks, works great. When memorize the keystrokes I hope it will be as fast as regular yanking. I actually use tabs for multiple files and these keybindings for navigation: nmap T :tabedit nmap H :tabprevious nmap L :tabnext So I can go into a project dir and do vim -p .c* which opens the file in tabs and just navigate with Shift-H and Shift-L
proper formatting:
nmap T :tabedit
nmap H :tabprevious
nmap L :tabnext