11The Dojo is our shell; it processes system commands and returns output. It's a
12good place to quickly experiment with Urbit. On the surface the Dojo is just a
13Hoon REPL. On the inside, the Dojo is a system for operating on and transforming
19You can use the Dojo to run arbitrary Hoon code, as well as non-Hoon system
24Evaluate a Hoon expression (whitespace matters):
27~your-urbit:dojo> (add 2 2)
28~your-urbit:dojo> %+ add 2 2
31Tall-form Hoon may require multiple lines:
34~your-urbit:dojo> %+ add
39Hoon uses something called [the subject](/docs/learn/hoon/hoon-tutorial/the-subject-and-its-legs).
40The Dojo has its own subject, and that's where Hoon's equivalent of variables,
41called faces, are stored.
43Use `=var` to save faces to the Dojo subject.
46~your-urbit:dojo> =foo (add 2 2)
49Note, however, that `=var` is Dojo syntax, not Hoon syntax. You cannot bind a
50face in a `.hoon` file in this way.
54Use `=dir` to set the current working directory:
57~your-urbit:dojo> =dir %/web
60(`%` represents your current directory. For a complete explanation on urbit
61paths, see the [filesystem section](../filesystem))
63Generators (files in `/gen`) are run with `+`:
66~your-urbit:dojo> +hello 'world'
69Save output to a file in `%clay` with `*`:
72~your-urbit:dojo> *some/file/path/hoon 'hello world'
75Run system commands from `:hood`, like `reload`, using `|`:
78~your-urbit:dojo> |reload %eyre
83Generators are short Hoon scripts, saved as `.hoon` files in the `/gen`
84directory. Many Dojo commands exist in the form of generators. The syntax for
85running a generator is `+genname` for a generator saved as `genname.hoon`.
89Accepts a path and displays the file. Similar to Unix `cat`.
92~your-urbit:dojo> +cat %/gen/curl/hoon
97Generates a code that is used to remotely log into your ship. No
101~your-urbit:dojo> +code
106Retrives data from a URL. Accepts a `tape`. Similar to Unix `curl`.
109~your-urbit:dojo> +curl "http://nyt.com"
114Just prints the argument. Accepts a `@ta`.
117~your-urbit:dojo> +hello 'mars'
122Similar to Unix `ls`. Accepts a path.
125~your-urbit:dojo> +ls %/web
126~your-urbit:dojo> +ls /~talsur-todres/home/2/web/notes
131Generates a random moon from a planet. No arguments.
134~your-urbit:dojo> +moon
139Compile the current state of the kernel and output a
140noun. Usually downloaded to a file in unix. No arguments.
143~your-urbit:dojo> .urbit/pill +solid
148Testrunner. Can test multiple generators at once, conventionally ones
149in the `/test` folder. Takes a path.
152~your-urbit:dojo> +test /lib
157Generate a ticket for an urbit ship. Takes an urbit name (`@p`).
161~your-urbit:dojo> +ticket ~talsur-todres-your-urbit
166Generate a recursive directory listing. Takes a path.
169~your-urbit:dojo> +tree %/web
174The hood is the system daemon. See `gen/hood` and `app/hood`.
176`|hi` - Sends a direct message. Sort of like Unix `write`. Accepts
177an urbit name (`@p`) and a string (`tape`, which is text wrapped with double-quotes).
180~your-urbit:dojo> |hi ~binzod "you there?"
183`|link` / `|unlink` - Link / unlink a remote app. Accepts an
184Urbit name and an app name.
187~your-urbit:dojo> |link ~talsur-todres %octo
190`|mass` - Prints the current memory usage of all the kernel modules.
194~your-urbit:dojo> |mass
197`|reload` - Reloads a kernel module (vane) from source. Accepts any
201~your-urbit:dojo> |reload %clay %eyre
204*`|reset`* - Reloads `hoon.hoon` and all modules. No arguments.
207~your-urbit:dojo> |reset
210*`|start`* - Starts an app. Accepts an app name.
213~your-urbit:dojo> |start %curl
220;h3(class "first child")
224A Dojo command is either a *source* or a *sink*. A source is just something
225that can be printed to your console or the result of some computation. A
226sink is an *effect*: a change to the filesystem, a network message, a
227change to your environment, or typed message to an app.
229Sources can be chained together, but we can only produce one effect per
234##### `=` - Set variable
236Set any environment variable:
239~your-urbit:dojo> =foo 42
240~your-urbit:dojo> (add 2 foo)
245Make sure to note that `=var` is Dojo syntax, not Hoon syntax. You cannot bind a
246variable in a `.hoon` file in this way.
248##### Special Variables
250There are a few special variables that the Dojo maintains.
252##### `:` - Send to app
254`:app` goes to a local `app`, `:~ship/app` goes to the `app` on `~ship`.
256Send a `helm-hi` message to `hood`:
259~your-urbit:dojo> :hood &helm-hi 'hi'
262Apps usually expect marked data, so `&` is often used here.
264##### `*` - Save in `%clay`
266Save a new `.udon` ([Udon](../udon)) file in `web`:
269~your-urbit:dojo> *%/web/foo/udon '# hello'
272The last component of the path is expected to be the mark (or mime
275##### `.` - Export to Unix
277Export a noun to Unix with `.`:
280~your-urbit:dojo> .foo/bar/baz (add 2 2)
283Which creates a file at `pier/.urb/put/foo/bar.baz`.
285This is very often used with `+solid`:
288~your-urbit:dojo> .urbit/pill +solid
291Which outputs a new `urbit.pill` to `pier/.urb/put/urbit.pill`
295##### `&` - Mark conversion
297Convert between marks using `&`:
300~your-urbit:dojo> &html &md '# hello'
301'<html><head></head><body><div><h1 id="-hello">hello</h1></div></body></html>'
304##### `_` - Run a function
306Use `_` to run a gate (or function):
308Write an arbitrary function and pass data to it:
311~your-urbit:dojo> _|=([a=@] (mul a 3)) 3
315Use a function to get the status code from an http request:
318~your-urbit:dojo> _|=([p=@ud q=* r=*] p) +http://google.com
322##### `+` `-` - HTTP requests
324`+http[s]://example.com` - sends a GET request
326`+http[s]://example.com &json [%s 'hi']` - sends a POST request with the
327JSON `"hi"` in the body.
329`-http[s]://example.com &json [%s 'hi']` - sends a PUT request with the
330JSON `"hi"` in the body.
332Note that the first of these is a source while the last two are sinks.
334##### `+` - Generators
336Generators are simple Hoon scripts loaded from the filesystem. They live
339An example of a generator that is built into your urbit is `+code`. It produces
340the code needed to log into your ship remotely.
343~your-urbit:dojo> +code
344fintyr-haldet-fassev-solhex
349You can use `=` to set an environment variable in Dojo, but there are
350a few reserved names that have special uses.
354Current working `%clay` desk and revision. Read / write.
359~your-urbit:dojo> =dir %/web
360~your-urbit:dojo> +ls %
361404/hoon docs/ dojo/hoon lib/ listen/hoon md static/udon talk/ testing/udon tree/main/ unmark/ womb/
366Current set of libraries (`/lib`) in your environment. Can be set
367with `/+`. Read / write.
372~your-urbit:dojo> /+ react
373~your-urbit:dojo> :: now we can use arms from lib/react.hoon
374~your-urbit:dojo> (react-vale:react %div)
379Current set of structures (`/sur`) in your environment. Can be set
380with `/-`. Read / write.
385~your-urbit:dojo> /- sole
386~your-urbit:dojo> :: now we can use arms in sur/sole.hoon
387~your-urbit:dojo> `sole-effect:sole`[%bel ~]
392The current (128-bit `@da`) time. Read-only.
399~2016.3.21..21.10.57..429a
404The current urbit ship. Read-only.
416512 bits of entropy. Read-only.
423\/0vnt.d474o.gpahj.jcf3o.448fh.2lamb.82ljm.8ol8u.b02vi.mrvvp.b7et2.knb7m.l8he\/
424 8.8qb9s.drm36.77n9b.a0qst.30g03.l5lb5.nvsbc.v39tn
430If you encounter `%dy-edit-busy` while entering commands, it is
431because your Dojo is blocked on a timer or an HTTP request. Type backspace
432and your Dojo will end the blocked command.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list