Repository navigation
fix: keep Tk and the usage bars legible on any status bar - #69
Merged
Merged
Conversation
Two rendering fixes for windows where the defaults did not fit. Remote windows default to block bars. Since 2.5.22 claudemeter runs on the remote host in a Remote-SSH, WSL or container window, so process.platform names that host while the client draws the glyphs. A Linux remote viewed from Windows picked barCircle and rendered the uneven circles the Windows default exists to avoid. VS Code does not expose the client OS, so a remote window now defaults to barLight, which renders on every platform. An explicit statusBar.usageFormat still wins. colors.rotLight and colors.rotDeep now set the Tk rot gradient. Above 400K on a large window Tk ramps from near-white to deep navy #163a63, which disappears into a dark blue status bar, so the gauge looks disabled just as it starts to warn. The ramp anchors were hard-coded; the two existing settings now override its start and end. Co-Authored-By: Claude Opus 5.5 <[email protected]>
hypersec-ci-bot Bot
pushed a commit
that referenced
this pull request
Oct 19, 2026
## [2.5.23](v2.5.22...v2.5.23) (2026-10-19) ### Bug Fixes * keep Tk and the usage bars legible on any status bar ([#69](#69)) ([4f4de4d](4f4de4d)), closes [#163a63](https://github.com/hyperi-io/claudemeter/issues/163a63)
|
This issue has been resolved in version 2.5.23 The release is available on GitHub release |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
barCircle, which Windows status-bar fonts render as uneven circles. VS Code does not expose the client OS, so a remote window now defaults tobarLight. An explicitstatusBar.usageFormatstill wins.colors.rotLight/colors.rotDeepnow set the Tk rot gradient. Above 400K on a large window Tk ramps from near-white to deep navy#163a63, which disappears into a dark blue status bar, so the gauge looks disabled as it starts to warn. The two existing settings now override the start and end of the ramp. Unset, the ramp is unchanged.Test plan
npx vitest run: 963 passed, 1 skipped (Linux)statusBarRender.test.js; ramp defaults, both overrides, one override, malformed value incolorResolver.test.jseslint src testsclean▓░barscolors.rotDeepset, Tk past 400K on a 1M window ramps toward that colour🤖 Generated with Claude Code