aboutsummaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
Diffstat (limited to 'posts')
-rw-r--r--posts/OSC-52.md66
-rw-r--r--posts/introducing_tablespoon.md181
2 files changed, 247 insertions, 0 deletions
diff --git a/posts/OSC-52.md b/posts/OSC-52.md
new file mode 100644
index 0000000..8dccef9
--- /dev/null
+++ b/posts/OSC-52.md
@@ -0,0 +1,66 @@
1I use `ssh` a lot. Copying text from the remote machine to
2the host machine always sucked. But OSC-52 makes that easy.
3
4OSC-52 is an ANSI escape sequence to write text to the
5terminal emulator. The terminal emulator, if it understands
6what is going on, will in turn write this text to the system
7clipboard.
8
9What this means is some `printf` magic can send text to your
10clipboard. I store this one-liner in a script called
11`oclip`:
12
13```bash
14printf "\033]52;c;%s\007" "$(base64 <&0)"
15```
16
17and I run it with:
18
19```bash
20remote $ cat some_file.txt | oclip
21
22# some_file.txt's contents are now the host's clipboard
23```
24
25### The catch
26
27Your terminal emulator must support OSC-52, `alacritty` and
28`termux` seem to support this out of the box. In `st`,
29OSC-52 works with this change to `config.h`:
30
31```
32int allowwindowops = 1;
33```
34
35If you are using `tmux`, you need to flip this switch on:
36
37```
38set -s set-clipboard on
39```
40
41If you are inside `nvim`, it may work as expected as long as
42`$SSH_TTY` is set. I sometimes physically start a session,
43and `ssh` into the same session later from another machine,
44and `$SSH_TTY` remains unset, so I force OSC-52 in `nvim` at
45all times (see
46[nvimdoc](https://neovim.io/doc/user/provider.html#clipboard-osc52)):
47
48```lua
49vim.g.clipboard = {
50 name = 'OSC 52',
51 copy = {
52 ['+'] = require('vim.ui.clipboard.osc52').copy('+'),
53 ['*'] = require('vim.ui.clipboard.osc52').copy('*'),
54 },
55 paste = {
56 ['+'] = require('vim.ui.clipboard.osc52').paste('+'),
57 ['*'] = require('vim.ui.clipboard.osc52').paste('*'),
58 },
59}
60```
61
62If you are inside `nvim` inside `tmux` inside an `ssh`
63session inside `st`, you neeed all of the above tweaks.
64`nvim` will pass the contents around to `tmux`, which in
65turn will pass the contents to `st`, which should pass it to
66your system clipboard.
diff --git a/posts/introducing_tablespoon.md b/posts/introducing_tablespoon.md
new file mode 100644
index 0000000..957b6d4
--- /dev/null
+++ b/posts/introducing_tablespoon.md
@@ -0,0 +1,181 @@
1[tbsp](https://git.peppe.rs/languages/tbsp) (tree-based
2source-processing language) is an awk-like language that
3operates on tree-sitter syntax trees. To motivate the need
4for such a program, we could begin by writing a
5markdown-to-html converter using `tbsp` and
6[tree-sitter-md](https://github.com/tree-sitter-grammars/tree-sitter-markdown).
7We need some markdown to begin with:
8
9
10 # 1 heading
11
12 content of first paragraph
13
14 ## 1.1 heading
15
16 content of nested paragraph
17
18
19For future reference, this markdown is parsed like so by
20tree-sitter-md (visualization generated by
21[tree-viz](https://git.peppe.rs/cli/tree-viz)):
22
23
24 document
25 | section
26 | | atx_heading
27 | | | atx_h1_marker "#"
28 | | | heading_content inline "1 heading"
29 | | paragraph
30 | | | inline "content of first paragraph"
31 | | section
32 | | | atx_heading
33 | | | | atx_h2_marker "##"
34 | | | | heading_content inline "1.1 heading"
35 | | | paragraph
36 | | | | inline "content of nested paragraph"
37
38
39Onto the converter itself. Every `tbsp` program is written as
40a collection of stanzas. Typically, we start with a stanza
41like so:
42
43
44 BEGIN {
45 int depth = 0;
46
47 print("<html>\n");
48 print("<body>\n");
49 }
50
51
52The stanza begins with a "pattern", in this case, `BEGIN`,
53and is followed a block of code. This block specifically, is
54executed right at the beginning, before traversing the parse
55tree. In this stanza, we set a "depth" variable to keep
56track of nesting of markdown headers, and begin our html
57document by printing the `<html>` and `<body>` tags.
58
59We can follow this stanza with an `END` stanza, that is
60executed after the traversal:
61
62
63 END {
64 print("</body>\n");
65 print("</html>\n");
66 }
67
68
69In this stanza, we close off the tags we opened at the start
70of the document. We can move onto the interesting bits of
71the conversion now:
72
73
74 enter section {
75 depth += 1;
76 }
77 leave section {
78 depth -= 1;
79 }
80
81
82The above stanzas begin with `enter` and `leave` clauses,
83followed by the name of a tree-sitter node kind: `section`.
84The `section` identifier is visible in the
85tree-visualization above, it encompasses a markdown-section,
86and is created for every markdown header. To understand how
87`tbsp` executes above stanzas:
88
89
90 document ... depth = 0
91 | section <-------- enter section (1) ... depth = 1
92 | | atx_heading
93 | | | inline
94 | | paragraph
95 | | | inline
96 | | section <----- enter section (2) ... depth = 2
97 | | | atx_heading
98 | | | | inline
99 | | | paragraph
100 | | | | inline
101 | | | <----------- leave section (2) ... depth = 1
102 | | <-------------- leave section (1) ... depth = 0
103
104
105The following stanzas should be self-explanatory now:
106
107
108 enter atx_heading {
109 print("<h");
110 print(depth);
111 print(">");
112 }
113 leave atx_heading {
114 print("</h");
115 print(depth);
116 print(">\n");
117 }
118
119 enter inline {
120 print(text(node));
121 }
122
123
124But an explanation is included nonetheless:
125
126
127 document ... depth = 0
128 | section <-------- enter section (1) ... depth = 1
129 | | atx_heading <- enter atx_heading ... print "<h1>"
130 | | | inline <--- enter inline ... print ..
131 | | | <----------- leave atx_heading ... print "</h1>"
132 | | paragraph
133 | | | inline <--- enter inline ... print ..
134 | | section <----- enter section (2) ... depth = 2
135 | | | atx_heading enter atx_heading ... print "<h2>"
136 | | | | inline <- enter inline ... print ..
137 | | | | <-------- leave atx_heading ... print "</h2>"
138 | | | paragraph
139 | | | | inline <- enter inline ... print ..
140 | | | <----------- leave section (2) ... depth = 1
141 | | <-------------- leave section (1) ... depth = 0
142
143
144The
145[examples](https://git.peppe.rs/languages/tbsp/tree/examples)
146directory contains a complete markdown-to-html converter,
147along with a few other motivating examples.
148
149### Usage
150
151The `tbsp` evaluator is written in rust, use cargo to build
152and run:
153
154 cargo build --release
155 ./target/release/tbsp --help
156
157
158`tbsp` requires three inputs:
159
160- a `tbsp` program, referred to as "program file"
161- a language
162- an input file or some input text at stdin
163
164
165You can run the interpreter like so (this program prints an
166overview of a rust file):
167
168 $ ./target/release/tbsp \
169 -f./examples/code-overview/overview.tbsp \
170 -l rust \
171 src/main.rs
172 module
173 └╴struct Cli
174 └╴trait Cli
175 └╴fn program
176 └╴fn language
177 └╴fn file
178 └╴fn try_consume_stdin
179 └╴fn main
180
181
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-05 05:10:40 +0100