On Sunday, 10 April 2016 at 02:59:41 UTC, Adam D. Ruppe wrote:
On Sunday, 10 April 2016 at 00:47:28 UTC, Puming wrote:
3. when hiting 'vim a.file' on the command, things go messy.
Have you got these interactive commands work in dexpect?
It is surely capturing exactly what vim sends to a terminal,
which is primarily a series of control sequences to draw the
screen, move the cursor, color it, etc.
Yes, I guess if I fully forward every output/input, it'll work.
You might want to watch for those and just forward them
directly to the user terminal... but this is getting kinda
wild....
Well, I'm not sure whether I can handle the complexity here. I
don't even quite understand terminal io/sequence characters yet.
Come back to this later when I get my little repl running.
1. Fully proxy for a bash shell.
2. Result data are separated for each command. So I can easily
search for hitorical sent commands or results.
What you probably want to do is just send one command at a time
to the bash process and handle the rest yourself.
Or just forget bash and write your own shell.
An indepedent shell would be GREAT! I hope someday we get a REPL
in D, and it is also an independent shell, just like FishShell,
but implemented in D, and scripts are also in D.
