Live data from Hacker News

Vim on Cloud9 IDE

cloud9ide.posterous.com

21–26 of 26 posts

Re: Vim on Cloud9 IDE

#21
Very cool! Cloud9 is, IMHO, getting closer and closer to being a legitimate choice for non-trivial development work. A few requests for this plugin, though:

* Allow me to remap my keys...especially . I prefer to use for since I don't like reaching with my pinky

* I like that ':' takes me to the console, but why does it also enter a ':' character into the console? This means that executing a console command from the keyboard requires ':'++...which kinda sucks

* Vimscript support? I realize this is completely non-trivial, but there are certain plugins that I simply cannot live without (yankring, for example...actually, just give me yankring and I'll forget about Vimscript support for now ;-)

Overall, though, I like what I see so far (you even implemented visual mode, yay!). Keep up the good work!

Re: Vim on Cloud9 IDE

#22

Earlier quoted context omitted.

Did you ask for help in our support page or on Github issues? We try to be very responsive. What problem are you having exactly?

Thanks for replying. Yes, i did visit the issues page on Github and it seemed others were experiencing a similar issue, and there was talk about changing the paths in some of the .js files, but i lost track of which file paths needed changing to what. I've just doing a fresh install of the back of a git clone in a clean dir and get "Error. require.paths is removed" upon doing 'Node bin/cloud9.js'

This seems to be a Node 0.6 issue. We're almost done adapting Cloud9IDE to run on Node 0.6. For the time being please use the node version that is packaged with Cloud9IDE. (Run the shell script bin/cloud9.sh)

Re: Vim on Cloud9 IDE

#23

Very cool! Cloud9 is, IMHO, getting closer and closer to being a legitimate choice for non-trivial development work. A few requests for this plugin, though: * Allow me to remap my keys...especially . I prefer to use for since I don't like reaching with my pinky * I like that ':' takes me to the console, but why does it also enter a ':' character into the console? This means that executing a console command from the k…

jj is another good remap for Esc.

    :imap jj 

Re: Vim on Cloud9 IDE

#24
post #23

Very cool! Cloud9 is, IMHO, getting closer and closer to being a legitimate choice for non-trivial development work. A few requests for this plugin, though: * Allow me to remap my keys...especially . I prefer to use for since I don't like reaching with my pinky * I like that ':' takes me to the console, but why does it also enter a ':' character into the console? This means that executing a console command from the k…

jj is another good remap for Esc. :imap jj

I tend to use jj far too much, so I mapped to jk

Re: Vim on Cloud9 IDE

#25
post #15

Earlier quoted context omitted.

Ok. Let's try that: support/node-builds-v4/node-linux64: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory Wait, what? Ahh, I have a newer version installed and it really wants the old 0.9.8. Let's fake the links and see what happens: ./cloud9/bin/cloud9.sh: line 11: 23557 Segmentation fault support/node-builds-v4/node-linux64 bin/cloud9.js "$@" -a x-www-…

Okay, I didn't know my node was a version behind, but are you really telling me checking out node.js into another directory and building it is a "real pain"? Maybe beta quality open source software isn't something I'd recommend to you then.

> Maybe beta quality open source software isn't something I'd recommend to you then.

Beta grade software isn't something I would recommend to anyone for the purposes of writing production code. That doesn't mean it's not for everyone, but it's certainly not for me.

Re: Vim on Cloud9 IDE

#26
post #25

Earlier quoted context omitted.

Okay, I didn't know my node was a version behind, but are you really telling me checking out node.js into another directory and building it is a "real pain"? Maybe beta quality open source software isn't something I'd recommend to you then.

> Maybe beta quality open source software isn't something I'd recommend to you then. Beta grade software isn't something I would recommend to anyone for the purposes of writing production code. That doesn't mean it's not for everyone, but it's certainly not for me.

What?

Now you're just playing word games to make me sound unreasonable. Unless you're implying that Cloud9 is going to hack my GitHub account and somehow wipe out my repository, I see no problem whatsoever using a beta text editor to write code.

It's not like the "beta" aspect of the editor is going to slip in some weird bug into the code I'm writing while I'm not looking.

Post reply on HN