3 ms·
This looks quite interesting. I wonder, though, if it might be a good idea to cut back the scope of the project (at least initially). Replacing the ANSI escap
by mikekchar 11y ago
This looks quite interesting. I wonder, though, if it might be a good idea to cut back the scope of the project (at least initially). Replacing the ANSI escape sequences with something sane is a hard enough problem, I think, even if you were just going for feature parity. Fixing the colour palette problems would be amazing.
- tatterdemalion 11y agoIndeed! The first step of this project was implementing an ANSI terminal, but with an eye toward abstracting ANSI commands into more fundamental building blocks, so that the analogous set of notty commands are already more powerful than ANSI commands (in the sense that actions that would require multiple ANSI commands can be performed in 1 notty command). This is done, excepting for bugs (there are many). I narrowed down the immediate term goals for radical new features to three: images, a minimal internal line discipline, and dividing the screen into multiple grids. I chose these because the first is a clear differentiator and the other two are very fundamental. Simultaneously, we're working on getting a reasonable terminal off the ground for dogfooding. Once we have that, the next step is writing a curses-like library that takes advantage of notty's features, as well as a shim to run programs written against that library in non-notty terminals. Then we'll have a solid base for adding more features. As of right now, it is already an ANSI terminal which accepts a cleaner escape sequence and supports 24-bit color, barring bugs.