On 2016-12-23 02:56 , Daniel J. Luke wrote:
On Dec 22, 2016, at 1:50 AM, Andrea D'Amore wrote:
Thanks for the quick patch, by the way 'lint' verb doesn't catch an
invalid command as in this case, is that on purpose?
lint only catches a subset of errors. I'm sure a patch to verify that all
po
On Dec 22, 2016, at 1:50 AM, Andrea D'Amore wrote:
> Thanks for the quick patch, by the way 'lint' verb doesn't catch an
> invalid command as in this case, is that on purpose?
lint only catches a subset of errors. I'm sure a patch to verify that all
ports/subports index properly would be welcome
On 21 December 2016 at 21:54, Marko Käning wrote:
> On 21 Dec 2016, at 21:51 , Daniel J. Luke wrote:
>> yep, I just pushed a fix for the missing \ in the description in the subport.
> :) Just wanted to push that fix myself, but you beat me there!
Be honest, you guys are just scared of my push-fu
On 21 Dec 2016, at 21:51 , Daniel J. Luke wrote:
> yep, I just pushed a fix for the missing \ in the description in the subport.
:) Just wanted to push that fix myself, but you beat me there!
On Dec 21, 2016, at 3:47 PM, Marko Käning wrote:
> I just saw this when running portindex on my El Capitan VM:
>
> Failed to parse file shells/xonsh/Portfile with subport 'xonsh-devel':
> invalid command name "BASHwards-looking”
yep, I just pushed a fix for the missing \ in the descriptio
Hi Andrea,
I just saw this when running portindex on my El Capitan VM:
Failed to parse file shells/xonsh/Portfile with subport 'xonsh-devel':
invalid command name "BASHwards-looking”
Greets,
Marko
