tree-edit

tree-edit copied to clipboard

File explaining the usage of evil-tree-edit. See http://www2.geog.ucl.ac.uk/~plewis/teaching/unix/vimtutor and https://github.com/abo-abo/lispy/blob/master/lispytutor/lispytutor.el

ethan-leba

Due to Python's whitespace-based parsing, there are oftentimes nodes with identical boundaries. For example, `{foo;}` in Java would simply be `foo` in Python, but the structure still implicitly exists. The...

ethan-leba

Using `helpful-key` on edit operations won't provide a named function, since the edits are defined as a lambda. This should be fixed. Maybe a tree-operator state? Open to other (easier)...

ethan-leba

Limit to the nearest sig. block? Or to grandparent?

ethan-leba

http://oremacs.com/lispy/#lispy-raise-some

ethan-leba

### Editing features - [x] Copy Should we be storing the node type on copy, or inferring it on usage? If we store type on copy, where does that live?...

ethan-leba

Currently the tests use the 'production' language configurations, which means the tests will need to be adjusted if we change the whitespace formatting, etc. Instead we should have test language...

ethan-leba

There are many node types that are only valid in a specific context. For example, a dictionary pair (`key : value`) is only valid within a dictionary node. Sometimes the...

ethan-leba

http://oremacs.com/lispy/#lispy-move-down

ethan-leba

support golang

7

hey! great presentation at emacsconf - thanks for pouring time into this project :) i'd love to try it for my daily work, but i use mainly golang. i'd like...

fgeller