Skip to content
nabinnoPublic

About

nabinno's zsh, emacs and etc config files, also devenv provisioner of good stuffs.

Topics

Resources

Stars

5 stars

Watchers

1 watching

Forks

Latest commit

 

History

979 Commits

Folders and files

Repository files navigation

nabinno's dotfiles

Personal dotfiles repository for Unix-like systems with modular configurations for Zsh and Emacs development environments.

[1]

Features

  • Modular Emacs Configuration: 100+ feature-specific modules using modern leaf package manager
  • Intelligent Zsh Functions: Autoloaded functions with Go utilities for complex shell operations
  • Cross-Platform Support: OS detection and platform-specific initialization
  • Development Tools Integration: LSP, Git workflows, language-specific configurations
  • Claude Code Integration: AI-assisted development with Emacs integration

Quick Start

Prerequisites

  1. Install Zsh
  2. Connect to GitHub with SSH

Installation

sh -c "$(curl -fsSL https://raw.github.com/nabinno/dotfiles/master/install.sh)"

Setup

Antigravity CLI (Linux / macOS):

The Zsh init-llm module installs agy when it is missing, using the official installer, and adds ~/.local/bin to PATH. The installer verifies the release checksum; Antigravity CLI manages its own updates.

Run agy in your project directory and follow the first-run Google sign-in instructions. Authentication state and session history stay local and are not included in this repository.

This setup uses Antigravity CLI in place of Gemini CLI.

Windows Claude Code (Pro / Bedrock):

The Windows CMD launchers and their shared PowerShell script are stored under .win32/AppData/Roaming/. Install them from the checkout in Windows PowerShell:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .win32\install-claude.ps1

Requires an existing %APPDATA%\npm\claude.cmd installation, Windows PowerShell, and %APPDATA%\npm on PATH. Existing launcher files are backed up when changed. In Windows CMD:

claude-pro
claude-bedrock -Profile your-aws-profile -Region ap-northeast-1

Pro and Bedrock use separate configuration directories: %APPDATA%\claude-profiles\pro and %APPDATA%\claude-profiles\bedrock. Sign in to Pro and configure AWS authentication locally as needed. The launcher clears inherited Anthropic/provider overrides; Bedrock also clears direct AWS credentials and selects the supplied AWS profile and region. Additional Claude arguments are forwarded by launch.ps1. Credentials, profile settings, and session history are not included in this repository.

WSL Claude Code (Pro / Bedrock):

.local/bin/claude-profile is a standalone Bash launcher for use before wiring up aliases in ~/.zsh.d/init.zsh. Run it directly from the checkout:

./.local/bin/claude-profile pro
./.local/bin/claude-profile bedrock --profile InfrastructureLLM --region ap-northeast-1
./.local/bin/claude-profile pro -- --resume

It runs the WSL claude executable on PATH, forwarding arguments and its exit status. CLAUDE_PROFILE_BIN can specify an explicit executable path. It clears inherited Anthropic/provider overrides and uses ~/.claude-pro or ~/.claude-bedrock as CLAUDE_CONFIG_DIR. Pro may require a separate login; existing ~/.claude settings and sessions are not copied. Bedrock requires an explicit AWS profile and region, and clears direct AWS credentials in the child process. Optional CLAUDE_BEDROCK_MODEL and CLAUDE_BEDROCK_SMALL_FAST_MODEL set Bedrock model overrides after clearing inherited variables.

To install just the launcher:

install -Dm755 .local/bin/claude-profile "$HOME/.local/bin/claude-profile"

Future init.zsh alias wiring (not applied automatically):

alias claude='$HOME/.local/bin/claude-profile bedrock --profile InfrastructureLLM --region ap-northeast-1 --'
alias ccpro='$HOME/.local/bin/claude-profile pro --'

The correct variable is CLAUDE_CONFIG_DIR (not CLAUDE_CONFI_DIR). The launcher runs as a separate process and leaves the parent shell environment unchanged.

WSL Networking:

On WSL, install.sh applies .win32/.wslconfig to the Windows user profile (%USERPROFILE%\.wslconfig). It sets [wsl2] networkingMode=mirrored, preserving other settings and backing up an existing file before changing it. This requires Windows 11 22H2 or later with a supported WSL version and allows WSL to reach Windows services, including Chrome CDP, through 127.0.0.1.

To apply just this configuration from an existing checkout:

bash .win32/install-wsl.sh

Save your work, run wsl --shutdown in Windows PowerShell, and reopen WSL to activate the change. The installer does not stop WSL automatically.

