git.iko.soy/urbit.org
on master help sign in
pad to pam, net to fas
commit017b68cb947b595593f17be30147c771a9977a9a authorJohn Franklin <jfranklin9000@gmail.com> dateThu 18 Jul 2019, 21:29 (7 years ago) parentb058df5
6 files changed+11−11
compare with master
unifiedsplit
learn/arvo/ford.md+1−1 learn/arvo/gall.md+1−1 learn/vere/jetting.md+2−2 reference/hoon-expressions/rune/ket.md+2−2 reference/hoon-expressions/rune/sig.md+4−4 reference/troubleshooting.md+1−1
learn/arvo/ford.md+1−1
@@ -106,7 +106,7 @@ extremely useful function.
106106
107107## Ford runes
108108
109−One of the most common ways to use ford is through ford's runes, all of which begin with `/` ("net"). A ford rune runs a step of a ford build and places the result in the subject. There are various kinds of build steps, some of which take other build steps as parameters. The most common pattern is to have a sequence of ford runes at the top of a hoon source file that import the results of evaluating other hoon files. This is how we "import a library" in urbit: we add the result of compiling another hoon file into the current subject, possibly renaming it by wrapping a face around it.
109+One of the most common ways to use ford is through ford's runes, all of which begin with `/` ("fas"). A ford rune runs a step of a ford build and places the result in the subject. There are various kinds of build steps, some of which take other build steps as parameters. The most common pattern is to have a sequence of ford runes at the top of a hoon source file that import the results of evaluating other hoon files. This is how we "import a library" in urbit: we add the result of compiling another hoon file into the current subject, possibly renaming it by wrapping a face around it.
110110
111111Another common use case is assembling and rendering markdown templates into a single HTML file, to be sent as an HTTP response in urbit's web server `%eyre`. It's important to keep in mind that %ford is quite flexible and generic, and is used in other parts of urbit -- such as the dojo -- that would not traditionally fall under the purview of a build system.
112112
learn/arvo/gall.md+1−1
@@ -1064,7 +1064,7 @@ from the command line, which we we did with `:echo 5`
10641064(`:[app-name] [argument(s)]`).
10651065
10661066In this case, `++poke-noun` takes an argument (**sample**) `arg` and
1067−prints it to dojo with `~&` ([sigpad](/docs/reference/hoon-expressions/rune/sig#sigpad/)).
1067+prints it to dojo with `~&` ([sigpam](/docs/reference/hoon-expressions/rune/sig#sigpam/)).
10681068This is an unusual rune that formally "does nothing", but the interpreter
10691069detects it and printfs the first child, before executing the second as if the
10701070first didn't exist. This is a slightly hacky way of printing to the console,
learn/vere/jetting.md+2−2
@@ -103,9 +103,9 @@ There are multiple runes to do hinting, but we're going to concentrate
103103on three. All hinting runes start with a tilda ("sig"). A mnemonic
104104is "we're signaling some information to the interpreter".
105105
106−+ `~/` "signet": simple jet registration, using defaults for some arguments
106++ `~/` "sigfas": simple jet registration, using defaults for some arguments
107107+ `~%` "sigcen": more complicated jet registration, specifying all arguments
108−+ `~&` "sigpad": debugging printf
108++ `~&` "sigpam": debugging printf
109109
110110Feel free to use `~&` liberally! (Just remove them when you're done).
111111
reference/hoon-expressions/rune/ket.md+2−2
@@ -188,9 +188,9 @@ Regular: **2-fixed**.
188188'a'
189189```
190190
191−### ^& "ketpad"
191+### ^& "ketpam"
192192
193−`[%ktpd p=hoon]`: convert a core to a zinc core (covariant).
193+`[%ktpm p=hoon]`: convert a core to a zinc core (covariant).
194194
195195##### Produces
196196
reference/hoon-expressions/rune/sig.md+4−4
@@ -284,9 +284,9 @@ This should work fine:
284284573.147.844.013.817.084.101
285285```
286286
287−### ~/ "signet"
287+### ~/ "sigfas"
288288
289−`[%sgnt p=term q=hoon]`: jet registration for gate with
289+`[%sgfs p=term q=hoon]`: jet registration for gate with
290290registered context.
291291
292292##### Expands to
@@ -311,9 +311,9 @@ From the kernel:
311311 $(a (dec a), b +(b))
312312```
313313
314−### ~& "sigpad"
314+### ~& "sigpam"
315315
316−`[%sgpd p=hoon q=hoon]`: debugging printf.
316+`[%sgpm p=hoon q=hoon]`: debugging printf.
317317
318318##### Expands to
319319
reference/troubleshooting.md+1−1
@@ -160,7 +160,7 @@ The worst possibility, of course, is that your code runs but does
160160the wrong thing. This is relatively unusual in a typed
161161functional language, but it still happens.
162162
163−`~&` ([**sigpad**](@/docs/reference/hoon-expressions/rune/sig.md#sigpad)) is Hoon's debugging printf.
163+`~&` ([**sigpam**](@/docs/reference/hoon-expressions/rune/sig.md#sigpam)) is Hoon's debugging printf.
164164This pretty-prints its argument:
165165
166166```