bclarkx2 / goto Goto Github PK

Suppose I have a repo with 40 submodules. I would like to be able to jump to any of those submodules, but:

1. I don't want to have to add each one to my top level nav root
2. I don't want to have to switch to a new root just to go to these.

A good solution would be to have the ability to create a new root with only the submodules in it, then specify that submodule as a sub-root of the nav root that contains the parent repo. Then, when I am in the parent root p, I can access any of the submodules m by using the sub-root name s like so:

goto -s

goto

Having information about a given root be split between the root file and the roots.json manifest file makes it harder to plug and play with the roots files.

This is a pre-requisite to backing up the roots files with local overrides.

As a user, I would like to be able to immediately use the tool after i run the install script.

Instead, I get an error when I try to run any command because the config directory doesn't yet exist.

Users often have similar but not exactly the same file structures between machines. It would be nice if some roots could be shared between them, perhaps backed up in git/rsync/etc...

Local overrides and the "defaults" attribute would let me customize the globally backed up files as necessary on each machine.