on master help sign in
Removing redundant information, clarifying flow
6cb91afMatilde Park
learn/hoon/hoon-tutorial/setup.md+6−53
@@ -17,35 +17,9 @@ An **urbit** is an Urbit virtual computer with persistent state that can connect
17
17
18These may not look like numbers, but they are. Each urbit name is written in a base-256 format, where each 'digit' is a syllable. Imagine your phone number as a pronounceable string which sounds like a name in a foreign language. An ordinary user-level urbit is a 'planet', and it's named by a 32-bit number. The latter is represented as a four-syllable string; e.g., the planet name `~taglux-nidsep` is the number 6,095,360.
18These may not look like numbers, but they are. Each urbit name is written in a base-256 format, where each 'digit' is a syllable. Imagine your phone number as a pronounceable string which sounds like a name in a foreign language. An ordinary user-level urbit is a 'planet', and it's named by a 32-bit number. The latter is represented as a four-syllable string; e.g., the planet name `~taglux-nidsep` is the number 6,095,360.
19
19
20−For this tutorial you'll boot and run what we call a 'comet'. **Comets** are urbits whose names are 128-bits or 16 syllables, such as:
20+## Getting started
21
21
22−`~hillyn-pitwet-hasdur-paswer--miszod-rabpex-divrup-fogdur`
23−
24−Comet names aren't quite as memorable as others, but they're disposable identities that anyone can make for free to join the live network. Thus, comets make the ideal urbit for playing around with Hoon, asking for help from other Urbit devs in [Talk](./docs/using/messaging.md) if you need it, and showing off Urbit to your friends.
25−
26−## Booting a Comet
27−
28−To boot your comet, go into the command line and run the following command from the directory that was created during Urbit installation:
29−
30−```
31−$ urbit -c mycomet
32−```
33−
34−This will take a few minutes and will spin out a bunch of boot messages. Toward the end, you'll see something like:
35−
36−```
37−ames: on localhost, UDP 31337.
38−http: live (insecure, public) on 8080
39−http: live ("secure", public) on 8443
40−http: live (insecure, loopback) on 12321
41−~palnul_nocser:dojo>
42−```
43−
44−(There will likely be other messages as well.)
45−
46−Look at the prompt, `~palnul_nocser:dojo>`. To the left of the `:` you'll see an abbreviation of the comet name you just booted, `~palnul_nocser` in this case. To the right is the name of a local application, `dojo`. **Dojo** is the Urbit command line app; it's also a Hoon [REPL](https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop) we'll use to run simple Hoon examples.
47−
48−To make sure everything is working, type `(add 2 2)` at the prompt and hit return. Your screen now shows:
22+Once you've installed your development ship (or your own ship on the live network), let's try a basic command. Type `(add 2 2)` at the prompt and hit return. Your screen now shows:
49
23
50```
24```
51ames: on localhost, UDP 31337.
25ames: on localhost, UDP 31337.
@@ -66,36 +40,15 @@ You just used a function from the Hoon standard library, `add`. Next, quit Urbi
66$
40$
67```
41```
68
42
69−Your comet isn't running anymore and you're back at your computer's normal terminal prompt. You now have a `mycomet` directory for your Urbit comet; this directory is your comet's **pier** and it contains the entirety of your comet's state.
43+Your ship isn't running anymore and you're back at your computer's normal terminal prompt. If your ship is `~palnul_nocser`, then you can restart the ship by typing:
70−
71−Right now the only thing in your pier is your comet's system files:
72−
73−```
74−$ ls -a /path/to/mycomet
75−./ ../ .urb/
76−```
77−
78−Restarting your already-created comet from the terminal is like creating a new one, but without the `-c` flag. (The `-c` is for "create".)
79−
80−```
81−$ urbit mycomet
82−```
83−
84−Because the comet has already been booted it won't take very long to get it running again. There are also fewer startup messages:
85
44
86```
45```
87−$ urbit mycomet
88−[...]
89−ames: on localhost, UDP 31337.
90−http: live (insecure, public) on 8080
91−http: live ("secure", public) on 8443
92−http: live (insecure, loopback) on 12321
93−~palnul_nocser:dojo>
46+urbit palnul_nocser
94```
47```
95
48
96## Another Noun
49## Another Noun
97
50
98−You've already used a standard library function to produce one value, in the dojo. Now that your comet is running again, let's try another. Enter the number `17`.
51+You've already used a standard library function to produce one value, in the dojo. Now that your ship is running again, let's try another. Enter the number `17`.
99
52
100> We won't show the `~palnul_nocser:dojo> ` prompt from here on out. We'll just show the echoed command along with its result.
53> We won't show the `~palnul_nocser:dojo> ` prompt from here on out. We'll just show the echoed command along with its result.
101
54
@@ -106,7 +59,7 @@ You'll see:
10617
5917
107```
60```
108
61
109−You asked dojo to evaluate `17` and it echoed the number back at you. This value is a 'noun'. But what is a noun? Move on to lesson 1.2 for the answer.
62+You asked dojo to evaluate `17` and it echoed the number back at you. This value is a 'noun'. We'll talk more about nouns in [Chapter 1.2](docs/learn/hoon/hoon-tutorial/nouns/), but first let's write a very basic program.
110
63
111## Generators
64## Generators
112
65