about summary refs log tree commit diff stats
path: root/chessboard-cursor.mu
Commit message (Collapse)AuthorAgeFilesLines
* 562Kartik K. Agaram2015-01-141-1/+0
|
* 560Kartik K. Agaram2015-01-131-3/+0
|
* 554 - tedious to have to check for routine errors on every forkKartik K. Agaram2015-01-131-0/+1
|
* 551Kartik K. Agaram2015-01-131-55/+61
| | | | Tests force me to extract functions 'read-rank' and 'read-file'.
* 550 - another bugfix, another pending testKartik K. Agaram2015-01-131-0/+3
|
* 549 - suppress prints in read-moveKartik K. Agaram2015-01-131-5/+21
| | | | | | 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.
* 546 - chessboard now reads from stdinKartik K. Agaram2015-01-121-5/+13
| | | | Hacky, but it's a start.
* 544 - text modes now called 'retro' & 'cursor'Kartik K. Agaram2015-01-121-0/+223
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?