tree-edit

tree-edit copied to clipboard

To prevent bugs like #60

ethan-leba

After much effort fighting against the highlighting inclinations of grammars, I've no choice but to fork. This branch is the future of tree-edit and will be merged once PRs in...

ethan-leba

Hard-coded grammars are difficult to maintain

2

Since compiled grammar binaries come from other sources, they can quite easily become out-of-sync with the hard-coded grammars. It's better for the compiled form and the source form (whether `json`...

ubolonton

adds minor tree-edit-mode

2

👋 thought i'd add a PR to check if you want to pull this into tree-edit or a separate package. if you do, there's probably still some more tweaks i...

fgeller

### TODO: * [ ] Complete `tree-edit-syntax-snippets` for all nodes * [ ] Add keybindings in `tree-edit-nodes` for all nodes * [ ] Address disabled tests in `tests/test-c.el`

ethan-leba

ethan-leba

Performance issues

1

There's a noticable delay once we hit ~10 statements in a block: ``` private void foo(String args) { break; break; break; break; break; break; break; break; break; break; } ```...

ethan-leba

The codebase uses `user-error`, but we should probably make a `tree-edit-error` in case anyone wants to catch it.

ethan-leba

Currently attempting to avy jump to a call in Python in the following scenario will only yield one choice, due to the node layout: ``` [[foo()].baz()] ``` This is because...

ethan-leba

Discussion on providing a non-evil editing mode for tree-edit

11

New 'layered' package model I'm considering: 1. `tree-edit-core`: Core structural editing logic, what `tree-edit.el` is currently. To be used by refactoring packages or those who aren't sold on modal editing....

ethan-leba