Live data from Hacker News

VIM Destroys All Other Rails Editors

adamlowe.me

31–40 of 42 posts

Re: VIM Destroys All Other Rails Editors

#31
post #20
post #3

Cream is a good VIM editor on Windows.

I never seemed to understand cream. The idea is to take vim and basically castrate it by getting rid of the standard keybindings and ways of doing things to make it 'easier' for non-vim users. It even appears they got rid of modal-editing. The issue with this then they don't learn how to do things the vim way which defeats the purpose of using vim, just go use notepad++ or any other gui editor you get the same experi…

Agreed. You can go into "expert" mode and use it with the normal vim bindings, though. Used in this manner, it does provide a bit of a better introduction to vim, as you learn the various modes and keybindings, but still get a reasonable UI for configuration and whatnot.

Re: VIM Destroys All Other Rails Editors

#32
The thing that always gets me when trying to use either vim and emacs for IDE-like programming (and don't get me wrong...I have used vim for regular editing for years), is that someone says, "yeah, (vim|emacs) destroys all other editors and IDEs. You just need to install this list of 400 plugins, write some elisp to configure it, learn each of these 200 keystrokes, understand where the plugins overlap and contradict, and you're golden".

Versus, download Eclipse/Netbeans, open, and start coding.

I want to use vim as an IDE...I just don't have the time.

Re: VIM Destroys All Other Rails Editors

#33

The headline is cheerful, ironic attention-grabbing; the writer acknowledges text editor choice is a preference, then lays out briefly how to set up vim for RoR development.

No offence, but this comment sounds more like a one generated by a bot of some kind.

shrug I almost didn't read the link because I halfway expected lame editor advocacy. There's a non-RTFAing comment or two already that assumes it is.

Re: VIM Destroys All Other Rails Editors

#34
post #32

The thing that always gets me when trying to use either vim and emacs for IDE-like programming (and don't get me wrong...I have used vim for regular editing for years), is that someone says, "yeah, (vim|emacs) destroys all other editors and IDEs. You just need to install this list of 400 plugins, write some elisp to configure it, learn each of these 200 keystrokes, understand where the plugins overlap and contradict,…

When I tried Eclipse, I found it as foreign as emacs, just GUIer. IDEs and editors require learning and configuration once you get much past notepad or pico.

Re: VIM Destroys All Other Rails Editors

#35

The headline is cheerful, ironic attention-grabbing; the writer acknowledges text editor choice is a preference, then lays out briefly how to set up vim for RoR development.

Translation: The author uses a flame to bait people into reading his opinion.

Re: VIM Destroys All Other Rails Editors

#36
post #32

The thing that always gets me when trying to use either vim and emacs for IDE-like programming (and don't get me wrong...I have used vim for regular editing for years), is that someone says, "yeah, (vim|emacs) destroys all other editors and IDEs. You just need to install this list of 400 plugins, write some elisp to configure it, learn each of these 200 keystrokes, understand where the plugins overlap and contradict,…

It sounds like the challenge is similar to that of a Linux distribution: where it's not just a matter of "installing Linux", but choosing one that has most of what you want already.

Perhaps there's a need to have "vim distributions" and "emacs distributions" that come pre-installed and preconfigured according to certain needs, such as this one.

Re: VIM Destroys All Other Rails Editors

#37
post #19

Earlier quoted context omitted.

You needn't ever say "cat myfile | ..." period! The shell has stdin redirection built in via '<'

Unless you want to read your pipeline from left to right, like everything else you read.

What if you want the subject on the right, like all non-pipeline commands you read?

  foo myfile
  bar 

Re: VIM Destroys All Other Rails Editors

#38
post #6
post #4

+ for mentioning all tpope's plugins/bundles. - for some poor suggestions.

Pray tell, what are your suggestions and criticisms? A friend of mine after a horrible computer bitswap, bit into vim after TextMate. I wanted to follow, just to learn. This is actually fantastic for me -- there are various . configs I knew nothing of, but now can grep/google for info. Please advise.

He had some things incorrect that have been mostly fixed now. Don't worry too much about it.

FYI, I suggest leaving tabstop=8 if you indent with spaces like a good boy.

Re: VIM Destroys All Other Rails Editors

#39
post #19

Earlier quoted context omitted.

You needn't ever say "cat myfile | ..." period! The shell has stdin redirection built in via '<'

Unless you want to read your pipeline from left to right, like everything else you read.

you can also say

  $ 

Re: VIM Destroys All Other Rails Editors

#40
post #38
post #6

Earlier quoted context omitted.

Pray tell, what are your suggestions and criticisms? A friend of mine after a horrible computer bitswap, bit into vim after TextMate. I wanted to follow, just to learn. This is actually fantastic for me -- there are various . configs I knew nothing of, but now can grep/google for info. Please advise.

He had some things incorrect that have been mostly fixed now. Don't worry too much about it. FYI, I suggest leaving tabstop=8 if you indent with spaces like a good boy.

Thanks for the good feedback to the post. I responded to the latest feedback from you and discussed with the Pope.
Post reply on HN