record keystrokes. then when an exception occurs bring up a popup asking user whether they'd like to report bug, and also whether they'd like to send keysequence and/or data

also just have a button for reporting bugs?

Part of 'scale better'.

You and Paul and I should talk about UI for this one I think, if possible.

Insert: A enter tab B enter tab C
alt+l (zooms into Home > A > B)
u (un-zooms to Home AND undoes insert)
ctrl+r (error trying to zoom back in)

1. Check out master
2. Delete all localstorage
3. Refresh

I see two copies of the intial data, with two cursors.

The bullet names at the top of the screen are clickable links in normal mode, but not in insert mode. Their color changes, I assume to indicate this. I find these color changes a bit distracting when there is a lot of text at the top of the screen. It might be worth tweaking the UI or providing an option to disable or something.

In particular, you're capturing important browser keys: ctrl+r, ctrl+shift+j etc. I think the default should be to let keys pass through if we can't figure out what to do with them.

implement some form of marks (m[a-z] or m[string]? 'a or '[string])
tagging, e.g. @mark that links to it

Jeff, I don't understand the 'tagging' comment.

It would be nice to have something like easymotion for within-bullet movement, if it's easy to implement

(especially low priority)

Switching the tests over to a standard framework like mocha will enable easier code coverage reports

Remove "meta" anywhere it appears in vimflowy.

I know it's in the documentation object. Might be other places.

What does this todo mean? Do you have any specifics in mind?

i followed by ctrl+r inserts the literal ctrl+r as though it were a character. It should probably insert nothing instead.

stylesheet that tries to look like workflowy

also possibly a custom option?

I don't know any way to use multiple documents in bitballoon, and I'm a bit scared about opening several instances of the same document in different tabs (perhaps irrationally).

use https://github.com/Matt-Esch/virtual-dom

'z' works fine, but clicking the +- icon doesn't update until e.g. the cursor moves

I sometimes use dd + p to effectively move a bullet. But (1) copying is slow when the tree is large, (2) I'm hesitant to do this because of concerns about losing data if there is a crash while moving, (3) if future features (aliasing, or plugins like time tracking) depend on the identity of bullets then it would be nice if the first paste inherited the identity of the original node.

It would be nice to do one of: (1) have a separate hotkey for some kind of "cut and paste once" option, that just moves the node rather than cutting it, or (2) only allow pasting once from a deleted tree (I'm totally fine having to copy explicitly if I want to make copies), (3) treat the first paste as a special move operation.

1. Go to a top-level bullet
2. Type <

An error is caught by workflowy. This should just do nothing instead.

Suggestion: yc

Jeff, not sure what you mean here either

Would be nice if gj and gk (or some other keys) moved up and down a graphical line rather than a bullet. I would probably prefer this as the j, k behavior in most cases, but I'm happy to use gj and gk until there are custom shortcuts.

https://github.com/easymotion/vim-easymotion

Instances should be their own class, and clearly documented. (strongly agree, just waiting to refactor until clones work) Some work done on the aliasing_jeff branch.

Methods should take in an instance/path, a node/row/datastore-object, or an id. Anything requiring an id should also be able to take a node. (It would be a bad idea to allow write-type methods needing an id/node to take an instance, because they might make larger changes than their interface suggests).

We should talk about whether we want the instance to include a list of nodes vs a list of ids and any internal datastructure trade-offs, but details are not as important compared to just making datatypes clearer than they are currently.