about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2023-01-221-1/+1
|\
| * remove a conditionKartik K. Agaram2023-01-221-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-01-207-1367/+1153
|\|
| * clean up a printKartik K. Agaram2023-01-201-1/+0
| |
| * show another detail on test failureKartik K. Agaram2023-01-201-1/+1
| |
| * deduce test names on failuresKartik K. Agaram2023-01-207-1375/+1159
| |
| * link to default love.run for comparisonKartik K. Agaram2023-01-201-2/+2
| |
* | fix broken linkKartik K. Agaram2023-01-201-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-01-191-1/+0
|\|
| * no, turn vsync back onKartik K. Agaram2023-01-191-1/+0
| | | | | | | | | | I notice my laptop's fan starts coming on when running many of my apps. An empty app takes 10% CPU where it used to take just 1-2%.
* | best prose across forksKartik K. Agaram2023-01-181-1/+2
| |
* | cleanerKartik K. Agaram2023-01-181-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-01-161-1/+1
|\|
| * correct comment; vsync is hard to reason aboutKartik K. Agaram2023-01-161-1/+1
| |
* | Merge lines.loveKartik K. Agaram2023-01-163-10/+6
|\|
| * disable vsyncKartik K. Agaram2023-01-161-0/+1
| | | | | | | | Thanks Nils Berg for the suggestion!
| * hoist out some common settingsKartik K. Agaram2023-01-163-10/+5
| |
* | Merge lines.loveKartik K. Agaram2023-01-133-14/+28
|\|
| * reduce use of rfindKartik K. Agaram2023-01-133-14/+28
| |
* | Merge lines.loveKartik K. Agaram2023-01-061-2/+2
|\|
| * bugfixKartik K. Agaram2023-01-061-2/+2
| | | | | | | | | | lines.love was broken since Dec 23 X-( Didn't get caught because all my tests start at edit, not at main or run. I need 'integration' tests.
* | Merge lines.loveKartik K. Agaram2023-01-012-3/+3
|\|
| * typoKartik K. Agaram2023-01-012-3/+3
| |
* | Merge lines.loveKartik K. Agaram2023-01-011-1/+1
|\|
| * fix stale commentKartik K. Agaram2023-01-011-1/+1
| |
* | Merge lines.loveKartik K. Agaram2022-12-242-2/+2
|\|
| * bugfixKartik K. Agaram2022-12-242-2/+2
| | | | | | | | | | | | | | | | | | | | | | Scenario: make some edits, select some text, make some more edits. Press ctrl-z. Before this commit, undo would stop at the point of selection and previous edits would become unreachable. After this commit, both ctrl-z and ctrl-y seem able to span the point of selection.
| * typoKartik K. Agaram2022-12-242-2/+2
| |
* | Merge lines.loveKartik K. Agaram2022-12-233-7/+7
|\|
| * fix some arg namesKartik K. Agaram2022-12-231-3/+3
| |
| * another missed renameKartik K. Agaram2022-12-231-2/+2
| |
| * overzealous search-and-replaceKartik K. Agaram2022-12-232-2/+2
| |
* | Merge lines.loveKartik K. Agaram2022-12-2316-311/+280
|\|
| * consistent names in a few more placesKartik K. Agaram2022-12-236-16/+16
| |
| * make love event names consistentKartik K. Agaram2022-12-2315-163/+163
| | | | | | | | | | I want the words to be easy to read, and to use a consistent tense. update and focus seem more timeless; let's make everything like those.
| * require editor margins to be intsKartik K. Agaram2022-12-232-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | Not directly relevant here, but forks of this project that permit zooming can run into weird glitches if margins are not a whole number of pixels. I'd always assumed a type system that divided ints into floats was strictly superior, but now I have experienced a situation where requiring ints isn't just a compromise for the underlying CPU implementation. Particularly since Lua's print() silently hides really tiny fractions.
| * streamline one more test nameKartik K. Agaram2022-12-132-28/+28
| |
| * repeat changes on source editorKartik K. Agaram2022-12-131-53/+36
| |
| * more streamlined test namesKartik K. Agaram2022-12-131-29/+29
| | | | | | | | https://lobste.rs/messages/e1rimy
| * remove a duplicate testKartik K. Agaram2022-12-131-27/+10
| |
* | Merge lines.loveKartik K. Agaram2022-12-121-2/+5
|\|
| * repeat bugfix on source editor X-(Kartik K. Agaram2022-12-121-2/+5
| |
* | Merge lines.loveKartik K. Agaram2022-12-121-18/+18
|\|
| * switch one call back to keychord_pressedKartik K. Agaram2022-12-121-1/+1
| | | | | | | | I don't understand why, but we need to fix production.
| * switch a bunch of tests to textinput eventsKartik K. Agaram2022-12-121-18/+18
| | | | | | | | | | textinput is strictly more realistic than keychord_pressed, which doesn't cause any textinput events. Use it wherever possible.
| * bugfix in changing shape mid-strokeKartik K. Agaram2022-12-122-3/+6
| |
* | Merge lines.loveKartik K. Agaram2022-12-121-1/+6
|\|
| * repeat bugfix on source editorKartik K. Agaram2022-12-121-1/+6
| |
* | Merge lines.loveKartik K. Agaram2022-12-121-1/+6
|\|
| * bugfix: naming points in drawingsKartik K. Agaram2022-12-121-1/+6
| | | | | | | | | | | | | | | | | | We had a regression since commit 60e1023f0 on Nov 27. Turns out we do need the ancient hack after all. But no, we won't go back to the hack. It's a simple problem to fix right. And while we're at it, we'll fix the test harness to be more realistic so it would have caught this problem.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-09-10 15:10:54 +0000