about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* mouse wheel supportKartik K. Agaram2023-03-236-12/+84
|
* mention a new toolKartik K. Agaram2023-03-211-0/+2
|
* give a test a unique nameKartik K. Agaram2023-03-192-6/+6
|
* get typed in keystrokes to show on screen on iPadKartik K. Agaram2023-03-182-0/+21
| | | | Many thanks to Myte for helping test this!
* extract a functionKartik K. Agaram2023-03-181-10/+14
|
* consistently use App names for methods everywhereKartik K. Agaram2023-03-182-9/+9
|
* move default file locationKartik K. Agaram2023-03-181-1/+1
| | | | | | | | This works better on mobile platforms while seeming about as useful anywhere else. I've verified that anyone who already edited a file will continue to use its path from settings.
* remove a stale issueKartik K. Agaram2023-03-171-2/+0
|
* more bugfixKartik K. Agaram2023-03-173-6/+4
| | | | Don't crash on showing the log browser.
* bugfixKartik K. Agaram2023-03-174-18/+72
| | | | Thanks Mikoláš Štrajt.
* get rid of all bifold textKartik K. Agaram2023-03-174-874/+120
| | | | | | | | | | | | | | | It's just uneconomic to maintain given how little I've used it. I have a bug right now and no time to port the bugfix to all the complexities of the B side. I briefly considered tossing out the entire source editor. But I _have_ been using it to browse logs across sessions. The live editor doesn't quite cover all my use cases just yet. We now have duplication in the source editor only for: * syntax highlighting * hyperlinking [[WikiWords]] * ability to hide cursor (when showing file browser or Focus is in log browser)
* bring a few things in sync between run and sourceKartik K. Agaram2023-03-173-8/+29
|
* bugfix: disallow font size of 0Kartik K. Agaram2023-03-172-4/+8
| | | | Thanks Mikoláš Štrajt.
* state validation in source editor as wellKartik K. Agaram2023-03-172-2/+25
|
* more robust state validationKartik K. Agaram2023-03-172-7/+26
|
* bugfixKartik K. Agaram2023-02-092-0/+2
| | | | | | | | | | | scenario: press ctrl+f, type in a string hit down arrow if needed until the screen scrolls press enter click with the mouse somewhere Before this commit the app would crash because cursor was above screen top.
* document the version of LÖVE I've been usingKartik K. Agaram2023-02-071-0/+3
|
* bugfix: up arrow when line above is a drawingKartik K. Agaram2023-01-314-3/+103
| | | | This bug was introduced in commit 528c64d690 on 2022-09-05 :/
* create a place for graphical log handlersKartik K. Agaram2023-01-302-1/+3
| | | | | | | | | | | | | Currently only used in pong.love, but let's keep the bad merge that had it broken since September from occurring again. To do that we'll be consistent across forks on where globals are initialized. I haven't appreciated the implications of main.lua for load order. log.lua comes first just because it's shared by both the main app and its 'source' editing environment. And it just so happens that source.lua was loading after log.lua resulting in the pong.love breakage. Now let's lean into that and enshrine that one should initialize log_render in log.lua.
* wait a little to flush disk before quittingKartik K. Agaram2023-01-281-0/+2
| | | | | | | I've been noticing in pensieve.love in particular that once a month or so I lose data if I quit immediately after typing in something. Nothing major, just the odd link between notes which leaves things in an inconsistent state. Let's see if this helps.
* include instructions to install LÖVEKartik K. Agaram2023-01-241-1/+5
|
* demote codeberg.org in the list of mirrorsKartik K. Agaram2023-01-231-2/+2
| | | | It's been slow to push to lately, so I'm going to update it less frequently.
* remove a conditionKartik K. Agaram2023-01-221-1/+1
|
* 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
|
* 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%.
* correct comment; vsync is hard to reason aboutKartik K. Agaram2023-01-161-1/+1
|
* 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
|
* reduce use of rfindKartik K. Agaram2023-01-133-14/+28
|
* 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.
* typoKartik K. Agaram2023-01-012-3/+3
|
* fix stale commentKartik K. Agaram2023-01-011-1/+1
|
* 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
|
* 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
|
* 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
|
* repeat bugfix on source editor X-(Kartik K. Agaram2022-12-121-2/+5
|
* 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.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-14 09:03:10 +0000