Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Readable C0 Control Characters in Hexdump #84

Open
rpetersonfujitsu opened this issue Jun 30, 2022 · 0 comments
Open

Request: Readable C0 Control Characters in Hexdump #84

rpetersonfujitsu opened this issue Jun 30, 2022 · 0 comments

Comments

@rpetersonfujitsu
Copy link

I would like to be able to distinguish between the non-printable characters and have them display as something other than dots.

To improve readability / recognition could you either…

A) Display the C0 control characters (range:0-32,127) as the Unicode "control pictures" characters

B) Print the control character itself.
In this case, if the font is Cascadia Code and the ss20 stylistic set enabled,
then those control characters will be displayed as the control pictures.

For example:
https://github.com/microsoft/cascadia-code/releases/tag/v2102.03

Perhaps there are technical limitations, but I'd really like to be able to know what character / value I'm looking at WITHOUT using the data inspector. (Too many bytes; takes too long.)I (also) would like to be able to distinguish between the non-printable characters and have them display as something other than dots.

To improve readability / recognition could you either…

A) Display the C0 control characters (range:0-32,127) as the Unicode "control pictures" characters

B) Print the control character itself.
In this case, if the font is Cascadia Code and the ss20 stylistic set enabled,
then those control characters will be displayed as the control pictures.

For example:
https://github.com/microsoft/cascadia-code/releases/tag/v2102.03

Perhaps there are technical limitations, but I'd really like to be able to know what character / value I'm looking at WITHOUT using the data inspector. (Too many bytes; takes too long.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant