| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will let me swap in a fake in tests.
Still hacky, though. I'm sure I'm not managing the parameter right in
the chessboard app.
And then there's the question of whether it should also appear as an
output operand.
But it's a start. And using nil to mean 'real' is a reasonable
convention.
If I ever need to handle multiple screens perhaps we'll have to switch
to 1:literal/terminal and 2:literal/terminal, etc. But those are equally
easy to guard on.
|
|
|
|
| |
Is it even worth having my generic function prepend idea?
|
| |
|
| |
|
| |
|
|
|
|
| |
Tests force me to extract functions 'read-rank' and 'read-file'.
|
| |
|
|
|
|
|
|
| |
This is the sort of thing we want to make super easy.
But there's a bug at the moment: chessboard prints junk input at second move.
|
|
|
|
| |
Hacky, but it's a start.
|
|
Other options considered for 'retro':
'teletype': perhaps most accurate, but arcane
'chat': captures that you have to hit 'enter', but not the rendering
'wrap': captures the auto-wrap when printing text but not that you have
to hit 'enter' when typing
'text': useful as a synonym of 'chat' while conveying more information
in other meanings, but too generic, nobody will get it
Why do the input and output options have to be entangled like this?
|