stumpwm/mahogany

Description and use

**Brief summary (2‑3 sentences)**
Mahogany is an experimental Wayland compositor written in Common Lisp that mimics the tiling‑window‑manager experience of StumpWM. It targets users who already enjoy StumpWM’s keyboard‑driven workflow and want a similar environment on modern Wayland systems. The project is actively maintained (last commit 2026‑05‑10) and has attracted modest community interest (≈ 355 stars).

**Value proposition**

• **Familiar workflow**: Developers and power‑users who have built a StumpWM‑centric workflow can transition to Wayland without relearning window‑management concepts.
• **Lisp‑centric extensibility**: Because the compositor is written in Common Lisp, it can be customized and extended using the same language and idioms that StumpWM users already employ.
• **Lightweight prototype platform**: Its minimal feature set makes it a good sandbox for experimenting with new tiling concepts or Wayland integrations before committing to a larger compositor.

**Practical adoption path**

1. **Evaluate the README and source** – Verify that the documented configuration model aligns with your existing StumpWM setup.
2. **Build & test in an isolated environment** – Clone the repo, compile with SBCL (or your preferred Lisp implementation), and run Mahogany on a dedicated Wayland session (e.g., via weston or a nested compositor).
3. **Port your StumpWM config** – Translate keybindings, hooks, and custom scripts into Mahogany’s configuration DSL; this may require modest Lisp refactoring.
4. **Integrate with your stack** – Add Mahogany to your system’s session manager (e.g., a systemd service or ~/.xinitrc‑style script) and validate interaction with essential applications (terminal, editor, browser).
5. **Iterate and document** – Record any missing features or bugs; consider contributing patches upstream if they are broadly useful.

**Production readiness**

• **Maturity**: Medium. The project is actively updated and has a reasonable star count, but the ecosystem is small and documentation is sparse.
• **Risk**: Integration signals are limited; you’ll need to manually verify dependency compatibility (SBCL version, Wayland libraries) and assess maintenance commitments.
• **Recommended use**: Suitable for internal tools, prototypes, or personal workstations where the benefits of a StumpWM‑style Wayland compositor outweigh the overhead of a custom setup. For critical production environments, perform a thorough stability and security audit, and be prepared to maintain a fork or contribute fixes as needed.

Use in a workflow

stumpwm/mahogany may be useful when its README and activity match a concrete workflow.

Limitations and review notes

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.