View Single Post
Old 09-20-2013, 08:44 AM   #37
jtt
Connoisseur
jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.jtt composes epic poetry in binary.
 
Posts: 97
Karma: 90350
Join Date: Aug 2013
Location: Berlin, Germany
Device: PB 622, PB 623
Quote:
Originally Posted by rkomar View Post
vi is my preferred editor, but as you say, with the necessity for the escape and control keys, it was never going to be easy to use with a software keyboard, even if the terminal behaviour is solved. A line editor seems a better choice, which is more or less what the Pi editor is.
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
jtt is offline   Reply With Quote