When a tmux session is killed (e.g., via `tmux kill-session`), the
zshexit hook may not fire, leaving p10k worker and gitstatus daemon
processes orphaned (PPID=1). These orphaned processes hold PTY
resources indefinitely, eventually causing PTY exhaustion.
This fix adds parent process monitoring:
1. worker.zsh: Check PPID in main loop - exit if parent dies
2. gitstatus.plugin.zsh: Add background monitor that detects
PPID change to 1 (init/launchd) and triggers cleanup
The fix handles the case where shells are terminated without
proper cleanup (SIGKILL, tmux kill-session, etc.).
Fixes orphaned processes like:
- p10k.worker.*.fifo holders
- gitstatus.POWERLEVEL9K.*.fifo holders
- gitstatusd-darwin-arm64 daemons
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Updated `_p9k_prompt_aws_init` to include `AWS_SSO_PROFILE` in the condition for activating the AWS segment.
- Ensures compatibility with AWS SSO profiles in addition to other AWS environment variables.
44504a24 make: remove -Wall
8795883c Specify cmake generator in build file (#441)
3e08476b docs: the project is on life support
12e6a689 Add support to build e2k arch. (#432)
a952c3f6 bump version to v1.5.5
git-subtree-dir: gitstatus
git-subtree-split: 44504a24b1b999a4f56ff74c75b8215bdcadee1f
The preference for nerdfont-complete was necessitated by a bug
in Windows Terminal that has since been fixed.
This reverts commit b474978b2e.
wizard: prefer POWERLEVEL9K_MODE=nerdfont-complete over nerdfont-v3
See the reverted commit for details on the Windows Terminal bug.
This commit provides support for virtualenv-like pyenv.cfg configuration files, where the `prompt` value is a plain text rather than a quoted string.
Before the commit, `prompt = My custom prompt` would not match the regex, returning a fallback of the $VIRTUAL_ENV directory name.
After the commit, both venv-like `prompt = 'My custom prompt'` and virtualenv-like `prompt = My custom prompt` are supported.
Closes#2628