I got this recently, except the message was:

> /usr/bin/how-can-i-help:244:in `&': no implicit conversion of true into Array 
> (TypeError)

'true' rather than 'nil'.

But on subsequent runs it printed 'nil' like in the bug report (some
system state had changed).  Athos Ribeiro's proposed patch fixes the
'nil' case; I don't think it would fix the 'true' case.

Reply via email to