about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* jsregex: remove use of newSeqUninitializedbptato2025-04-301-5/+4
| | | | It's fine to zero-fill this.
* myaddr: backport & switch to newSeqUninitbptato2025-04-309-19/+24
|
* config: misc optimizationbptato2025-04-291-4/+4
|
* config: fix arrays not being cleared on reassignmentbptato2025-04-291-0/+1
|
* Update docsbptato2025-04-281-2/+2
|
* term: support vt52bptato2025-04-281-6/+13
|
* term: reduce Termdesc sizebptato2025-04-271-43/+42
| | | | now it fits into 1 byte
* Fix typobptato2025-04-251-2/+2
|
* Update docsbptato2025-04-253-2/+62
|
* term: misc fixes, support rxvtbptato2025-04-251-42/+49
|
* term: misc fixes, support adm3abptato2025-04-241-55/+93
|
* Makefile: remove redundant assignmentbptato2025-04-241-5/+0
| | | | whoops
* http: cast away GCC complaints properlybptato2025-04-241-4/+7
|
* http: re-add brotli supportbptato2025-04-236-8/+109
| | | | | Unfortunately this is unavoidable, as some servers still seem to return brotli despite our Accept-Encoding header not including it.
* makefile: fix nanosvg dependencybptato2025-04-231-1/+1
|
* Add static linking optionbptato2025-04-232-2/+42
|
* term: replace termcap with a built-in terminal databasebptato2025-04-236-194/+166
| | | | | | | | | | | | | I considered using terminfo, but it works *worse* on several terminals I've tried than whatever this is. So out with ncurses, I say. In this new scheme, if the terminal is unrecognized, it is assumed to be XTerm-compatible. This does mean that an unrecognized terminal that doesn't do XTGETTCAP or COLORTERM will not get true colors. Another drawback is that non-VT-compatible terminals now have zero chance of working. This is unfortunate, but realistically they probably didn't work until now either.
* layout: simplify resolveBoundsbptato2025-04-231-31/+19
| | | | | Not entirely sure what the px check for the mi[dtHorizontal].send assingment was for; tests still pass after removing it.
* cssparser: optimize CSSToken sizebptato2025-04-181-2/+2
| | | | 4 -> 3 words
* selectorparser: check type flag of hash tokensbptato2025-04-184-10/+18
|
* toml: fix underscores in integer literalsbptato2025-04-171-9/+8
| | | | while at it, prefer seek to discarding consume
* config: remove bindPagerKey, bindLineKeybptato2025-04-171-6/+0
| | | | undocumented and likely unused.
* loader: remove obsolete commentbptato2025-04-171-1/+0
|
* pager: remove obsolete acceptBuffersbptato2025-04-171-28/+14
| | | | Hopefully this didn't break anything...
* loader: use pipes in network streamsbptato2025-04-172-13/+11
| | | | | | | | | | | Turns out we don't actually have a reliable mechanism to detect broken streams - if a pipe is broken, well, it's broken, but that's about all we know. It seems UNIX sockets didn't trigger the code path, but pipes do now, and it was causing issues (reporting some correctly ended streams as broken). This is not fixable with the current protocol, so for now, I've just made onError do the same as onRead at EOF.
* main: ensure that we own tmpdirbptato2025-04-171-9/+14
| | | | | | | | Otherwise a malicious user on the same machine could get access to the directory. (This isn't problematic in theory, since such users still wouldn't have access to the temp files. Still, better safe than sorry.)
* pager: remove unused fieldbptato2025-04-171-7/+6
|
* libfetch-http: update commentbptato2025-04-171-4/+0
| | | | yeah
* loaderiface: return PosixStream for startRequestbptato2025-04-154-11/+10
|
* toml: remove broken special case, update docsbptato2025-04-155-37/+20
| | | | | | Turns out the cure was worse than the disease. Let's just make it a backwards incompatible change, so that at least the error message is no longer nonsensical.
* pager: pin downloads panelbptato2025-04-152-2/+12
| | | | and make it autorefresh so the UX is halfway sane
* loader: fix redirectToFile looping logicbptato2025-04-151-13/+14
|
* loader: remove target pid from addCacheFilebptato2025-04-154-19/+15
| | | | I wonder if it would be better to just resume in the buffer.
* Update Makefilebptato2025-04-151-1/+1
|
* Update readmebptato2025-04-141-1/+1
|
* term: set VMIN, VTIME for good measurebptato2025-04-141-0/+2
| | | | I don't know if this actually helps anywhere, but it can't hurt
* lcgi_ssl, sftp: add cflags from pkg-configbptato2025-04-142-1/+5
|
* dom: add textarea value setter, defaultValuebptato2025-04-142-2/+26
|
* render: fix positioning of absolutes with negative z-indexbptato2025-04-143-2/+10
|
* http: replace with newhttpbptato2025-04-1410-1056/+1059
| | | | | I think it works well enough at this point. If it doesn't, somebody will complain :)
* http: merge in curl.nimbptato2025-04-143-457/+457
|
* pager, formdata: DynStream -> PosixStreambptato2025-04-142-3/+3
|
* nc: various fixesbptato2025-04-131-14/+9
|
* loader, pager: fix login with username onlybptato2025-04-132-3/+8
| | | | | | It's a bit tricky, because "username only" means "try with the username only" only if no password has been recorded for the username on the origin.
* loader: remove referrer field from Requestbptato2025-04-134-14/+23
| | | | It's OK to store it in headers.
* sftp: verify known_hostsbptato2025-04-131-4/+140
| | | | Long overdue... the API is extremely painful to work with.
* pager: reduce passFd callsbptato2025-04-131-26/+24
| | | | addPipe is unprivileged and preferable in general.
* mailcap: interpret xhtml as htmlbptato2025-04-131-0/+1
| | | | it's horrible, but better than nothing.
* newhttp: drop unbrotlibptato2025-04-132-94/+1
| | | | Actually, it may be fine to leave it out for now.
* quickjs: remove pointless overloadbptato2025-04-111-4/+0
|