The code assumed that the value of the profile-restore field is "default" for such profiles, but the C implementation is such that the field is intentionally omitted in such case. This resulted in incorrectly trying to restore such profiles. However, there are no stored values with profile-restore=default, so it only resulted in a harmless warning, but otherwise behaved correctly (i.e. nothing is restored). Fix the condition by taking into account that missing field means "default", so that it doesn't try to restore in such case, and avoid the warning.
Unified · Split
| @@ -163,7 +163,7 @@ local function load_profiles() · 162 unmodified lines | ||
| 163 | 163 | properties = {}, |
| 164 | 164 | status = nil, |
| 165 | 165 | dirty = true, -- need re-evaluate |
| 166 | − has_restore_opt = v["profile-restore"] ~= "default" | |
| 166 | + has_restore_opt = v["profile-restore"] and v["profile-restore"] ~= "default" | |
| 167 | 167 | } |
| 168 | 168 | profiles[#profiles + 1] = profile |
| 169 | 169 | have_dirty_profiles = true |