This got broken by 907a792 back in 2011 as encoding names started to be compared more permissively, leading to "none" matching the "None" encoding.

This shouldn't be too much of a problem as trying the None encoding first should not cause any issue, but fix loading of the option anyway.

This however won't restore settings from existing configuration files that used the previous code, as there is no way to tell whether the user selected the None encoding voluntarily or not.


To reproduce the issue, go to the file preferences, and deactivate the Use fixed encoding when opening non-Unicode files. Save the setting, and restart Geany: you'll see the setting is activated again.


You can view, comment on, or merge this pull request online at:

  https://github.com/geany/geany/pull/1326

Commit Summary

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.