Andreas Hrubak

using shell command lines you have to pay attention to meta chars (lookup shell meta/magic/special char). relation signs are special, so you have to double quote it: `cloudflare -E "youremail@address"...

much appreciation for your effort but it's an out of scope for me. usually i'd do this kind of parameter pass by wrapper scripts. i even regret `-E` and `-T`...

@xpliz what does `cf show zones` produce?

IMO the mentioned regex is OK. ``$zone`` is ``domain.co.uk``, regex matches for ``domain.co.uk`` alone and ``anything.domain.co.uk`` capturing empty string and ``anything`` respectively. Btw, your regex does not allow ``domain.co.uk`` just...

the pipe char is there to match even a zero prefix before "bar.net", so either "something and a dot" or nothing before the domain name. > Is this expression **^((.*)\.|**...

the pipe char is there to match even a zero prefix before "bar.net", so either "something and a dot or an empty > Is this expression **^((.*)\.|** in **findout_record()** supposed...

it's considerably slow on a 360 kB file too.

hi guys. i'm strongly against the idea that `ungron` would have the responsibility to ignore escape codes. it's a good practice to let the _output producer_ component to check who...

@rjmunro ye sorry i did not compare the current codebase to the version of the age of this ticket, just checked that the ticket is open. i'm glad that gron...

i agree ungron may indicate where the parse error happened by a snippet with escaped control chars in it - if you mean it.