On Thu, Sep 2, 2010 at 7:49 AM, steve donovan <[email protected]> wrote: > On Thu, Sep 2, 2010 at 12:33 PM, Andre Carregal <[email protected]> wrote: >> OTOH, extending the search to remote directories could slow down the >> command for those with bad or non existent connections and would be >> somewhat of an overload of the verb show. > > Yes, I'm often aware of that problem - that wait of several seconds > before LR gives me a query back. And then anybody using 'show' would > be at the mercy of mistyping! > >> "query" (or something similar) would fit better for things that are >> not "here". > > That does make sense. I'll put something basic & local together. > Another thing it would present is what modules have been added to the > system. (can read this from the manifest)
Yes, I was just about to suggest this. I'm more often interested in learning which modules the rocks present than which files are provided by the rock. Maybe this information could even be provided by 'list' as well (through a flag like --long, analogous to 'ls -l') > (It would be most cool if LR search would understand 'lfs' to mean > 'luafilesystem' but that is another discussion.) That would be nice indeed, but it requires extending the remote manifest, which would also require peeking inside .rock files, so not only it's extra work but it might also be incompatible (or not, since local manifests do provide module information; haven't thought much about it). -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
