if the TERM environment variable is not set, mc crashes Reproducible: Always Steps to Reproduce: 1. start an xterm 2. verify that TERM=xterm 3. start mc, see that it works, stop it again 4. unset TERM 5. verify that TERM= 6. start mc 7. See Segmentation Fault Expected Results: say "i cannot run with dumb terminal"
why should one unset the TERM variable?
well, it happened by accident that my TERM variable got unset. but imagine if all programs just crash in case of wrong parameters. this is not the way to write programs. it's an error and must be fixed. you should not argue "why should one unset the TERM variable?" X11 programs also don't just silently crash if the DISPLAY variable is unset. instead they all display useful error message. did you report the issue upstream or just silently ignore it??
that's correct indeed, i'll look into reporting it upstream
fixed in -r12