git.iko.soy/urbit.org
on master help sign in
unbold example code titles
20c0b4ctinnus-napbus
arvo/clay/foreign-requests.md+2−2
compare with master
unifiedsplit
@@ -38,7 +38,7 @@ We'll use a fake ~nes as the the foreign ship and a fake ~zod as the local ship.
38
38
39First we'll set permissions on the foreign ship. Here's a simple thread that just sends a task to clay:
39First we'll set permissions on the foreign ship. Here's a simple thread that just sends a task to clay:
40
40
41−**`send-clay-task.hoon`**
41+`send-clay-task.hoon`
42
42
43```hoon
43```hoon
44/- spider
44/- spider
@@ -72,7 +72,7 @@ If we scry the file for its permissions with a `%p` care, we'll see ~zod is now
72
72
73Next, save the following thread to `ted/send-task-take-gift.hoon` on ~zod:
73Next, save the following thread to `ted/send-task-take-gift.hoon` on ~zod:
74
74
75−**`send-task-take-gift.hoon`**
75+`send-task-take-gift.hoon`
76
76
77```hoon
77```hoon
78/- spider
78/- spider
arvo/clay/merge.md+1−1
@@ -61,7 +61,7 @@ Example:
61
61
62Here's a thread that sends the given `task:clay` to clay and prints the `gift:clay` response:
62Here's a thread that sends the given `task:clay` to clay and prints the `gift:clay` response:
63
63
64−**`send-task.hoon`**
64+`send-task.hoon`
65
65
66```hoon
66```hoon
67/- spider
67/- spider
arvo/clay/mounts.md+2−2
@@ -35,7 +35,7 @@ Example:
35
35
36Here's a thread that sends a `task:clay` and takes a `gift:clay` in response:
36Here's a thread that sends a `task:clay` and takes a `gift:clay` in response:
37
37
38−**`send-task-take-gift.hoon`**
38+`send-task-take-gift.hoon`
39
39
40```hoon
40```hoon
41/- spider
41/- spider
@@ -83,7 +83,7 @@ Example:
83
83
84Here's a thread which will send the given `task:clay` to clay.
84Here's a thread which will send the given `task:clay` to clay.
85
85
86−**`send-task.hoon`**
86+`send-task.hoon`
87
87
88```hoon
88```hoon
89/- spider
89/- spider
arvo/clay/permissions.md+2−2
@@ -94,7 +94,7 @@ Example:
94
94
95Here's a generic thread that just sends the given `task:clay` to clay so we can try a few different things:
95Here's a generic thread that just sends the given `task:clay` to clay so we can try a few different things:
96
96
97−**`send-clay-task.hoon`**
97+`send-clay-task.hoon`
98
98
99```hoon
99```hoon
100/- spider
100/- spider
@@ -233,7 +233,7 @@ Example:
233
233
234Here's a generic thread that sends the given `task:clay` and receives a gift which it just prints to the dojo.
234Here's a generic thread that sends the given `task:clay` and receives a gift which it just prints to the dojo.
235
235
236−**`send-task-take-gift.hoon`**
236+`send-task-take-gift.hoon`
237
237
238```hoon
238```hoon
239/- spider
239/- spider
arvo/clay/read.md+5−5
@@ -109,7 +109,7 @@ You can use whichever you prefer. The `path` will usually be a path to a file or
109
109
110Example:
110Example:
111
111
112−**`read-file.hoon`**
112+`read-file.hoon`
113
113
114```hoon
114```hoon
115/- spider
115/- spider
@@ -181,7 +181,7 @@ This subscribes to the next version of the specified file. The `mood` structure
181
181
182If you subscribe to the current case of the desk, clay will not respond until the file changes. If you subscribe to a previous case of the desk and the file has changed in between then and now, it will immediately return the first change it comes across in that range. For example, if you're currently at case `100`, subscribe to case `50` and the file in question has been modified at both `60` and `80`, clay will immediately return the version of the file at case `60`.
182If you subscribe to the current case of the desk, clay will not respond until the file changes. If you subscribe to a previous case of the desk and the file has changed in between then and now, it will immediately return the first change it comes across in that range. For example, if you're currently at case `100`, subscribe to case `50` and the file in question has been modified at both `60` and `80`, clay will immediately return the version of the file at case `60`.
183
183
184−**`sub-next.hoon`**
184+`sub-next.hoon`
185
185
186```hoon
186```hoon
187/- spider
187/- spider
@@ -271,7 +271,7 @@ Example:
271
271
272This thread will subscribe to `/foo/txt` with an `%x` care and `/bar/txt` with a `%u` care. It will print out the `%wris` it gets back from clay.
272This thread will subscribe to `/foo/txt` with an `%x` care and `/bar/txt` with a `%u` care. It will print out the `%wris` it gets back from clay.
273
273
274−**`sub-mult.hoon`**
274+`sub-mult.hoon`
275
275
276```hoon
276```hoon
277/- spider
277/- spider
@@ -379,7 +379,7 @@ Example:
379
379
380This thread will subscribe to changes to your `%home` desk for the next three minutes. The `track` is `%.y` so it will only inform you of changes, not send the full `nako`. It will only get updates if the specified file exists. It contains a `main-loop` that will take an arbitrary number of signs and print them out in the dojo. Since it never ends, you'll need to stop it with the `:spider|kill` command in the dojo.
380This thread will subscribe to changes to your `%home` desk for the next three minutes. The `track` is `%.y` so it will only inform you of changes, not send the full `nako`. It will only get updates if the specified file exists. It contains a `main-loop` that will take an arbitrary number of signs and print them out in the dojo. Since it never ends, you'll need to stop it with the `:spider|kill` command in the dojo.
381
381
382−**`sub-many.hoon`**
382+`sub-many.hoon`
383
383
384```hoon
384```hoon
385/- spider
385/- spider
@@ -475,7 +475,7 @@ Example:
475
475
476This thread will subscribe to the `%next` version of `/foo/txt`, then immediately cancel the subscription and wait for a response to print (which it will never receive).
476This thread will subscribe to the `%next` version of `/foo/txt`, then immediately cancel the subscription and wait for a response to print (which it will never receive).
477
477
478−**`stop-sub.hoon`**
478+`stop-sub.hoon`
479
479
480```hoon
480```hoon
481/- spider
481/- spider
arvo/clay/write.md+3−3
@@ -57,7 +57,7 @@ Now we'll look at some example threads:
57
57
58## Add File
58## Add File
59
59
60−**`add-file.hoon`**
60+`add-file.hoon`
61
61
62```hoon
62```hoon
63/- spider
63/- spider
@@ -95,7 +95,7 @@ Here's a breakdown of the `task:clay` we sent:
95
95
96## Delete File
96## Delete File
97
97
98−**`delete-file.hoon`**
98+`delete-file.hoon`
99
99
100```hoon
100```hoon
101/- spider
101/- spider
@@ -136,7 +136,7 @@ Identical to the [Add File](#add-file) example, just replace `%ins` with `%mut`.
136
136
137Since `soba:clay` is just a `list` of `miso:clay`, you can add a bunch of `miso:clay` and they'll all be applied. This thread adds three files and then deletes them. Here there's only one type of `miso` in each request but you could mix different types together too.
137Since `soba:clay` is just a `list` of `miso:clay`, you can add a bunch of `miso:clay` and they'll all be applied. This thread adds three files and then deletes them. Here there's only one type of `miso` in each request but you could mix different types together too.
138
138
139−**`multi-change.hoon`**
139+`multi-change.hoon`
140
140
141```hoon
141```hoon
142/- spider
142/- spider