Connect to your running Windows Chrome:

Shared agent skills and the Chrome CDP helper live in the public nabinno/agent-skills repository (MIT). This repository does not ship the helper. The file is agent-browser-current-browser/scripts/cdp.

ghq get nabinno/agent-skills
~/.ghq.d/src/github.com/nabinno/agent-skills/scripts/sync.sh
mkdir -p "$HOME/.local/bin"
ln -sfn ~/.ghq.d/src/github.com/nabinno/agent-skills/agent-browser-current-browser/scripts/cdp "$HOME/.local/bin/cdp"

sync.sh links each skill into the Claude Code, Codex, Grok, Antigravity, and .agents skill directories. Run it again after a new skill is added.

Scheduled agent skills (WSL systemd user timers):

The units in .config/systemd/user/ run three daily skills independently of interactive sessions: Claude Code health-news-digest at 09:03 JST and gmail-inbox-cleanup at 09:30 JST, then Codex hatena-hotentry-bookmark at 09:45 JST. They are not enabled by install.sh; install the files and enable the timers explicitly:

for file in .local/bin/claude-cron-* .local/bin/codex-hotentry-*; do
  install -Dm755 "$file" "$HOME/$file"
done
for file in .config/systemd/user/*; do
  install -Dm644 "$file" "$HOME/$file"
done
systemctl --user daemon-reload
systemctl --user enable --now health-news-digest.timer gmail-inbox-cleanup.timer hatena-hotentry-bookmark.timer

The Hatena job requires the existing Windows Chrome profile nabinno, its cb-bridge, remote debugging, and a Hatena login. Claude and Codex CLI sign-in must also be valid. These unattended jobs run with broad CLI permissions; review their scripts and service files before enabling them. Check schedules with systemctl --user list-timers --all and logs under ~/.claude/cron-logs/ and ~/.codex/cron-logs/. Run loginctl show-user "$USER" -p Linger to check whether user timers stay active after the last WSL login exits.

Zsh Environment:

exec zsh -l

Emacs Environment:

emacs --debug-init -nw

Architecture

Configuration Structure

  • Root Level: Core dotfiles (.zshrc, .gitconfig, .screenrc, etc.)
  • .emacs.d/: Modular Emacs configuration with init system
  • .zsh.d/function/: Zsh autoload functions with Go-based utilities

Key Components

  • Emacs: Uses leaf package manager with 100+ feature modules
  • Zsh Functions: Autoloaded via FPATH with platform detection
  • Go Utilities: Complex shell operations in .zsh.d/function/
  • Installation: Clones to ~/.local/dotfiles and copies files to $HOME

Environment Variables

  • DOTFILES_PATH: Automatically set (via ghq or ~/.local/dotfiles)
  • FPATH: Extended for custom function autoloading

Development

Testing Configuration

# Test Emacs configuration
emacs --debug-init

# Test Zsh functions
exec zsh -l

# Test Go utilities
cd .zsh.d/function && go run .

Zsh Startup Diagnostics

Startup messages and per-module timings are disabled by default. To show them for one shell, run ZSH_INIT_VERBOSE=1 zsh -i. Timings use Zsh's zsh/datetime module rather than spawning date and bc for each module. The active settings in $HOME/.zshrc and $HOME/.zprofile are copied files; keep them in sync with the corresponding repository settings when editing them.

Optional Docker Compose/Machine, OCaml, FastCGI, legacy PowerShell, dnsmasq provisioning, and the Ruby provisioning helper no longer run installation checks on every startup. Run the corresponding get-* functions explicitly; ZSH_AUTO_INSTALL=1 zsh -i restores these legacy startup checks (and may install packages or change system configuration). Installed tools, shell functions, completion, and the Windows PowerShell profile setup still load normally.

Adding New Configurations

  1. Emacs: Add init-feature.el to .emacs.d/lisp/
  2. Zsh: Add function to .zsh.d/function/ and call via require in .zshrc
  3. Go: Extend utilities in .zsh.d/function/ directory

License

MIT

Epilogue

A whale!
Down it goes, and more, and more
Up goes its tail!

-Buson Yosa

[1] "A selection of mallets, bores and files" (1700-1799, Robert Benard after Jacques-Raymond Lucotte) credited in Wellcome Collection is licensed by CC 4.0 BY ↩

About

nabinno's zsh, emacs and etc config files, also devenv provisioner of good stuffs.

Topics

Resources

Stars

5 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages