On a clean lf installation without any configs, I run lf, it takes a second or two to start, then shows up with either an error running shell: exit status 1, or its input buffer pre-filled with garbage data that looks like ANSI terminal request/response.
In the first case, when I quit lf, I see this log in the terminal:
$ lf
'$yy11000000' is not recognized as an internal or external command,
operable program or batch file.
In the second case, the garbage is consistently this specific line:
$$yy11000000;;22$$yy11000066;;22$$yy99000011;;22$$yy6611;;66;;77;;2222;;2233;;2244;;2288;;3322;;4422cc
Per terminal session, it seems that running lf for the first time, it is always going be the first case (exit code), but from the second launch onward it is always the second case (pre-filled garbage).
It happens with an empty PowerShell profile, empty lfrc config.
Version
> lf --version
Go version: go1.26.1
Installed from github:
$env:CGO_ENABLED = '0'
go install -trimpath -ldflags="-s -w" github.com/gokcehan/lf@latest
On a clean
lfinstallation without any configs, I runlf, it takes a second or two to start, then shows up with either an errorrunning shell: exit status 1, or its input buffer pre-filled with garbage data that looks like ANSI terminal request/response.In the first case, when I quit lf, I see this log in the terminal:
In the second case, the garbage is consistently this specific line:
Per terminal session, it seems that running lf for the first time, it is always going be the first case (exit code), but from the second launch onward it is always the second case (pre-filled garbage).
It happens with an empty PowerShell profile, empty lfrc config.
Version
Installed from github: