Jared Hughes

Currently, clicking on an expression in the text will select the expression on the view (bolds the line width etc) and vice versa. This behavior does not extend to table...

Converting a simple table to text mode yields ``` table { x_1 = [1] @{ color: "#c74440", hidden: true } y_1 = [2] @{ color: "#2d70b3" } } ``` The...

The editor currently highlights only the current line. It would be clearer to highlight the entire containing statement, or perhaps instead draw a horizontal line before and after the current...

The error messages from the current Pratt-based parser were all hastily added while implementing the parser. They are better than the old Lezer-based parser but could be improved. Revisit them...

Text Mode currently applies its state with `Calc.setState()`. There are two ways to proceed for incremental updates: - use dispatched events like "set-item-latex", "set-item-colorlatex" etc, to change the state how...

The current behavior is treating a pair newline-newline as a "semicolon" between two expressions. I would rather have some approach that supports single-newline separation in most places. However, without mandated...

It could be confusing for someone to write `true = 5` but also have `@{lines: true}`. The scope doesn't really make sense there. Disallow `true = *anything*`, `false = *anything*`,...

This mainly applies to image URLs. Long strings should be collapsed by default to avoid making long horizontal scrollbars.

This thing:  - [ ] Fix or remove the "Add Item" dropdown - [ ] Remove or modify the "Edit list" cogwheel - [ ] Fix the "undo/redo" buttons...

This is a general issue on many style attributes. Their representation modifies from Raw to Aug then again from Aug to Text. Similarly, it modifies from Text to Aug and...