@eht16 It's very simple actually, I only wanted to use them as session presets. Although hacky, it was working great until the read-only warning has been introduced in later versions. The warning itself isn't problematic, but the fact that it constantly pops up. A partial solution would be to warn only once per file and suppress subsequent warnings. A more thorough solution would be #2304 (which would also solve #2864). Instead of "write-locking" the file, configurable "session autosaving" would probably be more understandable while having practically the same effect.

—
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.