dc2c990c0f
We want to decouple drum state & semantics from term.c. But we also want to continue showing printfs without mangling whatever the arvo side is doing. Short of formalizing various "terminal modes", the best we can do it assume that the main session is always in drum mode, and use that assumption to squeeze into the actual content stream when doing printfs. In essence, we insert the printf between the prompt and content, pushing the content up into terminal scrollback. Both the prompt and cursor position are maintained without knowledge of their original states. Because this logic relies on knowing the (accurate) terminal height, and this logic being the *only* thing in term.c that reads from the height, we no longer initialize the terminal size with a sane height. Instead, we set it to zero, and check for that to determine whether we're ready to use this logic or not. Due to the way this inserting works, trailing newlines are no longer required from the output. For consistency, we manually add trailing newlines when this logic cannot be used, both in the above-described circumstance, and the less-common case of u3l_log. This will of course need to be accounted for in all existing calls to u3l_log, but we move that into the next commit for readability's sake. |
||
---|---|---|
.github | ||
bin | ||
doc/spec | ||
extras | ||
nix | ||
pkg | ||
sh | ||
.gitattributes | ||
.gitignore | ||
.ignore | ||
.mailmap | ||
.stylish-haskell.yaml | ||
CONTRIBUTING.md | ||
default.nix | ||
LICENSE.txt | ||
MAINTAINERS.md | ||
Makefile | ||
README.md | ||
shell.nix |
Urbit
Urbit is a personal server stack built from scratch. It has an identity layer (Azimuth), virtual machine (Vere), and operating system (Arvo).
A running Urbit "ship" is designed to operate with other ships peer-to-peer. Urbit is a general-purpose, peer-to-peer computer and network.
This repository contains:
- The Arvo OS
- herb, a tool for Unix control of an Urbit ship
- Source code for Landscape's web interface
- Source code for the vere virtual machine.
For more on the identity layer, see Azimuth. To manage your Urbit identity, use Bridge.
Install
To install and run Urbit, please follow the instructions at urbit.org/using/install. You'll be on the live network in a few minutes.
If you're interested in Urbit development, keep reading.
Development
Urbit uses Nix to manage builds. On Linux and macOS you can install Nix via:
curl -L https://nixos.org/nix/install | sh
You can optionally setup Nix to pull build artefacts from the binary cache that continuous integration uses. This will improve build times and avoid unnecessary recompilations of common dependencies. Once Nix has been installed you can setup Cachix via:
nix-env -iA cachix -f https://cachix.org/api/v1/install
cachix use ares
The Makefile in the project's root directory contains useful phony targets for building, installing, testing, and so on. You can use it to avoid dealing with Nix explicitly.
To build the Urbit virtual machine binary, for example, use:
make build
The test suite can similarly be run via a simple:
make test
Note that some of the Makefile targets need access to pills tracked via git LFS, so you'll also need to have those available locally:
git lfs install
git lfs pull
Contributing
Contributions of any form are more than welcome! Please take a look at our contributing guidelines for details on our git practices, coding styles, how we manage issues, and so on.
For instructions on contributing to Landscape, see its guidelines.
You might also be interested in joining the urbit-dev mailing list.