Quote:
Originally Posted by jtt
I always thought that you don't need the <CTRL> key with vi, do you? And the idea is to actually run vi as a child process, conntected via a pseudoterminal (I fear pipes won't do due to the line-buffering), and just interpret the VT102 escape sequences vi seems to be sending for correct display, while a newly written keyboard occupies the bottom of the screen, which sends characters as they're typed in (the keyboard from libinkvew is useless here) and has an <ESC> key. Of course, that's just an idea, don't know if this can be made to work. At least I will learn a bit more about vi should I attempt at write something like that;-)
Best regards, Jens
|
I looked into getting vi running in a curses-based environment a few years ago when I first got my PocketBook device, so it's a bit vague in my memory now. You're probably right about the CTRL keys not being required (except for CTRL-V for inputting hex). Thinking back, I think it was the fact that the Enter key was missing from the software keyboard that put me off pursuing this. I had already made my own keyboard layout with more special characters, but I couldn't figure out how to add the Enter key to it. Since you can't use a bluetooth keyboard either, I just gave up on running vi from the device's interface.
I got WiFi working and used sshd and utelnetd for shell access after that, and never looked back. If you think the software keyboard sucks on your Touch device, you should see what it's like on the button-only devices like my 902 (three button presses on average per character, and much more for the special ones).