# some primitives for checking stream contents
== code
# instruction effective address register displacement immediate
# . op subop mod rm32 base index scale r32
# . 1-3 bytes 3 bits 2 bits 3 bits 3 bits 3 bits 2 bits 2 bits 0/1/2/4 bytes 0/1/2/4 bytes
# compare all the data in a stream (ignoring the read pointer)
stream-data-equal?: # f : (address stream), s : (address string) -> eax : boolean
# . prologue
55/push-ebp
89/copy 3/mod/direct 5/rm32/ebp . . . 4/r32/esp . . # copy esp to ebp
# . save registers
51/push-ecx
52/push-edx
56/push-esi
57/push-edi
# esi = f
8b/copy 1/mod/*+disp8 5/rm32/ebp . . . 6/r32/esi 8/disp8 . # copy *(ebp+8) to esi
# eax = f->write
8b/copy 0/mod/indirect 6/rm32/esi . . . 0/r32/eax . . # copy *esi to eax
# maxf/edx = f->data + f->write
8d/copy-address 1/mod/*+disp8 4/rm32/sib 6/base/esi 0/index/eax . 2/r32/edx 0xc/disp8 . # copy esi+eax+12 to edx
# currf/esi = f->data
81 0/subop/add 3/mod/direct 6/rm32/esi . . . . . 0xc/imm32 # add to esi
# edi = s
8b/copy 1/mod/*+disp8 5/rm32/ebp . . . 7/r32/edi 0xc/disp8 . # copy *(ebp+12) to edi
# if (f->write != s->length) return false
$stream-data-equal?:compare-lengths:
39/compare 0/mod/indirect 7/rm32/edi . . . 0/r32/eax . . # compare *edi and eax
75/jump-if-not-equal $stream-data-equal?:false/disp8
# currs/edi = s->data
81 0/subop/add 3/mod/direct 7/rm32/edi . . . . . 4/imm32 # add to edi
# eax = ecx = 0
31/xor 3/mod/direct 0/rm32/eax . . . 0/r32/eax . . # clear eax
31/xor 3/mod/direct 1/rm32/ecx # 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
Like all LÖVE apps, lines.love can be invoked either from a terminal or
by clicking on the application in a graphical desktop.
When invoked from a terminal, you can pass the love binary the path to either
the zipped lines.love or a directory containing lines.love unzipped.
```sh
$ path/to/love path/to/lines.love
$ path/to/love . # from this repo directory
$ path/to/love path/to/lines/directory # from anywhere
```
By default, lines.love reads/writes the file `lines.txt` in your default
user/home directory (`https://love2d.org/wiki/love.filesystem.getUserDirectory`).
When invoked from a terminal, you can pass in a different file to edit, either
to the zipped or unzipped versions:
```sh
$ path/to/love path/to/lines.love path/to/file/to/edit
$ path/to/love path/to/lines/directory /path/to/file/to/edit
```
On a graphical desktop you can also drag and drop a file icon on to the
lines.love window.
You can also configure the size of the window on the commandline. For example:
```sh
$ path/to/love path/to/lines.love -geometry 640x480+10+10 path/to/file/to/edit
```
The syntax of the geometry parameter is {width}x{height}+{x}+{y} which will
position the top-left corner of the window at co-ordinate (x,y). The geometry
parameter must come before the file to edit.
## Keyboard shortcuts
While editing text:
* `ctrl+f` to find patterns within a file
* `ctrl+c` to copy, `ctrl+x` to cut, `ctrl+v` to paste
* `ctrl+z` to undo, `ctrl+y` to redo
* `ctrl+=` to zoom in, `ctrl+-` to zoom out, `ctrl+0` to reset zoom
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 `h` to 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
* There's a bug in freehand drawings (`ctrl+p` mode) that causes them to be
highlighted even when the mouse is nowhere near them.
* No support yet for Unicode graphemes spanning multiple codepoints.
* Undo/redo may be sluggish in large files. Large files may grow sluggish in
other ways.
* 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 and point labels can
overflow a drawing.
* Insufficient handling of constraints when moving points. For example, if you
draw a manhattan line and then move one of the points, you may not be able
to hover on it anymore.
There's two broad ways to fix this. The first is to relax constraints,
switch the manhattan line to not be manhattan. The second is to try to
maintain constraints. Either constrain the point to only move along one line
(but what if it's connected to two manhattan lines?!), or constrain the
other end of the line to move alongside. I'm not sure yet which would be
more useful. Getting into constraints would also make the program more
complex.
Bottomline: at the moment moving points connected to manhattan lines,
rectangles or squares can break drawings in subtle ways.
* 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.
## 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://pagure.io/lines.love
Forks of lines.love are encouraged. If you show me your fork, I'll link to it
here.
## Feedback
[Most appreciated.](http://akkartik.name/contact)