warmstarter
commented
3 years ago and that was quick to find. if you have your TERMCAP enabled, but your HARDCODE set to TERM_* it will enable weird behavior. You shouldn't really ever be set for those things at the same time, but it's possible to do it (as I just demonstrated.) So, going to leave this here as a note for myself to tighten up the conditions of the #define's a bit better throughout. I think it will also add clarity to things, such as with the OS2 and EMXANSI confusion (though I kinda just wanna rip those out.)
Accidentally got my terminal hardcoded, set to hardcode-vt100 and noticed there's a bug. Initial status line seems to start one space in, which messes up a ton of things. My guess is there's either an off by one error or a slightly mangled ANSI control sequence. Haven't gotten to investigate thoroughly yet, but the earlier versions I checked still had the bug. Doesn't seem like a priority as most people are not going to need hardcode-vt100 terminal encoding, but it could be doing more subtle stuff. Worth fixing eventually, so leaving a note here.