You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
In
atom@7a5d727
the 'set-user-settings' callback was changed so that it nolonger
returned the promise created by `ConfigFile.update()`. This meant that
the logic in
[`ApplicateDelegate.onDidChangeUserSetting()`](https://github.com/atom/atom/blob/5f0231b/src/application-delegate.js#L193-L206) which uses
`.pendingSettingUpdateCount` to avoid triggering in response to calls to
ApplicationDelegate.setUserSettings` was no longer effective.
I noticed this when updating settings via the setting view. If you type
at just the right (wrong?) cadence, you'll notice that your input can
get updated with stale values.
Something like this:
```
You type "a" "b" "c"
config.set "a" "ab" "ac"
config.observe "a" "ab" "ac"
Input value "a" "ab" "a" "ac" "ab" "ac"
```
It's possible that is the same as atom/settings-view#1062
After this change typing in settings input seems to behave as expected.
If you type in
Settings > Editor > Font Family
on macOS or Windows, it will delete your characters as you type.The text was updated successfully, but these errors were encountered: