Gate One 1.1 Released: Run Vim In Your Browser 150
Riskable writes "Version 1.1 of Gate One (HTML5 terminal emulator/SSH client) was just released (download). New features include security enhancements, major performance improvements, mobile browser support, improved terminal emulation, automatic syntax highlighting of syslog messages, PDFs can now be captured/displayed just like images, Python 3 support, Internet Explorer (10) support, and quite a lot more (full release notes). There's also a new demo where you can try out vim in your browser, play terminal games (nethack, vitetris, adventure, zangband, battlestar, greed, robotfindskitten, and hangman), surf the web in lynx, and a useful suite of IPv6-enabled network tools (ping, traceroute, nmap, dig, and a domain name checker)." Gate One is dual licensed (AGPLv3/Commercial Licensing); for individuals, it's pay-as-you-please.
Nano is all that? (Score:5, Insightful)
From wikipedia [wikipedia.org]:
nano implements some features that Pico lacks, including colored text, regular expression search and replace, smooth scrolling, multiple buffers, rebindable key support, and (experimental) undoing and redoing of edit changes.
I poked around nano's website [nano-editor.org] and it seems pretty capable.
It sounds like nano does everything you need, so there is no reason to learn about other editors.
I have fond memories of pine and pico; maybe I will look at nano one of these days.
fwiw, I find some powertools worth learning to use well even if they have a non-easy learning curve (sed comes to mind). This also applies to text editors; they're just tools.
As for "1975 wants vi back", I actually get a lot of mileage from vim [vim.org] which is a bit closer to nano's era.
nano: born 1999 as TIP, inspired by pico.
(btw, the last item on the nano news page [gnu.org] is from 2009: "Now on Twitter and Facebook and Happy 10th Birthday nano". Is nano under active development these days?)
vim:born 1988, released 1991 (initially for amiga, much more widespread now), inspired by vi (note I do feel sorry for anyone stuck using "classic vi" in the same way I'd feel sorry for anyone stuck with edlin).
(side note: vi-style learning curve sucks. My first two weeks were Painful, but now that I have some skill (muscle memory) with the keys I find it very effective. Kind of like how touch-typing is harder to learn than "hunt & peck" but it is still well worthwhile to learn how to touch-type; it pays dividends. Most of vi-style power (for me) comes from the fast navigation+editing commands that are tied to a rather terse (and admittedly cryptic) "shorthand" language of key combinations... I remember actually being surprised at how clunky arrow key + mouse navigation felt when I first used conventional editors after driving vi-style for a while.)
One of the things I like about having learned Vim is it will be available pretty much wherever I might need to work: here are some of the targets from from wikipedia's vim page [wikipedia.org] (* indicates ports I have used):
AmigaOS (the initial target platform), DOS, Microsoft Windows 95/*98/Me/*NT/*2000/*XP/*Server 2003/*Vista/*Server 2008/*7, IBM OS/2 and OS/390, OpenVMS, QNX, *Unix, *Linux, BSD, and Mac OS. Also, Vim is shipped with every copy of Apple Mac OS X. Independent ports of Vim are available both for Android and iOS.
(I've also found vim for aix; useful if one needs to spend time there.) Note that vim seems pretty consistently fully featured on the various platforms I've used it on (*'s above).
By comparison, nano seems pretty content to excel in linux distributions (redhat & debian).
And maybe, possibly, kind of sort of windows: from the nano faq, 3.9 How about in Win32 [nano-editor.org]
We're still working on documentation for enabling synax highlighting on Win32; please bear with us. Note that the nano.rc file must remain Unix formatted in order for nano to understand it. In other words, you should use probably only use nano to edit its config file. Other programs like Wordpad and Notepad will either convert the file to DOS format when saving, and the latter does not even properly read Unix-formatted files to begin with.
*shrug* I'm glad nano is working for you in the land of the modern linux desktop.
As for emacs: I sincerely believe that emacs users enjoy the capabilities they find; I may find a need for something emacs does well these days. I've never heard anyone say "Yeah,