On 4 August 2010 05:13, Wolf Tivy <wti...@my.bcit.ca> wrote: > > Sounds like vi. > except with a clean command set and less legacy baggage.
And structural regular expressions, and less modality, and sam networking. It sounds like vi in the sense that yes, it edits text. Regarding the command input, imo there should just be a bar at the bottom which displays information such as the filename and "dot", which highlights in some way (colour inversion?) and accepts input when you hit a certain shortcut. This means there are only two modes: cmd, and not-cmd. And there could also be a cmd window which contains all your previous input - the bar would only be for convenience. On 3 August 2010 19:10, Wolf Tivy <wti...@my.bcit.ca> wrote: > How different is the protocol from sam -d? I will have to do > some reading. They aren't even related. The sam protocol is completely binary, for one thing. I dug up some code I wrote a while back for parsing the sam protocol, and some rudimentary rasp algorithms (that is, requesting and recieving data to fill holes in the term's file cache). But it is, I stress, extremely crude. It does go as far as to establish the connection and display the contents of a "hello world" file, but it also segfaults if the file is too big. Even so, it seems cleaner than the standard samterm's mesg.c. If you want to have a look I can upload the code, but don't say I didn't warn you. cls
