fix: wrap long CLI paths in table output#24
Open
jottakka wants to merge 1 commit into
Open
Conversation
99cf4a0 to
aaeca96
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
aaeca96 to
c0e4b77
Compare
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
CLI tables now wrap long path cells instead of truncating them with Rich's ellipsis overflow. This keeps long Windows paths distinguishable in narrow terminals and avoids emitting the Unicode ellipsis that can render as corrupted text in some PowerShell/Codex sessions.
The fix covers
libr search,libr list,libr docs,libr docs list, andlibr docs search. The existing--format pathsmode remains the full copyable-path output for search results.Testing
uv run --extra dev pytest tests/test_cli.pyuv run --extra dev pytestPathtables