Extend string search

[Rot127]

Is your feature request related to a problem? Please describe.

The string search could use some more extensions and fine-tuning options for the user.

Describe the solution you'd like

• Allow to define "printable" and "non-printable" characters.
• Count the grapheme length of a string and provide it in the search hit.

Describe alternatives you've considered

None.

Additional context

Left over from: https://github.com/rizinorg/rizin/pull/4919

[notxvilka]

Please elaborate more on how you imagine defining printable and non-printable characters.

[Rot127]

Some instructions stop printing at "non-printable" characters. Those are of course invalid unicode code points. But for some commands those are also tab, newline or color code escape sequences. What is deemed "un-printable" is depending on the use case (e.g. color escape sequences).

So these should be user defined by some option which takes a list of unicode code points.