Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | js: proper distinction between Opt/Option | bptato | 2024-03-24 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | until now, this had very strange (and inconsistent) semantics: * err() was used for exception propagation, but also as a null value * Option accepted undefined as a none value, but not null * Opt and Option were used interchangeably (and mostly randomly) Now, Result is always used for error reporting, and err(nil) means JS_EXCEPTION. (Opt is a special case of Result where we don't care about the error type, and is not used in JS.) Option on the other hand means "nullable variation of normally non-nullable type", and translates to JS_NULL. In JS we mainly use it for turning strings nullable. | ||||
* | buffer: form fixes & improvements | bptato | 2024-03-24 | 1 | -6/+6 |
| | | | | | | | * fall back to text for unimplemented input types * add custom prompt to all text-like input types * show min/max for range * fix accidental override of repaint | ||||
* | catom: at -> sat | bptato | 2024-03-21 | 1 | -5/+5 |
| | | | | just for consistency | ||||
* | Move around some modules | bptato | 2024-03-14 | 1 | -0/+177 |
* extern -> gone, runproc absorbed by pager, others moved into io/ * display -> local/ (where else would we display?) * xhr -> html/ * move out WindowAttributes from term, so we don't depend on local from server |