I'm not sure what the exact situation is, but I think that the system
is behaving as expected. The general idea is that only one module is
in the official search path, Graphics, and that it then loads a bunch
of modules that are not on the search path by adding the Graphics/
prefix to their module name. The effect is that only one module
intrudes onto the module namespace instead of all of them. Since
you're trying to load a module that's not on the search path, the
system can't find it unless you add the Graphics directory to the
search path. The point of the design is that you won't accidentally
pick up modules in the Graphics directory; GTest isn't meant to be
imported separately so not seeing it is a feature, not a bug.
Personally, when I'm debugging inside a library like Graphics, I :cd
to the Graphics directory and then can load anything without messing
with the search path. If I'm just using the library, I shouldn't be
using anything not exported from the top level module so not seeing
the submodules is a good thing.
John
