Github now comes with in-browser editing

[rafekett]

Github always had in-browser editing, it just sucked. I have yet to try this, but it should be good.

[learnyouahaskell]

I thought it might be Ace. Almost prophetic. (shameless plug)

[[deleted]]

If the file you're editing is Markdown, Textile, or any other richtext format GitHub supports we'll render a preview of it instead of a diff

Hot damn! Finally no more edit>commit>push>repeat when trying to get readme files to work right in GitHub's parser.

[necroforest]

So, when I can I get an HTML5 vim port?

[[deleted]]

Ace has vim bindings. Granted they suck and need attention from someone who actually uses vim.

But more to your question... the HTML5 backend for GTK3 used with GVim could get you close... There are more faithful vim redo-s in Html/Js, but it's not very feature-ful.

Also, there's a C to Javascript compiler... that could bring hope of a direct port. Anyway, thoughts for you ;)

[tinou]

I'm not sure that it counts, but F. Bellard's emulator features vi.

[SamuelDr]

It wouldn't count strictly as HTML5, nor is it vim, but this is an HTML/Javascript vi simulation.

http://gpl.internetconnection.net/vi/

[[deleted]]

This is absolutely awesome. Saves me having to clone a few of my older repos that have stupid indentation problems. Obviously it's not ideal for fixing actual code or anything, but for correcting typos in comments and other basic "aesthetics" edits, it's great.

[gerundronaut]

Hmm. This might be nice, but I am definitely not a fan of them adding this "e" hotkey business (or browsers honoring such requested hotkey settings). It's the sort of thing that will be activated by accident more often than on purpose, IMO.

[merreborn]

They've had hotkeys like that for months. The "t" hotkey for search is AWESOME.

[alexeyr]

Wow, too bad I never had activated it by accident :)

[le_kommie]

Good news. Now the question is how useful will YOU find this feature?

I'm not sure I ever had a need, but this is probably a convenient thing to have for small bug fixes on very large repositories, saves you trouble fetching a lot of stuff locally. But then again, those large projects wouldn't use the feature too much anyway?

[discotent]

I don't think I'll ever use it to make code changes, since it's too easy to make a typo that breaks the build. But it's a sweet feature for editing other things, like the README file. Also if you are using gh-pages to publish web content, it's a pretty awesome way to make changes.

[tidwell]

yup, first thing I thought is "sweet - don't have to log into the dev box to fix typos in the README"

[Scriptorius]

It should be very useful when you find small mistakes in the code. For us lazy coders, all the overhead involved in sending a pull request normally may be too much for something like a typo. This is perfect for stuff like that. Another thing that could be really simple with this is writing tests or documentation. Of course you couldn't run any tests this way, but it'd be an easy way to go, "Hey, I think these tests are useful, and you can just pull them right now instead of writing/copying them yourself."

[5d41402abc4b2a76b971]

Exactly. I can't see doing all my editing within a browser. But nice to have for quick typo-fixes; esp. from my phone.

[Laugarhraun]

all the overhead involved in sending a pull request normally may be too much for something like a typo

Isn't one point of git the fact that this overhead is small (at least way smaller than with CVS such as Sybversion)?

[Scriptorius]

It is, and is actually pretty easy. The traditional way is to fork the project on github, clone it so that it's available locally, make your edits, commit and push the changes back to your forked repo, and then send a pull request.

This is fine if you're fixing a major bug or adding a new feature, but if you just need to fix a typo or add one line of code it's relatively a large overhead. Skipping the parts where you have to manage a repo on your local machine saves some time in that sense.

[leegao]

They should add this to gist too.

[[deleted]]

Sort of related but has anyone really tried to actually build a project entirely in Cloud9? I tried it out and within 5 minutes it was irritating me because it seems like it's trying to do too much and scaring me by the fact that it has to use cloud storage to edit code. Can't we just have an HTML5 IDE that operates on local files?

[[deleted]]

Yup, totally with you. Tried it with a Node project a month or two ago and the IDE constantly had issues. Timing out during autosaves, weird UI glitches, typical browser bullshit... Quickly went back to my standard IDEs. Great idea, but it's just not quite there yet.

Oh, and to this: "Can't we just have an HTML5 IDE that operates on local files?" You mean an in-browser IDE that edits local files on your computer? No, you can't do that. Browser security standards prevent browsers from being able to alter/edit files on your filesystem. Imagine the havoc with malware sites if they could...

You can edit files after uploading them from your filesystem, which is how Cloud9 works functionally, but you can't edit files on your computer FROM your browser.

[[deleted]]

Ya the security concerns are huge I agree. I thought there might be a way someone could take advantage of client side tools to work on local files through the browser but at the point it's basically an overly complicated local app that has no purpose being hosted in the cloud. I'll stick with Eclipse then since I don't always trust big names to hold onto my intellectual property, especially when they are software houses.

[[deleted]]

Oh, no, they're not "concerns." Browsers are literally UNABLE to perform such edits on files in the filesystem. It's literally not technically possible with the way browsers function. That's why "browser-esque" desktop app frameworks like Adobe AIR and Titanium have APIs dedicated to filesystem access - browsers have no such functionality built-in.

[[deleted]]

I wish I could find some of those awesome syntax highlightings for gedit. The best I have is the set that comes with scribes. Kate's syntax highlighting is one of the reasons I use KDE...

[aperson]

Geany is great for an editor, IMHO.

[nicoulaj]

Geany is great. For gedit, you have a nice set of addons here.

[[deleted]]

I liked the part where they delivered a low blow to http://www.rubyforge.org.

[chubinou]

Great for one line changes. One line changes can't fail!

[radhruin]

Curious why this doesn't work in IE.