-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Description
This has bugged me for a while but I've never filed it. On the "physical" vty under FreeBSD, fish emits some invalid/unrecognized character codes that appear as garbled letters before each fish_prompt call.
Here's a screenshot (clean fish install from master):
If using the new vt (aka newcons) console driver (used by KMS drivers and the UEFI framebuffer), the problem goes away:
It's not a huge deal since vt is the default on FreeBSD 11 and up, but sc is still supported (and required if you want to use a driver without KMS support).
However, it bugs me because there's nothing funky in the default prompt that should result in this behavior in the first place, as it's all ascii and standard color escapes (which seem to be working fine). The default $TERM at the console is xterm for both drivers, and the problem persists under tmux where $TERM defaults to screen instead.

