vt::ExecuteCommandBegin fails because of motd being displayed

[DamianFekete]

On some Linux distributions (like https://github.com/ublue-os/aurora) a motd (message of the day) is displayed by default when users log in.
Aurora uses glow to render a Markdown message.

/etc/profile.d/ublue-motd.sh executes this ublue-motd script:

#!/usr/bin/env sh

MOTD_TEMPLATE_FILE="${MOTD_TEMPLATE_FILE:-/usr/share/ublue-os/motd/template.md}"
. "${MOTD_ENV_SCRIPT:-/usr/share/ublue-os/motd/env.sh}"

envsubst < "${MOTD_TEMPLATE_FILE}" | glow -

It seems, that if glow is executed by .bashrc, the command that I try to execute in FAR is not executed at all in the BASH shell. I land in the shell and can type commands there, and I have to type exit to get back to FAR. Nothing is visible (neither the command or what I type).

For the following screenshot I've commented out

far2l/far2l/src/vt/vtshell.cpp

Line 1005 in b9702f9

_vta.DisableOutput(); // will enable on start marker arrival

to be able to see what is going on. Please ignore the {xxx} blocks in the motd.

Everything works as expected after I disable the motd, but I was wondering if this issue could be better handled (either by FAR or glow).

---

The temp vtcmd files are not deleted as far doesn't find the echoed marker.