proper contemporary (2026 year) way to set up $TERM for vt console (not X, not syscons)

Closest thread here about localisation, /etc/ttys and termcap I found was Thread console-settings-oddity.20676. There all answer was just link to handbook part about localization. It was true that times. But now where is UEFI, thus vt(4), therefore there must be different settings for text console font, keyboard ....

Why I'm asking: this time installing FreeBSD I found that bsdinstall, bsdconfig set settings into /etc/rc.conf for sc(4). Some of them obviously do not work with error message, some -- keyboard layout -- politely intercepted by system and proposed me correct one. So I easely recall heeded settings for my target (ukrainian locale, keyboard with ukrainian and russian keys). Changing console font seems to be not necessary, at least for now -- default font shows all cyrillic chars good. Locale setup using login.conf is very good -- one place for locale unlike linux, where I must put LANG in many rc's of shells.

But one thing I mentioned looks weird: some programs on console
1) draw incorrect ascii-art boxes, for example vidfont(1)
2) unexpectedly (for my, or course) react on some keys, or do not react at all: aforementioned vidfont(1) closed for PgUp/Pgdn keys, misc/mc do not react on them at all, also it did not see any Fx keys (yep, until learning keys in that case).

And other problems:
ee(1), when started, writes text from his status line (printed with "=" above text) not inside this "=", but lower
emacs(1) also did not react on PgUp/PgDn

Yep, all that works good inside X, but I found, that if to change $TERM to thins like xterm, or to xterm-88color -- emacs(1) shows hist status line in pretty green color, or better to xterm-256color, like in X, the aforementioned keys (Fx, PgUp, PgDn, others) works as expected. Except Backspace and Del -- they still interpreted in other ways in edtiors.

Moreover, if read /etc/termcap, there written, that cons25u -- default settings in /etc/ttys and others cons25, is for syscons().

It still greek to me all that settings in termcap (almost in part of Esc-codes), and also I found nothing about vt(4) capabilities compared to X terminals. But, as I said, chaning $TERM to xterm-256color works good for me.

So my questions:
* is there some considerations about pros and cons (pros I see, cons still not any) about change defaults for vt(4) setups from cons25u to something more appropriate?
* as far as I know little about terminals at all (in part of all that control codes, esq-sequences, compatibility issues in interpreting ^H and so on), I still want to change something in termcap definition to get Backspace and Del to work as I want (as it work in X usually). You may ask "why?", because really, a few of us, and I also, spend a little time in real text console, unless first setup and solving graphics issues. And my answer will bee -- maybe I learn something about that "greek" stuff that way. So, what to read to fix it, if it possible? I try read manpages, but without point to start (like "this terminal works this way, as mentioned in his manual, sow we must write these parameters this way....") I cant get it.
 
Sorry, I do not understand why, but my text was expanded and repeated in some strange way.... In simple text editor it was clear...
corrected.
 
Use xterm-256color for TERM and look at stty(1) to tune the behavior of ^H. You should not need to hack xterm terminfo. Note that vt(4) supports only 16 colors; unsupported colors will be rounded to nearest supported one.
If you use a UTF-8 locale (which you should, e.g. en_US.UTF-8), you might want to look at the thread about the gallant console font, which provides many more characters that other fonts may not.
 
Back
Top