summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--2021/talks/structural.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/2021/talks/structural.md b/2021/talks/structural.md
index 889de8a..d1fca71 100644
--- a/2021/talks/structural.md
+++ b/2021/talks/structural.md
@@ -10,7 +10,7 @@ Ethan Leba
In this talk, I'll discuss a vision for how writing code could be, where the
editing operations map directly to the primitives of the language itself -- and
-my humble attempt of implementing this vision. **tree-edit** seeks to provides a
+my humble attempt of implementing this vision. _tree-edit_ seeks to provides a
structural editing plugin supporting conceivably any language with a tree-sitter
parser.
@@ -24,19 +24,19 @@ etc. So when we write and edit code, why do we edit in terms of deleting,
inserting, replacing characters – not wrapping, inserting, raising,
deleting expressions and statements?
-I'll also discuss the implementation of `tree-edit`, which uses a novel
+I'll also discuss the implementation of tree-edit, which uses a novel
combination of the fantastic
[tree-sitter](https://github.com/emacs-tree-sitter/elisp-tree-sitter) parser
with an embedded logic programming DSL ([miniKanren](http://minikanren.org/),
using elisp port [reazon](https://github.com/nickdrozd/reazon)) to power it's
syntax tree generation.
-Check out the GitHub repo at: https://github.com/ethan-leba/tree-edit
+Check out the GitHub repo [here](https://github.com/ethan-leba/tree-edit)!
# Outline
- Discuss motivation (Why should I care?)
-- Demonstrate tree-edit (Live-coding with `tree-edit`)
+- Demonstrate tree-edit (Live-coding with tree-edit)
- Demonstrate tree-edit syntax tree generator (Elevator pitch on miniKanren)
<!--