Re: Fwd: The $20 Android tablet
dmccunney <[email protected]> Wed, 30 Apr 2014 20:14:34 -0400
| Newsgroups | gmane.comp.handhelds.palm.peditors |
|---|---|
| Message-ID | <CAF4AJDxmrPTJpXy2MBLmrLstEvg82QwCRRC1wBfcmsVCDfzqkg@mail.gmail.com> |
On Wed, Apr 30, 2014 at 6:57 PM, Voytek <[email protected]> wrote: > On April 30, 2014 1:01:25 AM GMT+10:00, dmccunney . >> >>Other things added are the RealVNC client (formerly payware and now >>free,) Zarchiver (since I use 7-Zip as my archiver under Windows and >>p7z under Linux, this is a no brainer), Hacker's keyboard (thanks >>again!), and VimTouch, a version of the Vim editor modified for touch >>screens. As it happens, there's even a port of Gnu Emacs for Android, >>though getting it set up looks non-trivial. > > What do you use at the other end for RealVNC? Nothing, yet. The first target when I get to that point will be TightVNC on my home network. At a former employer, I had TightVNC installed on the Solaris servers I administered. It meant I could access a GUI desktop on the server without running an X client on my desktop. The TightVNC server process on the server handled things. I didn't use it much, since most of what I did was at the command line via a PuTTY telnet or SSH session, and I seldom needed to use a GUI. That employer used RealVNC for remote desktop stuff, and I'd first encountered VNC previously in the AT&T UK Research Labs flavor, before settling on TightVNC for my own use. (I even had a VNC client running on my Zodiac that could successfully access my home server.) The critical part is the VNC protocol. If it's properly implemented, you shouldn't have to care which VNC flavor is on the other end. > I'll try VimTouch, though I never used vim, once I was shown 'mc', that's what I used mainly (but all I need I just to edit some config stuff) Vim Touch is there to see what they did. I learned vi under AT&T Unix System V, and stayed fluent for the same reason I learned WordStar back in the MS-DOS days: it was likely to be on whatever machine I had to deal with when other things might not be. Vim is technically "Vi Improved", based on vi's design but with a *lot* of stuff added. I have Vim under Windows, but seldom use it. Under Linux, it might as well *be* vi for the use I make, as I essentially don't use any of the advanced features. My usage is like yours: edit the odd config file or shell script. The requirements are fast to invoke and powerful enough to do what I need to do. There are far more powerful editors than vi (like Vim if you use all the stuff it includes), but I don't need what they do. To my bemusement, there's even an Android port of Gnu Emacs. What I have installed for further investigation now are the 920 editor and the Jota editor. Both are open source products. The other thing you might want to look at under Linux is Gnu nano. Nano is based on the design of the pico editor shipped with the Elm mail system, but pico's license is incompatible with the GPL, so the Gnu version is a reverse engineered clone with a few more features. It's a minimal editor with all editing commands displayed on screen. If you need syntax highlighting, fancy undo, scripting or the like, nano is not for you. If you need a small editor that invokes fast to do some simple edits on a file, it might be just the thing. > V ______ Dennis