oh-my-posh 13.7.0+ breaks Midnight Commander's subshell #4436
Labels
area: core
Issues not related to a specific subsystem
prio: medium
Has the potential to affect progress
ver: 4.8.26
Reproducible in version 4.8.26
Important
This issue was migrated from Trac:
philip_petev
(madmax2000@….com)Guys, any comments on this one:
JanDeDobbeleer/oh-my-posh#3415
Version 13.7.0 introduced changes in the function that hooks up with the bash prompt and that change causes mc to act like the -u parameter (no subshell) is used or the subshell support was never enabled in the first place.
Now, the oh-my-posh author claims there is nothing wrong on his side and the problem must be on your side.
Tested on:
Debian 11 (amd64, bash 5.1.4, mc 4.8.26)
Ubuntu 22.04.1 (amd64, bash 5.1.16, mc 4.8.27)
my NAS (Linux 4.2.8, aarch64, bash 5.2.15, mc 4.8.29)
Providing config to oh-my-posh or using the stock settings doesn't matter.
Some logs from the Debian machine:
I've selected version mc 4.8.26, but it happens pretty much with every version after this one. Can't say are the version before this one affected or not since 4.8.26 is the oldest I've got.
The text was updated successfully, but these errors were encountered: