> I have pushed a couple patches to HEAD
> (http://eigenclass.org/repos/fastri/head) that implement these search methods:
> * complete namespace (m)
> * complete both namespace and method (f)
>
> FastRI's search strategy can be specified with the -O option:
>
>     -O, --order ORDER                Specify lookup order.
>                                      (default: eEnNpPxX)
>                                      Uppercase: case-indep.
>                                      e:exact n:nested p:partial (completion)
>                                      x:nested and partial m:complete namespace
>                                      f:complete both class and method
>                                      a:match method name anywhere
>
> See [225037] for an explanation of the basic search modes.
>
> You can make fri behave like ri (regarding partial completion of the namespace
> name) by adding 'm' to the lookup order:
>
> $ fri -Om A#flatten
> ---------------------------------------------------------- Array#flatten
>      array.flatten -> an_array
>
> Moreover,
>
> $ fri -Of A#a
> ------------------------------------------------------ Multiple choices:
>
>      ACL#allow_addr?, ACL#allow_socket?, Abbrev#abbrev, Array#abbrev,
>      Array#assoc, Array#at, Autotest#add_sigint_handler,
>      Autotest#all_good
>
>
> However, I'm not sure about the position in the search strategy (currently
> eEnNpPxX) at which the 'm' or 'f' modes could be added.
> Maybe  eEnNpPxXmM(fF)a  ?
>
> Anyway, even if I left the default search strategy unchanged, it could be
> overridden with --order (-O).
>
Ok, great. If it could check some ENV variable for the search order
people could spec their own default. FASTRI_LOOKUP_ORDER? I don't
think that would add very much to the execution time...

Regards,

Robert