Executer, rename sg_parser_unhandled_regex

[theludovyc]

Since Parser was split in two, it is Executer send this signal.

So I think we can rename it in "sg_custom_regex" ?

[Jeremi360]

Since Parser was split in two, it is Executer send this signal.

So I think we can rename it in "sg_custom_regex" ?

Yes, I think this is a good name and previous name felt me as being too long.
And I think we should name function that adds regex add_custom_regex() then.

[theludovyc]

Also agree for add_custom_regex()

[theludovyc]

Maybe add_custom_regex_to_parse(...) is better ?

[Jeremi360]

Maybe add_custom_regex_to_parse(...) is better ?

@theludovyc this is really long name for func, and I don't like it.
And to make this clear we can just comments so it automatically clearly it out in docs.
On the other hand your in proposition is func name self explanatory.

[theludovyc]

I am afraid that add_custom_regex() is too ambiguous. But yes with comments it can be good :)

[Jeremi360]

I am afraid that add_custom_regex() is too ambiguous. But yes with comments it can be good :)

I think it would be ambiguous only if we had some other func with similar name or functionality

[theludovyc]

I see what you mean. So let's go for add_custom_regex() :)