> On 19 Aug 2015, at 11:18, Louis Gesbert <[email protected]> wrote: > >> Another possibility would be to have aliases for builtins, and allow >> to override their default names: for example, if I type "opam search >> XXX", opam would first call "opam-search", and only if it does not >> exist, call the builtin. Then "opam-search" would be able to call >> "opam builtins search XXX" to access the builtin command with enhanced >> parameters... > > That sounds dangerous ;) > There is at the moment a check that specifically disables plugins named like > a known command. The above could be quite straight-forward to implement, but > I don't clearly see a use-case.
I think this kind of ‘shadowing’ can be confusing for users and end up making bug reports more complex to handle. _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
