about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge lines.loveKartik K. Agaram2023-09-103-17/+3
|\|
| * Revert "deemphasize the source editor"Kartik K. Agaram2023-09-103-17/+3
| | | | | | | | | | | | | | Now that we have decent error handling, I think we can encourage people to press ctrl+e again. This reverts commit 4b43e9e85d985bcedd105fa9693ae751e5b6d0b6.
* | Merge lines.loveKartik K. Agaram2023-09-091-11/+46
|\|
| * yet another bugfix X-(Kartik K. Agaram2023-09-091-2/+2
| | | | | | | | This time it really does work with pensieve.love
| * two bugfixesKartik K. Agaram2023-09-091-2/+3
| | | | | | | | | | Annoying dangers of testing in one fork and committing upstream (where it isn't used yet).
| * new primitives for reading/writing filesKartik K. Agaram2023-09-091-0/+34
| | | | | | | | | | | | | | | | These are like versions in nativefs, but only support absolute paths. I want to be thoughtful about the precise location at each call-site. It's a little ugly that app.lua now has a dependency on file.lua. Or source_file.lua for the source editor.
| * reorderKartik K. Agaram2023-09-091-11/+11
| |
* | Merge lines.loveKartik K. Agaram2023-09-081-0/+13
|\|
| * a few more testable file-system operationsKartik K. Agaram2023-09-081-0/+13
| |
* | Merge lines.loveKartik K. Agaram2023-09-042-0/+9
|\|
| * show any error after switching to source editorKartik K. Agaram2023-09-042-0/+9
| | | | | | | | | | | | Error_message is a special global. It's set when the app (Current_app = 'run') encounters an error and switches to the source editor, and cleared when switching from source editor back to the app.
* | Merge lines.loveKartik K. Agaram2023-09-041-5/+36
|\|
| * switch to source editor on errorKartik K. Agaram2023-09-041-3/+18
| | | | | | | | | | | | If we're already in source editor we'll quit as before. It's ugly that app.lua now knows about run.lua. But it's a start.
| * stop using keyboard.isDownKartik K. Agaram2023-09-041-2/+18
| | | | | | | | It doesn't work on Android, and it's not much work to avoid.
* | Merge lines.loveKartik K. Agaram2023-08-312-2/+2
|\|
| * yet another set of bugfixesKartik K. Agaram2023-08-302-2/+2
| | | | | | | | | | The key API change I'd underestimated: opening a file used to return nil on failure, and now returns false.
* | Merge lines.loveKartik K. Agaram2023-08-306-73/+562
|\|
| * bugfix in source editorKartik K. Agaram2023-08-301-2/+8
| | | | | | | | We now need to explicitly select the directory we want to read from.
| * cleaner API for file-system accessKartik K. Agaram2023-08-304-52/+535
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Thanks to physfs and nativefs.lua nativefs still introduces some inconsistencies with love.filesystem with relative paths: * love.fs.read: reads from save dir if it exists, falls back to source dir if not * nativefs.read: reads from save dir if it exists, falls back to source dir if not ✓ * love.fs.write: always writes to save dir * nativefs.write: always writes to source dir (since no restrictions) * love.fs.newFile followed by file:open('r'): reads from save dir if it exists, source dir if not * nativefs.newFile followed by file:open('r'): always reads from working dir * love.fs.newFile followed by file:open('w'): always writes to save dir * nativefs.newFile followed by file:open('w'): always writes to working dir So avoid using relative paths with App primitives.
| * make a few names consistent with snake_caseKartik K. Agaram2023-08-304-20/+20
| |
* | Merge lines.loveKartik K. Agaram2023-08-263-177/+152
|\|
| * reorganize app.lua and its commentsKartik K. Agaram2023-08-261-166/+142
| | | | | | | | | | | | I was so sure my comments were clear when I wrote this a year ago. They were shit. So, most probably, is the current iteration. Feedback appreciated.
| * correct various names in this and other pre-freewheeling forksKartik K. Agaram2023-08-261-7/+7
| |
| * fix method name in documentationKartik K. Agaram2023-08-261-1/+1
| |
| * tweak wording in test listKartik K. Agaram2023-08-071-3/+2
| |
* | Merge lines.loveKartik K. Agaram2023-07-312-32/+47
|\|
| * reorganize some commentsKartik K. Agaram2023-07-311-2/+2
| | | | | | | | | | This keeps things consistent with other forks (links, lines-and-links) that are "conceptually upstream" of the source editor.
| * bugfix: search highlight straddling screen linesKartik K. Agaram2023-07-312-14/+16
| |
| * remove a duplicate print to screenKartik K. Agaram2023-07-312-17/+14
| | | | | | | | In addition to being more efficient, this will simplify the next bugfix.
| * extract a variableKartik K. Agaram2023-07-312-2/+4
| |
| * bugfix: highlight search patterns on the right lineKartik K. Agaram2023-07-312-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | scenario: * position a wrapped line on screen * search for the word immediately after the point of wrapping Before this commit the word would be highlighted twice: - at the end of the first screen line - at the start of the second screen line Now it shows up at the right place.
| * hoist and duplicate a conditionalKartik K. Agaram2023-07-312-6/+10
| | | | | | | | | | | | I'm duplicating the bounds check when drawing cursor and search highlight because they're separate concerns and require subtly different logic.
| * improve a commentKartik K. Agaram2023-07-312-2/+2
| |
* | Merge lines.loveKartik K. Agaram2023-07-112-4/+4
|\|
| * drop an unused argKartik K. Agaram2023-07-112-4/+4
| |
* | Merge lines.loveKartik K. Agaram2023-07-103-117/+54
|\|
| * standardize between run and source some moreKartik K. Agaram2023-07-102-7/+3
| | | | | | | | | | We shouldn't be thinking about saving settings when we're initializing window geometry.
| * simplify saving settingsKartik K. Agaram2023-07-102-8/+2
| | | | | | | | We don't ever call one app's settings while Current_app is the other.
| * bugfix: Windows pushing title bar off screenKartik K. Agaram2023-07-103-92/+32
| | | | | | | | | | | | | | | | | | | | | | I'm learning the hard way that resizing the window is a big deal. Only do this when someone explicitly requests it, otherwise follow LÖVE's defaults. Therefore we're also going to stop trying to be smart when showing the log browser. Leave window resizing to manual operations. Now initialization looks a lot more similar for the run and source apps.
| * delete flags that have never been exercisedKartik K. Agaram2023-07-102-8/+0
| | | | | | | | Initialization is getting complex, and I'm finding bugs.
| * bugfix: preserve window positionKartik K. Agaram2023-07-101-1/+11
| | | | | | | | | | | | | | | | I just noticed we hadn't got this bugfix for Linux on the main app. How had we not noticed this issue before? Answer: lines.love windows tend to be tall and skinny, and resize must keep the window entirely within the screen. So the window was staying in place just because it happened to be running up against the bottom.
| * bugfix: preserve window positionKartik K. Agaram2023-07-101-2/+7
| |
* | Merge lines.loveKartik K. Agaram2023-07-071-0/+37
|\|
| * support for num padKartik K. Agaram2023-07-071-0/+37
| | | | | | | | It'll only work after LÖVE v12 comes out.
* | Merge lines.loveKartik K. Agaram2023-06-251-0/+1
|\|
| * experiment: convert to PijulKartik K. Agaram2023-06-251-0/+1
| | | | | | | | https://pijul.org
* | Merge lines.loveKartik K. Agaram2023-06-171-2/+3
|\|
| * stop highlighting strings in codeKartik K. Agaram2023-06-171-2/+3
| | | | | | | | | | It works right so rarely that it's a net negative. I'll bring it back if I ever start tokenizing on non-whitespace.
* | Merge lines.loveKartik K. Agaram2023-06-081-1/+3
|\|
| * reconcile manual tests with some downstream forksKartik K. Agaram2023-06-081-1/+3
| |