> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Sunday, October 18, 2020 4:45 AM
>
> How clear is the desired scope of SRFI 205 at this point?
>
> John added a ton of stty settings on top of the latest draft.

And they haven't been examined, but they're from scsh and therefore
should fit in the remit of "POSIX Terminal Fundamentals".

> I would be interested in something at the level of the minsi library I
> wrote: "just give me a raw terminal and let me read and write ANSI
> sequences". If SRFI 205 wants to be more fine-grained, that is fine.

Up to now it wants to be lower level.  And provides with-raw-mode to
give you that raw terminal as safely as possible, i.e. less likely for
a program exit to leave the terminal in raw mode.

ANSI sequences strike me at first glance as not being in its remit.
Putting on my implementor hat, adding them should not significantly
increase the workload after the first sample implementation, it would
all be standard Scheme code, right?

I'd like to know where John etc. think this level of ANSI terminal
stuff should go.

> If there's wider interest in the minsi-level stuff, we can make another
> SRFI out of it (with SRFI 205 as one possible implementation strategy)
> and make sure the API plays nicely with SRFI 205, avoiding redundancy
> and inconsistency as far as possible. I can also just keep it as a
> library in snow-fort. Just wrote a Chibi wrapper for it.

A separate SRFI would be cleaner, I think, and could be a building
block for more serious terminal user interfaces:

> On top of this stuff, we should draft the character cell SRFI, with ANSI
> codes, Windows Console, and others as possible backends....

- Harold