Alright, this is now fixed with the latest push I just made. Also reflected 
in the docs. Thanks for spotting that flaw :)

Reply via email to