Each page carries the logo of its main theme: 🖥️ the terminal session, 🏷️ environment variables, ⚡ doskey aliases, 🧰 applications, or 📦 senv as a whole when the page spans them all.
Documentation for senv, organized on the Diátaxis model. The discipline is simple: each page belongs to exactly one of the four categories below, and never mixes goals: a tutorial teaches, a how-to guide solves, a reference describes, an explanation clarifies.
Learning by doing: follow the steps in order, type what is shown, check what you see. Start here if senv is new to you.
- 📦 Your first senv
- 🧰 Install and use a tool on demand
- 🖥️ Give a project its own senv
- 📦 From zero on a team laptop
Recipes for a precise goal, for readers who already know the basics.
- 🧰 Add a program to prgs.list
- 🧰 Write an install hook
- 🧰 Reference an already-installed tool
- 📦 Create a team profile
- 📦 Build and publish a profile archive
- ⚡ Add a personal alias or environment variable
- 📦 Migrate HOME to a local drive
- 🏷️ Work behind a corporate proxy
- 🧰 Manage Python virtual environments
- 🖥️ Open project tabs in Windows Terminal
- 📦 Update senv and diagnose version drift
- 📦 Sanitize the history before publishing
- ⚡ Copy cached Teams chats to the clipboard
Exact, dry descriptions of commands, formats and conventions.
- 🖥️ Commands
- 🧰 prgs.list format
- 🧰 install_<profile>.list format
- 📦 Naming conventions
- 🏷️ Environment variables
- ⚡ Doskey aliases
- 🧰 Git configuration
- 🖥️ Exit codes
Background and reasoning: why senv is built the way it is.