diff options
| author | Sacha Chua <sacha@sachachua.com> | 2021-12-02 01:23:52 -0500 |
|---|---|---|
| committer | Sacha Chua <sacha@sachachua.com> | 2021-12-02 01:23:52 -0500 |
| commit | 3b6a2c161825236f442727107b02d30a4b4c0c70 (patch) | |
| tree | d604edeb2cfca73cd654abde2745a51f831a2540 /2021/talks/structural.md | |
| parent | 532bc5cda6dc0f094e9adcfdadfdc7bf435779f0 (diff) | |
| download | emacsconf-wiki-3b6a2c161825236f442727107b02d30a4b4c0c70.tar.xz emacsconf-wiki-3b6a2c161825236f442727107b02d30a4b4c0c70.zip | |
IRC notes from day 2
Diffstat (limited to '2021/talks/structural.md')
| -rw-r--r-- | 2021/talks/structural.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/2021/talks/structural.md b/2021/talks/structural.md index d4ce9188..c301fc3b 100644 --- a/2021/talks/structural.md +++ b/2021/talks/structural.md @@ -44,6 +44,25 @@ syntax tree generation. Check out the GitHub repo [here](https://github.com/ethan-leba/tree-edit)! +# Discussion + +IRC nick: ethan + +- any chance you tried this with Clojure as well? + - ethan: haven't tried it yet, i don't think tree-sitter-langs has a clojure grammar AFAIK + - yeah I use sogaiu's (https://github.com/sogaiu/tree-sitter-clojure) but it does not have if else and the rest, only the main data types +- so tree-edit is orthogonal to the LSP features? +- did not know that miniKanren had an elisp port +- Seems like a really cool use of logic programming. All the examples I've heard of are much simpler than this. +- Wow, voice control is a good point +- Could tree-edit be made to work with Org (orgdown!) itself, or maybe rather what would be needed to get such a unified tree-editing framework to work also for complex Org trees? +- Awesome talk. I'm definetly going to try out tree-edit later :) +- Amazing talk!! Such a cool project +- `andrea: absolutely! Also for Orgdown - which is a good start since it is much easier. +- Andrew Blinn's talk on Fructure and Ethan Leba's talk on Tree-edit are really insightful. +- Agreed about the lack of formal grammar (only a proliferation of parsers) being a limiting factor. Maybe we could bridge directly to the available commands without going through a grammar though. A unified tree-editing framework across languages but definitely including Org would be awesome (ala lispy/etc). + + # Outline - Discuss motivation (Why should I care?) |