How lingjie00/cli_settings works
Project type and purpose
• This is a personal “dotfiles” repository—an open-source tool for managing and bootstrapping a developer’s CLI environment.
• Purpose: store all configuration files for various terminal tools (Neovim, fish shell, tmux, Yabai, Alacritty, etc.), and provide install/uninstall scripts to symlink these configs into a fresh machine.
File structure
• Top-level config directory:
• .config/alacritty – terminal emulator
• .config/fish – shell config (with plugins & functions)
• .config/i3, i3blocks – Linux window manager
• .config/kitty – another terminal emulator
• .config/limelight, rofi, skhd, yabai – macOS window management
• .config/nvim – Neovim editor and plugins (Lua config)
• .config/qutebrowser, zathura, w3m – CLI browsers/viewers
• Root-level dotfiles: .vimrc, .zshrc, .tmux.conf, .gitconfig
• Install tooling: Makefile, install, uninstall, homebrew.sh, install_neovim.sh
• Project scripts for data-science: read_excel.py, nb_clean, Python requirements
• Metadata: pyproject.toml, read_excel_requirements.txt
README for additional insights
• Describes the four core tools managed: Neovim, fish shell, tmux, Yabai
• Setup flow:
1) git clone the repo
2) run ./install which creates symbolic links to ~
• Notes on Python/Jupyter and R workflows (Jupytext, RStudio server)
• SSH config snippet management
• Common editor commands and build recipes
• Version Control & Bootstrap Scripts
• Symlink Manager
• Config Targets (shell, editor, WM, terminal emulators)
• External Services
• Host OS / Terminal
• install → symlink creation → config pickup
• shell startup → conda init
• editor → LSP & plugin subsystems
• user commands → external services (SSH, Jupyter)
• Scripts/orchestration
• Configuration directories
• Runtime applications
• External services/hosts