Does it mean the session information will be lost if the project directory is moved somewhere else? The whole point of #3021 is to preserve the session when the project directory is moved to some other place (which, right now, is quite annoying).

If the project config and session are split, any scheme that is able to distinguish projects with different paths, but same basename, will risk allowing the session to be orphaned.

• There could be an option to not split the session from the project. In that case, relative paths would continue to work.
• The scheme may be extensible to allow it to work with relative paths, at the risk of being unable to distinguish between projects that share the same basename.
• If Project Preferences is extended to be able to move project files, the session files could also be updated.
• Project files could contain a copy of the hash to enable locating and moving old session files.
• You can suggest other ideas.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.