The problem that this would address is the complexity of figuring out
where a project has been deployed.
Yes, it's true that we can install from github. But to test that we
have supported that we need the project installed in a different
location.
And, yes, this is entirely solvable. But it's
Suggestions like this come up from time to time, but I think they are
mistaken. We already have a mechanism for naming files outside
standard J directories, see
https://code.jsoftware.com/wiki/Guides/Folders_and_Projects . I don't
think anything else is needed, rather any extra mechanism will add
Quite often, we might want to work with collections of J scripts which
are outside the standard J system and user directories.
It's quite possible, though obscure, to use introspection (4!:4 and
4!:3) to locate scripts relative to the currently executing script.
It would probably be better to
