New ambigous_width=1 argument #172
Merged
+476
−56
Conversation
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
jquast
force-pushed
the
jq/ambiguous-width
branch
from
196f7ea to
46be512
Compare
jquast
added a commit
to jquast/blessed
that referenced
this pull request
Jan 19, 2026
This is a supporting method for the wcwidth library documentation in PR jquast/wcwidth#172 I don't want the "wcwidth" library to be bogged down with terminal support, but I need a place to document, "this is how you can detect ambiguous wide support", for forthcoming ambiguous_wide=2 argument, in popular use by CJK folk.
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.
Most importantly, adds ambiguous_width=1 argument to all functions, may be set to '2' for CJK context.
in bin/update-tables.py:
Documentation suggests to see source code of, or to use the blessed library method,
detect_ambiguous_width()to determine the argument,