Good to hear about terminal? And shelling out is a good and necessary use case for with-cooked, and won't it be safe just as soon as you start running the command? We'll just have to add warnings to SRFI nnn POSIX Terminal Fundamentals about the dangers.
That SRFI is also an opportunity to add baud rate changing to the API, I want that for embedded programming, which still uses serial lines a whole lot (usually through a USB adapter). As I recall it won't be much effort once you create all the termios low level infrastructure, and have example code for the higher levels to cut and paste.
Are we essentially all but done with the HTML document? I suspect the final call should have my Chibi Scheme implementation conforming to it as much as I'm going (that includes all the POSIX interfacing, but not some of the pure Scheme built on top of it). I'm ready to make those final changes, just don't want to have to do them again unless there's changes prompted from outside our circle due to the final call.
- Harold
----- Original message -----
Date: Tuesday, June 23, 2020 11:01 AM
Okay, terminal? is now the only procedure in 3.12.
with-cooked was meant to be used when we need to exit temporarily from a TUI into a CLI. An example would be the ! command in vi, which gets a command line and runs the command in a CLI, returning to the TUI when the command is finished.
Date: Monday, June 22, 2020 2:23 PM
That's exactly what I'm advocating, reverting to having with-raw-mode and with-rare-mode as SRFI ecosystem exposed fundamental building blocks for a TUI, your's or anyone else's. Given how useful without-echo is, I'm inclined to keep all of 3.11 Terminal Device Control in, but they're a lot of work, it would be OK to move all of it to another SRFI, my strong position is that all the with- and without- modes stay in one block of work for implementors.
Okay, I'm flushing the whole of 3.12 (not 3.11) for an eventual new SRFI.
It would still be handy to have the low effort to implement terminal? for the low effort Terminal User Interface of printing a status line, and regularly overwriting it with a carriage return and a new status line. terminal? tells you if standard out or error is being piped to something, in which case you want to automatically skip that.
I was going to say I'm neutral on the new with-cooked-mode, but it just occurred to me that it's dangerous. If while in it the user ^C's out of the running Scheme, he should end up with a sane, cooked mode terminal, but that'll blast him out of the nested with-cooked and with-raw/rare-mode, and thus the whole TUI. I can't think of any reason a developer using a TUI to create an application would want to allow that.
I don't understand this, but it's moot now.
TL;DR: with-cooked-mode is dangerous and not useful?? But moving all of them to another SRFI works, implementing any single one of the with- or without- procedures is a lot of work.
Anyway, I think I'm done dinking with these two SRFIs, unless you have specific remaining difficulties or objections. I'll pull together the quasi-portable 198 implementation, as the hard parts are already done.
Only the above WRT to terminal?
- Harold