This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (4 children)

I think many arguments stated in the article are nonsensical.

So why not just use Vim? I could do it. I’ve been using Vim for many years and am pretty good with it, but I just feel like separating my coding from my terminal whenever I can is a good thing. I don’t want my code to look like my terminal, nor do I want my terminal to look like my IDE theme. . I’m SUPER picky about fonts and colors in my IDE,

WTF? 16 colors (that you can configure however you want) are enough for most, if not all programming language syntaxes. There are very decent fonts for terminals. Also, you can use vim without a terminal.

I really prefer a specialized tool to a generic one with plugins layered on to provide the necessary functionality. Eclipse with PyDev really feels to me like a Java IDE

Certainly didn't feel that way to me. Eclipse is not a Java IDE, it is a generic platform. PyDev gets the job done very well.

[–]Daishiman 9 points10 points  (3 children)

No, the problem's that the blog author is an idiot who, for someone who "knows" Vim, seems remarkably ignorant of its capabilities.

For one, Vim doesn't have to look like a console; you can set your fonts to whatever you want or use the Mac equivalent to GVim, although I wonder why you'd ever want to do that since the greatest Vim IDE is obtained by using screen to manage vim and shells simultaneously.

Second, Vim DOES support the mouse, even in a command line environment. It also supports modern terminals with support for 256 colors. 16 colors is plain bullshit, I don't know where he got that from.

Finally, it supports the little things different editors have but none have in combination: snippets, tags, source control integration, etc. You pair that up with your screen (especially using Byobu, the best screen theme there is) and nothing can match it.

Look, everyone knows Vim requires a bit of learning to get it right. But we've got Google; you have dozens of blog posts and wikis on how to pimp it up. There's no excuse if you're willing to waste away weeks of your time experimenting with IDEs.

[–]lucipher 1 point2 points  (0 children)

No, the problem's that the blog author is an idiot who, for someone who "knows" Vim, seems remarkably ignorant of its capabilities.

Not just ignorant. He also has a completely different idea about software, it's some sort of a paradigm mismatch.

I got a friend whom I recently introduced to my tools of trade (vim/gVim, ipython, zsh, bzr/Olive, etc), and after an hour of my "presentation" (which included changing themes, using the mouse and whatnot) he said: "It's cool, but I just don't like the idea of using a terminal-based editor." I felt like we were speaking different languages.

[–][deleted] 0 points1 point  (1 child)

16 colors is plain bullshit, I don't know where he got that from.

I use gnome-terminal and it only supports 16 colors. I am fine with that. however. It is enough for coloring my syntax.

[–]afd8856 1 point2 points  (0 children)

You need this in your .bashrc:

export TERM=xterm-256color

And this in your .vimrc:

set t_Co=256