On Tuesday, 16 August 2016 at 13:32:26 UTC, Jacob Carlborg wrote:
> On 2016-08-16 11:37, Seb wrote:
>
>> Manual work? O_o
>> Just open code.dlang.org and either hit CTRL-F or use the search bar
>> (Martin added elastic search two months ago) as the packages usually
>> have a very low PageRank.
>
> It's a bit problematic when you don't know what to search for. Not all projects have a descriptive name ;)

Does it only search the description or also the README?

On Tuesday, 16 August 2016 at 13:52:19 UTC, Edwin van Leeuwen wrote:
> On Tuesday, 16 August 2016 at 13:32:26 UTC, Jacob Carlborg wrote:
>> On 2016-08-16 11:37, Seb wrote:
>>
>>> Manual work? O_o
>>> Just open code.dlang.org and either hit CTRL-F or use the search bar
>>> (Martin added elastic search two months ago) as the packages usually
>>> have a very low PageRank.
>>
>> It's a bit problematic when you don't know what to search for. Not all projects have a descriptive name ;)
>
> Does it only search the description or also the README?

https://github.com/dlang/dub-registry/pull/149

Indexing the README is marked as TODO, but it shouldn't be too difficult to add  - afaik it's already stored in the database.

On Tuesday, 16 August 2016 at 07:19:18 UTC, Edwin van Leeuwen wrote:
> I am using:
> http://code.dlang.org/packages/docopt
>
> It's not really json configurable, but that shouldn't be to complex to implement yourself.

That's also very nice. I hadn't thought of writing the help text first and then having a parser for the usage to generate options.
Much appreciated.

On Tuesday, 16 August 2016 at 01:46:53 UTC, Seb wrote:
> Have you had a detailed look at std.getopt?
> https://dlang.org/phobos/std_getopt.html
>
> That's very similar to commander.js ;-)

I shall reread the std.getopt doco.

ty ss :)