you missed the point, obviously the regex returns a smaller value: 1 which is plenty short enough for noop. The point is the need for such a work-around as noop can't handle a line length that the regex identifier can. I'll have to do some testing with capture groups, maybe /(.)/g so the return is a match result larger than 1 and compare this to the actual line length in question to see where they differ in size-of string processed.
If this indeed the case, does this hold true for any and all identifiers? that they're automatically chomping a value to the maximum line length? Why can't noop follow this behavior as well? Thought noop was for when you need to do nothing with a return, hence no operation, much like linux/unix you'd cat to /dev/null for instance.
