rootiest/fish-config
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(docs): regenerate man page, HTML docs, and wiki

Browse Source
This commit is contained in:
Gitea Actions
2026-06-19 06:58:05 +00:00
parent cf8dc8d7e1
commit a76e4de605
7 changed files with 123 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/html/11-7-customization.html
+15 -5
View File
@@ -638,15 +638,25 @@ Catppuccin Mocha theme First shell only Applies theme via fish_config
paru wrapper Every startup Writes ~/.local/bin/paru wrapper
yay wrapper Every startup Writes ~/.local/bin/yay wrapper
Python venv activation On every cd Sources .venv/bin/activate.fish
WakaTime command hook On every command Reports to WakaTime API</code></pre>
WakaTime command hook On every command Reports to WakaTime API
Auto-pull fast-forward On entering a repo Background ff-only git pull</code></pre>
<p>When C2 is disabled: no Fisher install, no theme application, no
paru/yay wrapper generation, no automatic venv activation, and no
WakaTime reporting. The first-run completion marker
(__fish_config_first_run_complete) is still set so the init does not
re-run on subsequent shells.</p>
paru/yay wrapper generation, no automatic venv activation, no WakaTime
reporting, and no auto-pull (the PWD handler is never registered). The
first-run completion marker (__fish_config_first_run_complete) is still
set so the init does not re-run on subsequent shells.</p>
<p>Python venv activation fires on every directory change. If a
directory uses direnv (.envrc present), direnv takes priority and
auto-venv is skipped for that directory.</p>
<p>Auto-pull fast-forwards opted-in repositories in the background when
you cd into them. The fish-config repo is always covered; other repos
are added with the <code>auto-pull</code> command (see its entry in the
functions reference). It only ever fast-forwards a clean repo whose
branch has an upstream — never rebases, merges, or overwrites work — so
it is a no-op on dirty trees, divergent branches, or repos without a
remote. The handler fires once per repo entry (not on every
sub-directory cd). The registry is machine-local at
~/.config/.user-dots/fish/auto-pull.list and is never committed.</p>
<h4 data-number="11.5.1.3" id="c3--key-and-environment-overrides">C3 —
Key and Environment Overrides</h4>
<p>These change fundamental shell behavior: how keys work, which pager