phaolo: I must say that I previously tried symlinks in Win7 and they didn't work with gogrepoc. I guess they do in win10?
I would have preferred to avoid having to use a "bridge" folder, but altering gogrepoc seems too difficult, so I may have to accept that option (atm I forgot if there could have been some issues with orphaned folders).
Anyway, I'll still have to create a excel+script to at least automatically create\refresh the symlinks (but I should manage).
I'm using Linux here, and the last "NT style" Windows version I've been actively using was Vista, but meanwhile Symlinks
should work on Windows as well. It's important to not use the old ".lnk" type "links", which are text files with more information than just the path name they point to – those only work when "clicked" on, in Explorer, for example. NTFS as a filesystem is required for those "non-.lnk-links". This had "hard links" from the beginning, they also implemented "reparse points", which are more "mount points" rather than "links" in Unix terminology. At a certain point, MS came up with "true symlinks", which
should be "transparent" for Python applications (i.e. should not require specific support and additional programming effort in "gogrepoc.py").
What I didn't mention: symlinks can get "broken" by renaming or moving the path they're pointing to. This normally results in a write error, the path won't be re-created when accessed.