functions/logs.fish: Scrollback logs now open in ov with a per-invocation temp config that sets SectionLine.Background and SectionLine.Foreground to empty strings. This prevents ov from overriding the ANSI colors embedded in the starship prompt when it is pinned as a sticky section header — the prompt now renders with its original colors instead of ov's default slateblue background.
config.fish: Added a second return sentinel inside the if status is-interactive block (in addition to the existing one at EOF) to guard against tool-injected init lines that target the interactive scope specifically.
README.md: Updated the > [!IMPORTANT] callout to document both return sentinels.
Manual Verification
Open a scrollback log via logs → select a scrollback entry → press Enter
Confirm the sticky prompt header at the top of the ov viewer shows the original starship colors (bright green segment, rainbow, etc.) with no purple/dark background override
Scroll through the log and confirm section headers update correctly as you navigate between prompts
Open a paru or yay log and confirm its colored section headers are unchanged (slateblue/colored background still present)
Start a fresh interactive shell and confirm the prompt renders normally (both return sentinels are present but neither affects interactive startup)
## Summary
- **`functions/logs.fish`**: Scrollback logs now open in `ov` with a per-invocation temp config that sets `SectionLine.Background` and `SectionLine.Foreground` to empty strings. This prevents ov from overriding the ANSI colors embedded in the starship prompt when it is pinned as a sticky section header — the prompt now renders with its original colors instead of ov's default slateblue background.
- **`config.fish`**: Added a second `return` sentinel inside the `if status is-interactive` block (in addition to the existing one at EOF) to guard against tool-injected init lines that target the interactive scope specifically.
- **`README.md`**: Updated the `> [!IMPORTANT]` callout to document both return sentinels.
## Manual Verification
- [x] Open a scrollback log via `logs` → select a scrollback entry → press `Enter`
- [x] Confirm the sticky prompt header at the top of the ov viewer shows the **original starship colors** (bright green segment, rainbow, etc.) with no purple/dark background override
- [x] Scroll through the log and confirm section headers update correctly as you navigate between prompts
- [x] Open a paru or yay log and confirm its colored section headers are **unchanged** (slateblue/colored background still present)
- [x] Start a fresh interactive shell and confirm the prompt renders normally (both `return` sentinels are present but neither affects interactive startup)
Use a per-invocation temp ov config to set SectionLine Background/Foreground
to empty strings, preventing ov from overriding the ANSI colors embedded in
the starship prompt when it is pinned as a sticky section header.
Also adds a second return sentinel inside the interactive block of config.fish
to guard against tool-injected init lines that target the inner scope, and
updates README accordingly.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
functions/logs.fish: Scrollback logs now open inovwith a per-invocation temp config that setsSectionLine.BackgroundandSectionLine.Foregroundto empty strings. This prevents ov from overriding the ANSI colors embedded in the starship prompt when it is pinned as a sticky section header — the prompt now renders with its original colors instead of ov's default slateblue background.config.fish: Added a secondreturnsentinel inside theif status is-interactiveblock (in addition to the existing one at EOF) to guard against tool-injected init lines that target the interactive scope specifically.README.md: Updated the> [!IMPORTANT]callout to document both return sentinels.Manual Verification
logs→ select a scrollback entry → pressEnterreturnsentinels are present but neither affects interactive startup)