/e: Add match length to results

[kazarmy]

Your checklist for this pull request

• I've read the guidelines for contributing to this repository.
• I made sure to follow the project's coding style.
• I've documented every RZ_API function and struct this PR changes.
• I've added tests that prove my changes are effective (required for changes to RZ_API).
• I've updated the Rizin book with the relevant information (if needed).

Detailed description

This pr adds the match length to /e regex search results since it can be different for different hits.

This pr is currently just a reminder that regex search results are incomplete without the match length. Once #4762 lands (which has the match length displayed for apparently all searches), this pr can be closed.

Test plan

All builds are green.

Closing issues

...

[notxvilka]

I like this change. But please wait for @Rot127 review

[Rot127]

It is addressed in the search PR as well. At least it saves the number of bytes of the hit (not number of characters). Is this a proper replacement? Let me just investigate some timeout issue and then I can open the new one for review.

[kazarmy]

At least it saves the number of bytes of the hit (not number of characters).

Regarding this pr, the match length shown is set here:

rizin/librz/search/regexp.c

Lines 38 to 39 in e0a69df

	RzRegexMatch *m = *it;
	kw->keyword_length = m->len; // For a regex search, the keyword can be of variable length

and m->len is from PCRE2 and is in bytes (according to this header comment):

rizin/librz/include/rz_util/rz_regex.h

Line 53 in e0a69df

RzRegexSize len; ///< Length of match in bytes.

---

Is this a proper replacement?

Not sure what you mean by this, but I'm not planning on working on counting code points, grapheme clusters etc. in the near future.

---

Let me just investigate some timeout issue and then I can open the new one for review.

If the search PR lands soon, then this pr is no longer necessary. If it doesn't, then I would like to merge this pr by the end of this week.

[Rot127]

Not sure what you mean by this, but I'm not planning on working on counting code points, grapheme clusters etc. in the near future.

Counting code points can be easily extended after the search PR is done. Because each detected string counts them already. They are just not applied to the RzSearchHit. Currently it stores only bytes as you did here as well.

If the search PR lands soon, then this pr is no longer necessary. If it doesn't, then I would like to merge this pr by the end of this week.

Ok for me.

[kazarmy]

Closing due to #4919