Go strings integration tasks

[mr-tz]

Tasks

Preview Give feedback

1. render \t vs. tab (strings.exe does the latter)
2. Go build ID string split into multiple lines, see image1?
3. strings split, see image 2?

image 1

image 2

[mr-tz]

For task 2 and 3 I think the console setting (width) results in the added new lines...

[Arker123]

For task 2 and 3 I think the console setting (width) results in the added new lines...

So, to address this, should I increase the width setting?

[williballenthin]

if the case is what @mr-tz mentioned, then its rich deciding to wrap the string across multiple lines, based on the current width of the terminal. we should decide what the behavior should be. i think two reasonable options include:

• don't wrap, and truncate strings at the end of the terminal, though this potentially makes it difficult to review the complete string contents
• don't wrap, and let the terminal wrap long lines, as strings.exe does. i dont think blindly changing the console width is the right fix here, since i can trivially construct a string that's longer than whatever width you pick. instead, we should read more about rich and how to change the behavior.

[Arker123]

render \t vs. tab (strings.exe does the latter)

Is this feature already in place?

[Arker123]

Go build ID string split into multiple lines, see image1?

Could we utilize the enrich library for this task?

Enriched extends [rich](https://pypi.org/project/rich/) library functionality with a set of changes that were not accepted to rich itself.

Reference:- https://github.com/pycontribs/enrich

[mr-tz]

render \t vs. tab (strings.exe does the latter)

Is this feature already in place?

we need to decide which behavior we want and make sure it's consistent across the output functions

is that the case currently?

[Arker123]

is that the case currently?

Yes, that is currently the case.

[mr-tz]

Ok, then we only have the wrapping issue left to fix.

[mr-tz]

closed via #861