I'm a bit leery of going down this road: - If there's a bug in how I render logs graphically that could be extremely misleading. Perhaps this suggests that the code to log things should be significantly simpler than the code that might be debugged. If writing the debug helper requires all my smarts I'm not smart enough to debug using the helper, etc. Given this idea, the fact that I'm copying production code into the logging helper is concerning. - There's a question of what code it's ok for logging helpers to depend on. This is an issue shared with tests. I often implicitly (and without meaning to) assume the presence of some well-tested helpers when writing tests. If those helpers ever break I can get into a rabbit hole of debugging. This problem might be even more insidious with logging helpers that will give me no indication when they break. Still and all, it's cool to see menus in my logs. Let's see if it's useful. |
||
|---|---|---|
| LICENSE.txt | ||
| Manual_tests.md | ||
| MemoryReferenceInfo.lua.0 | ||
| MemoryReferenceInfo.lua.unused | ||
| README.md | ||
| app.lua | ||
| button.lua | ||
| colorize.lua | ||
| commands.lua | ||
| drawing.lua | ||
| drawing_tests.lua | ||
| edit.lua | ||
| file.lua | ||
| geom.lua | ||
| help.lua | ||
| icons.lua | ||
| json.lua | ||
| keychord.lua | ||
| log.lua | ||
| log_browser.lua | ||
| main.lua | ||
| run.lua | ||
| run_tests.lua | ||
| search.lua | ||
| select.lua | ||
| source.lua | ||
| source_edit.lua | ||
| source_file.lua | ||
| source_select.lua | ||
| source_tests.lua | ||
| source_text.lua | ||
| source_text_tests.lua | ||
| source_undo.lua | ||
| test.lua | ||
| text.lua | ||
| text_tests.lua | ||
| undo.lua | ||
README.md
Plain text with lines
An editor for plain text where you can also seamlessly insert line drawings. Designed above all to be easy to modify and give you early warning if your modifications break something.
http://akkartik.name/lines.html
Invocation
To run from the terminal, pass this directory to LÖVE, optionally with a file path to edit.
Alternatively, turn it into a .love file you can double-click on:
$ zip -r /tmp/lines.love *.lua
By default, lines.love reads/writes the file lines.txt in your default
user/home directory (https://love2d.org/wiki/love.filesystem.getUserDirectory).
To open a different file, drop it on the lines.love window.
Keyboard shortcuts
While editing text:
ctrl+fto find patterns within a filectrl+cto copy,ctrl+xto cut,ctrl+vto pastectrl+zto undo,ctrl+yto redoctrl+=to zoom in,ctrl+-to zoom out,ctrl+0to reset zoomalt+right/alt+leftto jump to the next/previous word, respectivelyctrl+eto modify the sources
For shortcuts while editing drawings, consult the online help. Either:
- hover on a drawing and hit
ctrl+h, or - click on a drawing to start a stroke and then press and hold
hto see your options at any point during a stroke.
lines.love has been exclusively tested so far with a US keyboard layout. If you use a different layout, please let me know if things worked, or if you found anything amiss: http://akkartik.name/contact
Known issues
-
No support yet for Unicode graphemes spanning multiple codepoints.
-
No support yet for right-to-left languages.
-
Undo/redo may be sluggish in large files. Large files may grow sluggish in other ways. lines.love works well in all circumstances with files under 50KB.
-
If you kill the process, say by force-quitting because things things get sluggish, you can lose data.
-
The text cursor will always stay on the screen. This can have some strange implications:
- A long series of drawings will get silently skipped when you hit page-down, until a line of text can be showed on screen.
- If there's no line of text at the top of the file, you may not be able to scroll back up to the top with page-up.
So far this app isn't really designed for drawing-heavy files. For now I'm targeting mostly-text files with a few drawings mixed in.
-
No clipping yet for drawings. In particular, circles/squares/rectangles and point labels can overflow a drawing.
-
Long wrapping lines can't yet distinguish between the cursor at end of one screen line and start of the next, so clicking the mouse to position the cursor can very occasionally do the wrong thing.
-
Touchpads can drag the mouse pointer using a light touch or a heavy click. On Linux, drags using the light touch get interrupted when a key is pressed. You'll have to press down to drag.
-
Can't scroll while selecting text with mouse.
-
No scrollbars yet. That stuff is hard.
-
When editing sources, selecting text is not yet completely implemented.
Mirrors and Forks
Updates to lines.love can be downloaded from the following mirrors in addition to the website above:
- https://github.com/akkartik/lines.love
- https://repo.or.cz/lines.love.git
- https://codeberg.org/akkartik/lines.love
- https://tildegit.org/akkartik/lines.love
- https://git.tilde.institute/akkartik/lines.love
- https://git.sr.ht/~akkartik/lines.love
- https://notabug.org/akkartik/lines.love
- https://pagure.io/lines.love
Forks of lines.love are encouraged. If you show me your fork, I'll link to it here.
- https://github.com/akkartik/lines-polygon-experiment -- an experiment that
uses separate shortcuts for regular polygons.
ctrl+3for triangles,ctrl+4for squares, etc. - https://codeberg.org/akkartik/text.love -- a stripped down version without drawings; useful starting point for some forks
- https://git.sr.ht/~akkartik/pensieve.love -- a note-taking app on an infinite 2D surface. Still in development.
- https://git.sr.ht/~akkartik/capture.love -- a blank-slate mode for the note-taking app, so all the stuff pensieve.love puts on screen doesn't cause you to forget what you came to write down.
Associated tools
- https://codeberg.org/akkartik/lines2md exports lines.love files to Markdown and (non-editable) SVG.