There is a problem with storing the session setting Charset encoding for filenames to the settings database.
Steps to reproduce:
Press F4 on some session in the session list
Edit Charset encoding for filenames: change to 1251
Save session, exit Far, start Far
Check Charset encoding for filenames, it should be equal to 1251
Change Charset encoding for filenames: select the first element from the drop-down menu (65001 (UTF-8))
Save session, exit Far, start Far
Check Charset encoding for filenames again: it is set to 1251 instead of 65001 (UTF-8)
This pull request fixes the problem. It just prevents setting empty code page (aka default value). This way, the correct value will be written to the database later.
There is a problem with storing the session setting
Charset encoding for filenamesto the settings database.Steps to reproduce:
F4on some session in the session listCharset encoding for filenames: change to1251Far, startFarCharset encoding for filenames, it should be equal to1251Charset encoding for filenames: select the first element from the drop-down menu (65001 (UTF-8))Far, startFarCharset encoding for filenamesagain: it is set to1251instead of65001 (UTF-8)This pull request fixes the problem. It just prevents setting empty code page (aka default value). This way, the correct value will be written to the database later.