even in the TUI we need proper syntax highlighting for source code and diffs and I don't know how markdown comments are handled, if they are rendered or showing source - I would prefer a pseudo-rendered. markdown look so that emphasies and titles and things like that show in the terminal. but for source and diffs definitely need syntax highlights
even in the TUI we need proper syntax highlighting for source code and diffs and I don't know how markdown comments are handled, if they are rendered or showing source - I would prefer a pseudo-rendered. markdown look so that emphasies and titles and things like that show in the terminal. but for source and diffs definitely need syntax highlights
hugo
added this to the first feature complete release milestone 2026-08-03 20:55:06 +00:00
hugo
added the bug label 2026-08-03 20:55:06 +00:00
Source-file previews now use Syntect's bundled grammars, selected by filename with first-line/shebang fallback; unknown text remains plain and legible.
Commit and pull-request unified diffs use the bundled diff grammar, giving metadata, hunks, additions, and deletions distinct syntax colors.
Home activity content and issue, pull-request, milestone, and comment text now use a Ratatui-native pseudo-rendered Markdown presentation for headings, emphasis, strong text, lists, links, inline code, and fenced blocks.
Existing work-item metadata line breaks are preserved through Markdown rendering.
Syntax output is cached by exact path/content so the TUI redraw loop does not repeatedly parse the same large file or diff.
TESTING.md now covers syntax, Markdown, fallback, and the current unconditional q behavior.
Color-capable interactive PTY against the configured server: verified a real commit diff emitted distinct truecolor context/addition styles
Opened TESTING.md through the live repository browser and verified filename-driven source syntax colors
Selected the Markdown implementation comment in live Home activity, scrolled its preview, and verified list structure plus inline-code styling
This is TUI-only, so no iPhone release build was performed as requested.
Implemented in `aafde7e`.
- Source-file previews now use Syntect's bundled grammars, selected by filename with first-line/shebang fallback; unknown text remains plain and legible.
- Commit and pull-request unified diffs use the bundled diff grammar, giving metadata, hunks, additions, and deletions distinct syntax colors.
- Home activity content and issue, pull-request, milestone, and comment text now use a Ratatui-native pseudo-rendered Markdown presentation for headings, emphasis, strong text, lists, links, inline code, and fenced blocks.
- Existing work-item metadata line breaks are preserved through Markdown rendering.
- Syntax output is cached by exact path/content so the TUI redraw loop does not repeatedly parse the same large file or diff.
- `TESTING.md` now covers syntax, Markdown, fallback, and the current unconditional `q` behavior.
Verification:
- `cargo fmt --all -- --check`
- `RUSTFLAGS="-D warnings" cargo check --workspace --all-targets`
- `cargo clippy --workspace --all-targets -- -D warnings`
- `cargo test --workspace` (46 tests)
- Color-capable interactive PTY against the configured server: verified a real commit diff emitted distinct truecolor context/addition styles
- Opened `TESTING.md` through the live repository browser and verified filename-driven source syntax colors
- Selected the Markdown implementation comment in live Home activity, scrolled its preview, and verified list structure plus inline-code styling
This is TUI-only, so no iPhone release build was performed as requested.
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.
even in the TUI we need proper syntax highlighting for source code and diffs and I don't know how markdown comments are handled, if they are rendered or showing source - I would prefer a pseudo-rendered. markdown look so that emphasies and titles and things like that show in the terminal. but for source and diffs definitely need syntax highlights
Implemented in
aafde7e.TESTING.mdnow covers syntax, Markdown, fallback, and the current unconditionalqbehavior.Verification:
cargo fmt --all -- --checkRUSTFLAGS="-D warnings" cargo check --workspace --all-targetscargo clippy --workspace --all-targets -- -D warningscargo test --workspace(46 tests)TESTING.mdthrough the live repository browser and verified filename-driven source syntax colorsThis is TUI-only, so no iPhone release build was performed as requested.