@jrose Ooooh. That's very useful, thanks. It's relative to enclosing group. Which means the group it's a part of MIGHT be the offending thing - it resolves differently on either machine for some reason? Either way, I'll try setting it to relative to project and see if that solves my problem.
@vampiress that is weird and feels like an off-by-one-error inside xcode (e.g. because one project is is ~/dev/projects and the other one is in ~/develop/ and the different path depths are throwing xcode off)
@vampiress okay that is extra weird :blobcatfearful:
I do hope you figure out what the problem is but it sounds easy enough to work around too so at least there's that ^^'
@dequbed Yeah. When I first saw the issue I thought maybe it put the project file in with absolute rather than relative path but... no, relative just... relatively wrong.
@vampiress I would love to know if there's some silly "its idea of the 'current path' is retained when/where Xcode is first started", a la VS Code, Vim, etc etc.
@rfc6919@buzzyrobin Good point. Clumsy but yeah… it’ll do. Fortunately I’m the only one working on it so I won’t have to get other people to kludge it.