Skip to content

Conversation

@FichteFoll
Copy link
Member

Since the settings are accumulated in a ChainMap, they would have to either be accessed via settings.maps[1].save() or via an explicitly named global.

I chose the latter, since it does not rely on the ChainMap order and is more explicit.

The same also applies to writing to the ChainMap before, of course.

Should fix #156 but changes are untested (I simply made the code changes and don't use the package).

Since the settings are accumulated in a ChainMap, they would have to
either be accessed via `settings.maps[1].save()` or via an explicitly
named global.

I chose the latter, since it does not rely on the `ChainMap` order and
is more explicit.

The same also applies to writing to the `ChainMap` before, of course.
Copy link
Member

@rchl rchl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed that the previous code was just broken. It just happened that settings[0].save() has never happened to trigger for me.

@rchl rchl merged commit 5695f73 into master Jun 4, 2023
@rchl rchl deleted the bugfix/fix-save branch June 4, 2023 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TrailingSpaces fails to execute

3 participants