Skip to content

Fix/xdg shell paths - #92

Merged
capydev42 merged 4 commits into
mainfrom
fix/xdg-shell-paths
Oct 4, 2026
Merged

capydev42 merged 4 commits into
mainfrom
fix/xdg-shell-paths

Conversation

@capydev42

Copy link
Copy Markdown
Owner

No description provided.

…ntion

history_path() and config_path() hardcoded five paths that the shells themselves resolve through the
environment. Anyone who sets $XDG_CONFIG_HOME, $XDG_DATA_HOME or $ZDOTDIR got no history at all, and --worse
-- a silent non-install: ctrlr init wrote the integration into a file the shell never loads, Ctrl+R did nothing,
 and the next ctrlr init read the same wrong file back and reported "up to date". Measured against
fish 3.7.0, pwsh and zsh 5.9 rather than taken from the docs:
fish history  $XDG_DATA_HOME/fish/fish_history
fish config   $XDG_CONFIG_HOME/fish/config.fish
pwsh history  $XDG_DATA_HOME/powershell/PSReadLine/ConsoleHost_history.txt
pwsh profile  $XDG_CONFIG_HOME/powershell/Microsoft.PowerShell_profile.ps1
zsh config    $ZDOTDIR/.zshrc

With none of those set, all three shells answer with exactly the paths that were hardcoded, so this is a
superset and the default case cannot regress.
The "PowerShell hook writes a parseable record" step failed with "the hook wrote nothing". No code was broken;
the step was writing outside its ownsandbox.
@capydev42
capydev42 merged commit 041abac into main Oct 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant