
On 2011 May 25, at 16:41, Gwern Branwen wrote:
On Wed, May 25, 2011 at 6:22 AM, Jacek Generowicz
wrote: I had assumed that it connected to a server.
It did at one point, but Hoogle had downtime and the local hoogle command was just as good and worked offline.
Makes sense.
(Maybe my assumption was not entirely unfounded, given that the installation instructions for lambdabot blithely state that you "just cabal install lambdabot", nowhere suggesting that you might need to *manually* install some of its dependencies.)
Well, does every lambdabot user want mueval and hoogle installed?
Quite possibly not, but it would it be too much to ask, to have the documentation mention that they need to be installed separately if you intend to use them through lambdabot? I've already stumbled across mueval and hoogle as things that need to be installed separately before the full advertized features of lambdabot work. With this experience under my belt and the benefit of hindsight, I vaguely, almost, kinda, maybe see how I could have guessed that the stubborn response "A Hoogle error occurred." to any hoogle command in lambdabot, means that I need to install hoogle locally: 'hoogle ...' --> "A Hoogle error occurred." ==> install hoogle. But how on earth was I supposed to guess that in order to make 'check' work, the package to install was 'mueval', given that the error message was "Terminated"? 'check ...' --> "Terminated" ==> install mueval. Hmmm. What other lambdabot features rely on packages that need to be installed separately?
Once I have the hoogle command line version working, it seems that lambdabot truncates its output to just the first 3 lines. Is this normal? Is there a way of customizing or changing this behaviour?
It's normal, yeah. Don't want to spam #haskell with 100 lines of useless matches.
Agreed. I guessed that this would be the motivation.
Configurable? Not really.
OK. Thank you.