austindloar/dev-env

Purpose and Scope

This is a personal Unix desktop/developer-environment configuration repository. It centralizes shell, terminal, editor, multiplexer, SSH, Git, and Sway window-manager settings, plus launcher-style files for running selected applications.

Primary Entry Points

• dev-env appears to be the top-level environment bootstrap or development entry point.

• run is the likely general execution wrapper.

• Application-specific launch surfaces are under runs/, including runs/firefox, runs/ghostty, runs/neovim, runs/sway, runs/tmux, and runs/zsh.

• Shell startup is rooted at .zshrc, with prompt behavior in .p10k.zsh.

Shell and Session Layer

The interactive environment is Zsh-based:

• .zshrc defines the shell session configuration.

• .p10k.zsh supplies Powerlevel10k prompt configuration.

• .local/scripts/ready-tmux and .ready-tmux indicate a readiness/session handoff mechanism around tmux.

This layer is the likely common initialization boundary before editor, terminal, and multiplexer workflows begin.

Terminal and Multiplexer Workflow

Terminal and terminal-session behavior is configured separately:

• Ghostty: .config/ghostty/config.ghostty

• tmux: .config/tmux/tmux.conf

• Session selection/creation helper: .local/scripts/tmux-sessionizer

• Runtime launch target: runs/ghostty and runs/tmux

The intended flow is likely terminal → Zsh → tmux, with sessionizer tooling selecting project or working-directory sessions.

Neovim Configuration Architecture

Neovim is organized as a Lua configuration module rather than a monolithic init file:

• Root entry: .config/nvim/init.lua

• Local module root: .config/nvim/lua/austin/init.lua

• Base settings: .config/nvim/lua/austin/set.lua

• Plugin/bootstrap initialization: .config/nvim/lua/austin/lazy_init.lua

• Feature modules: .config/nvim/lua/austin/lazy/lsp.lua, .config/nvim/lua/austin/lazy/conform.lua, .config/nvim/lua/austin/lazy/telescope.lua

This separates editor startup, core options, plugin loading, language-server integration, formatting, and search/navigation capabilities.

Desktop and System Boundaries

The graphical desktop boundary is Sway:

• .config/sway/config

• Runtime launcher: runs/sway

Terminal GUI behavior is Ghostty-specific, while Sway owns window-management concerns. The repository also includes authentication/remote-access and source-control client configuration:

• .ssh/config

• .gitconfig

Runtime Packaging/Launch Boundary

The runs/ directory is the repository’s runtime abstraction layer. It contains executable or wrapper targets for user-facing programs and a shared library area:

• runs/libs

• runs/ly

• runs/firefox

• runs/neovim

This boundary likely decouples machine setup and application invocation from the underlying dotfile locations, allowing a consistent way to start desktop and development tools.