161–170 of 237 posts
Earlier quoted context omitted.
Just watch the video of the page http://blog.extracheese.org/2010/11/screencast-custom-vim-re... to get the gist of "entire blocks of code with the flick of a finger".
Wow. That guy's VimFu is crazy. I wish I was half as fast as he is.
Earlier quoted context omitted.
Some of my coworkers use sublime, and have been very excited about it. I used vim for several years and use emacs now, so probably a hard sell. Still, I get curious when people are Really Excited about other editors (because there may be ideas worth stealing and adding to emacs ;) ). What's the "minimap", the scrollbar that is a shrunken version of the document? The "multiple carets" feature seems handy. Are there an…
Yes, the minimap is what you guessed it was. Other ST features that Vim/Emacs don’t have (by default, at least): • You can use proportional fonts (I use Verdana) • The interface chrome is graphical, not text in a grid. This allows nice details such as a drop-shadow from the minimap when it covers the text and proportional fonts in the file tree’s filenames. • On a Mac with smooth scrolling, you can scroll smoothly pi…
Also, all the people I know using ST are ex-vimmers, and use its vim emulation mode. A data point, I suppose.
And yes, agreed on the open-source-ness, though commercial support does have its advantages.
* I know you can do X forwarding and so on, but, eh.
Earlier quoted context omitted.
I recently discovered a way to learn Vim without fear: learn undo ('u') first! If you know that, you can just mess around with Vim commands until you inevitably screw something up, undo the changes, relax, take a deep breath, and Google whatever you're trying to do.
and Ctrl + R for redo.
:earlier 10m
:later 10m
Earlier quoted context omitted.
There are multiple variables in your equation. You may be altering the wrong one.
What are you talking about? His job?
Seriously, it's a language sufficiently verbose and inexpressive to effectively require an IDE. If you're just going to be generating 70% of your code from your IDE, why is it there in the first place?
For me pragmatism wins the day. Vim has been installed on every machine I've ever ssh'ed into. Not true for emacs or even nano or pico.
Just as pragmatic, and I get to use all my nice normal Emacs features at the same time.
Earlier quoted context omitted.
What are you talking about? His job?
Java. Seriously, it's a language sufficiently verbose and inexpressive to effectively require an IDE. If you're just going to be generating 70% of your code from your IDE, why is it there in the first place?
Earlier quoted context omitted.
What are you talking about? His job?
Java. Seriously, it's a language sufficiently verbose and inexpressive to effectively require an IDE. If you're just going to be generating 70% of your code from your IDE, why is it there in the first place?
Unless I'm missing something, specialized non-VIM IDEs tend to be much better at auto completion (especially in C++), jump-to-definition, refactoring, etc. IDE users (who typically are ignorant to VIM) can use these features with extreme productivity. On the other hand, VIM users tend to be rather ignorant of how incredibly productive you can be and how nice it feels to have these powerful context-sensitive tools at your fingertips (and sorry, but CTAGS is useless). Regardless of what IDE you use, nobody can deny IMO that having an editor look up APIs and function lists for you in a context-relevant manner is productivity-boosting versus the alternate of scanning headers manually.
So in this sense I think both VIM/EMACS and IDE users are ignorant to other editor paradigms. What I don't like is how each party tries to claim that their method is the best, without having truly tried both.
I've used both extensively (used VIM for years) and I prefer IDEs by far, but that's just my personal preference.
My first week in college a distant relative of mine at the same school pulled me into the Sun lab. The sum-total of his instructions were: * This is how you log in. * This is ls. * This is cd. * This is man. * This is apropos. * Learn vi. * Have fun. What came from that 5 minute intro to Unix has been applied orders of magnitude more often than anything from 5 years of an EE degree.
Not to detract from your point, which was similar to my intro to Unix, but I've always preferred 'man -k' to apropos, because it means remembering only one command plus it is slightly less typing.
A long time ago I narrowly escaped being like that exactly, but with TECO :-)
I've learned not to fret about people's choice of editor. FOr instance, if someone was happy in NotePad, as long as it didn't affect me, I learned not to care. (I might grit my teeth in frustration, watching them flail for minutes at something I could do in seconds with my choice of editor, but that's my problem).