slight reorg in Readme
This commit is contained in:
parent
299890f593
commit
d202e2ce99
|
@ -70,14 +70,16 @@ found anything amiss: http://akkartik.name/contact
|
||||||
|
|
||||||
* No support yet for Unicode graphemes spanning multiple codepoints.
|
* No support yet for Unicode graphemes spanning multiple codepoints.
|
||||||
|
|
||||||
* Undo/redo can be sluggish in large files. If things get sluggish, killing
|
* Undo/redo can be sluggish in large files.
|
||||||
the process can lose data.
|
|
||||||
|
|
||||||
* Large files may grow sluggish in other ways. I've noticed in 100KB files
|
* Large files may grow sluggish in other ways. I've noticed in 100KB files
|
||||||
that closing the window can take a few seconds. And it seems to take longer
|
that closing the window can take a few seconds. And it seems to take longer
|
||||||
in proportion to how far down my edits are. The phenomenon persists even if
|
in proportion to how far down my edits are. The phenomenon persists even if
|
||||||
I take out undo history.
|
I take out undo history.
|
||||||
|
|
||||||
|
* 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
|
* The text cursor will always stay on the screen. This can have some strange
|
||||||
implications:
|
implications:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue