Is there a way to map worktrees to directories, and vice versa?

[KingMob]

Problem

I need to use workspaces more these days, and I thought I'd write some helper shell fns to fit my workflow of making sibling workspaces.

The problem came when trying to write some workspace directory-switching functionality.

Is there any way to get a list of directories that the workspaces were created in, or are currently associated with? jj workspace list has no associated directory info. jj root always show the current workspace root.

Likewise, from a given directory, is there a way to figure out which workspace you're in?

I'm not averse to poking around in the guts of .jj/.git if that's the solution, but I'd rather not.

Example

Say you have a ~/code/jjrepo directory that's the default workspace. and sibling workspaces called sibling1 in ~/code/jjrepo-sibling1, sibling2 in ~/code/jjrepo-sibling2, etc.

I'm trying to write code like jj-worksibling.sh switch sibling1, or jj-worksibling.sh switch default that will work from any workspace's directory.

[jennings]

I believe there is no reference from the repository to where each workspace is located on disk. The workspace only refers back to the repository.

[KingMob]

I'm surprised that info isn't stored; it would be handy.

It would also enable forgetting the workspace if you delete the directory, and vice versa. I was a little surprised forgetting and deletion were independent operations.

[martinvonz]

The reason they're decoupled is so we can update the tracked state in the repo without having access to workspaces. For example, if one workspace is on a USB stick that's not plugged in, we can't update it. Similarly, if the repo lives on a server (as they do at Google), the workspace can still be on a user's local disk. In the latter case a regular path doesn't even make sense.

[KingMob]

Sure, that makes sense.

Would something like weak references be possible, though? I imagine a lot of the time (most?), workspaces will be accessible folders on your local machine.

It seems a shame to not support a common use case better.

[martinvonz]

Sure, I don't see much harm in recording paths to known workspaces somewhere as hints.