Selection

[stefnotch]

Hold down and drag to select more stuff. How exactly should it work with nested elements?

I think I prefer the variant where carets are turned into ranges. A range is simply a start caret and an end caret. They don't have to be in the same row.

[stefnotch]

When something is selected, certain insert commands should attempt to wrap the selection. Like "select something" and then hit ( or "

[stefnotch]

To investigate

• Selecting + removing
• Selecting + copying
• Selecting + cutting
• Selecting + inserting (aka replacing)

e.g.

$$ a+\sqrt{b+\sqrt{c^2}} $$

$$ \frac{a}{b}+\frac{c}{d} $$

[stefnotch]

When selecting this range

should it actually select that range^ or should it select according to brackets v

[stefnotch]

Seems like selecting according to mathlayout is the reasonable option. Start somewhere, end somewhere else, and then select their shared row.
So, those are valid selections

[stefnotch]

The table doesn't need ranges for selecting its cells. Instead it's a lot of individual row-selections!
Think: File list. You can drag-select and then unselect one file that you don't like.
Excel works the same way.

[stefnotch]

One can choose whether text deserves its own type of row and its own type of context, or whether it's just symbols with "quotes".

The symbols with quotes around them design isn't half bad.

• it forces you to only write text that's actually semantically useful. As in, text that's only an explanation absolutely belongs in the "annotations tree" and not in the math layout one.
• rendering is different: we have to do the parsing and custom rendering anyways
• shortcuts are different
• it makes writing formal grammars rather nice, because writing $A -> "a" A | "a"$ gets handled naturally
• "write some text, select it, put it in quotes => string"
• /Copium , because I definitely didn't try making it its own type of row and failed

[stefnotch]

Remember ctrl+d? Vscode actually has multiple selections!