git master: --enable-charset should automatically detect user's charset

[slyfox]

After recently merged utf-8 branch into master we got interesting (rather old) misfeature:
Encoding for output/view/edit is set to 'Other 8 bit' by default.
It is not true for most of modern distros, UTF-8 is almost everywhere nowadays.

When user tries to use git master he stucks with ant awful problem:
editor shows him dots only and user has to:

• switch display bits to UTF-8 (in F9 -> Dispaly bits)
• switch encoding via 'Ctrl+T' and set UTF-8 manually

My proposition:

• Display bits should not be choosable in menu:

they should be detected via LC_CTYPE (nl_langinfo(CODESET))

• default encoding in editor should be equal to autodetected display bits (unless other is choosen explicitely via 'Ctrl+T')

[angel_il]

branch: 343_check_codeset (parent: master)
changeset: f3a3a4f3a89eba3e544dc22828431bba36c07870

[angel_il]

branch: 343_autocheck_codeset (parent:master)
changeset: e25d0744f9b4c8808de612115e472aa3fbeb72fc

prev branch has been removed

[iNode]

Yes, it work.

But why need ask user defaults on first start of mc?
(Yes. mv ~/.mc ~/.mc.bak; mc and it did happend).

I propose setup default vaules without user interaction.

And also cp1251 don't work with this test

#!/bin/sh

rm -f *.tst

#echo "проверка" | iconv -f utf-8 -t cp1251 | enca
echo "проверка" | iconv -f utf-8 -t cp1251 > cp1251file.tst

cat<<DESCRIPTION
=== test #343 ===
Try to edit file cp1251file.tst
when you select charset CP1251 (C-t 5)
you should see text "проверка"

(press enter to close test description)
DESCRIPTION

read void

and the same with koi8-r (and maybe any other).

Did you broke editor charset select or that branch should be rebased?

[angel_il]

rebased again
branch: 343_autocheck_codeset
changeset: 31b8e949cd47d7b29d3cc7d05905c244c27fb9e3

[angel_il]

changeset: 23e907be8128b98d232099d2c48cf1f7a2dd86ed (forced update)

[slavazanko]

All work fine. Code looks good. Three test cases passed:

1.
$ sudo su - test_user
$ rm -fR ~/.mc
$ /path/to/tested/mc

2.
$ sudo su - test_user
$ sed -i 's/UTF\-8/8859-1' ~/.mc/ini
$ /path/to/tested/mc

3. Runing mc with normal config

my vote here.

[iNode]

% git branch | grep '*'
* 343_autocheck_codeset
%  git log HEAD~1..HEAD | grep commit
commit 23e907be8128b98d232099d2c48cf1f7a2dd86ed
% mc -V | grep GNU
GNU Midnight Commander 4.6.99.2-95-g23e907b

Test case 1:

% rm -rf ~/.mc
% mc 
# [fix it]
# go to test file described in my previous post
# open it 
# Select Windows 1251 [C-t 5]
# no text here
# [F10][F10]
% grep UTF ~/.mc/ini  
display_codepage=UTF-8

So testcase failed.
1) There is no dialog should need for default setup without config.
2) Editor works incorrect (if I select Options->Display Bits manually all works properly)
3) See test case 2

Test case 2:
Run it again.
Dialog window - again. And again [Fix it].
Open test file, [C-t 5], and yeah it's ok.
[F10][F10]

% grep UTF ~/.mc/ini
display_codepage=UTF-8

But every mc start I see that Dialog.

I tested invalid branch or it's work fully invalid?

[iNode]

Yes, now that branch work properly.

[angel_il]

Fixed: d737b9151f7ee91320425499ccb7923f48207336

[andrew_b]

If mc is run as viewer or editor the codeset is not checked.

[angel_il]

Branch: 343_fix_mcedit_autochoice_codeset (parent: master)
changeset: cb9171d2ed99061478bd8451d287f33f04def30b

[angel_il]

branch: 962da1b296cd7f187e9a0b27ca22fb1677b165ec (forced update)

[angel_il]

Fixed: d205e724f0eb7f56094cf30201cfd73ab2c049f6