editor_return_does_auto_indent= reversed on 0/1 conversion in ini file to false/true

To reproduce: >From menu, save settings, where ini last saved quite some time ago contained 0s for false and 1s for true, including: editor_return_does_auto_indent=0 Actual behavior: editor_return_does_auto_indent=true Expected behavior:

Re: Announcement: this mailing list will be retired by the end of Oct 2022

Andrea Veri composed on 2022-10-20 13:09 (UTC+0200): > Mailing list subscribers are invited to migrate to GNOME's Discourse > instance [1]. Neil made sure [2] to create a set of tags ... > [1] https://discourse.gnome.org I went there. I saw nothing obviously having anything to do with MC on home

corruption on vttys

Is this a known problem? Block characters following funzip (7) and liblapadk.so.3 (3 & 5) do not belong there. I see this quiet commonly on return to a vtty running mc from some other vtty login. Ctrl-O Ctrl-O clears them away. http://fm.no-ip.com/SS/mc-corrupt-1440x0900.png This has been

displays bad regular file timestamps on entry to .bz2 file & preserves the errors on copy out

It's only happened on this one so far that I can remember: Others I've checked from mozilla.org are handled normally. Tar has no such problem. Is this a known issue? I've not been able to

random "characters" in filename field

http://fm.no-ip.com/Files/Pix/Tmp/mcCorruption.jpg In this image they are drawn to the right of icewm session (7 on line 25) and rdoc (8 on line 40). This framebuffer screen happens to be 180x56 (1440x900). Font is 256char 8x16 font from file /usr/share/kbd/consolefonts/default8x16.gz. This is

Re: change default configuration

Egmont Koblinger composed on 2018-07-27 20:43 (UTC+0200): > Oswald Buddenhagen wrote: >> fwiw, i always found that default setting rather surprising and >> counter-productive, too. the vim/emacs/etc. hardliners will find the way >> to launch their personal deity, err, preferred editor soon