Skip to content

fix(fish): parse the format fish actually writes - #90

Merged
capydev42 merged 1 commit into
mainfrom
fix/fish-history
Sep 25, 2026
Merged

capydev42 merged 1 commit into
mainfrom
fix/fish-history

Conversation

@capydev42

Copy link
Copy Markdown
Owner

parse_fish_line expected cmd "foo" / when 1700000000 without colons.fish writes YAML-shaped entries: - cmd:
, when: , and an optional indented paths: block. So - cmd: git status hit the leading dash,
went to parse_fish_yaml_line, which split on '\n' over a single line,found no cmd prefix and returned None.
Every fish user saw an empty history. The module's tests were green because all of them asserted the invented
format.

parse_fish_line expected cmd "foo" / when 1700000000 without colons.fish writes YAML-shaped entries: - cmd:
<raw text>,   when: <unix>, and an optional indented paths: block. So - cmd: git status hit the leading dash,
went to parse_fish_yaml_line, which split on '\n' over a single line,found no cmd  prefix and returned None.
Every fish user saw an empty history. The module's tests were green because all of them asserted the invented
format.
@capydev42
capydev42 merged commit e185266 into main Sep 25, 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