Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SettingsArea: what it touches
In DevelopmentKind: in v2.1.267,
In DevelopmentSection of the release
What
A new helper (lr) wraps settings-file writes so that, on a permission-type write failure, it checks a new Lo() function and, if Lo() returns true, retries the write with allowSymlink: true (and checkParentDir: false), logging "Writing settings through symlinked path". However, Lo() is a stub that unconditionally returns false, so the retry branch and its log message can never run.
Why
Anyone whose settings file lives behind a symlink and hits this permission error still sees the original failure; the intended fallback to write through the symlinked path does not actually work yet.
