jameseidson / brutus

A terminal multiplexer.

Brutus

Brutus is a terminal multiplexer.

Building

Brutus uses the Bazel build system.

bazel build //src:brutus

Will produce a binary at bazel-bin/src/brutus.

If you have a system installation of Cap'n Proto, you can tell bazel to use it by adding the flag --//:use-system-capnp=true. Otherwise, the Cap'n Proto compiler will be built from source (this can take some time).

Development

Editor Setup

Getting language servers to work well with Bazel and generated code requires some setup.

1. Make sure you're using rust-analyzer for rust and gopls for go.

2. Run gen-project-for-rust-analyzer to generate a rust-project.json in the repository root.

   bazel run //:gen-project-for-rust-analyzer
   

   This file supplies Bazel build information to rust-analyzer and will be automatically discovered. Documentation can be found here.

3. Apply the following language server configurations as appropriate for your editor. The scripts used in these configurations assume you have the capnp binary on your $PATH.

   "rust-analyzer.check.overrideCommand": ["scripts/rustanalyzer-bazel-bridge.sh"],
   

   "gopls.env": {
     "GOPACKAGESDRIVER": "<ABSOLUTE PATH TO REPOSITORY>/scripts/gopls-bazel-bridge.sh",
   }
   

   • VS Code is already configured via .vscode/settings.json.
   • Neovim is already configured via .nvim.lua. This requires vim.opt.exrc = true in your global Neovim configuration.
   • Zed is already configured via .zed/settings.json.

Workflows

Update Bazel dependencies from src/server/Cargo.toml:

CARGO_BAZEL_REPIN=1 bazel sync --only=crate_index

Update Bazel dependencies from src/client/go.mod:

gazelle update-repos -from_file=src/client/go.mod