fzf is not working in CLI / TUI mode

[eshepelyuk]

Hello

I'm having following playbook

When running from VS Code - fzf is successfully invoked, i.e. it's rendered and arrow keys are worrking, Enter completes selection

But when running from CLI - fzf render just blank screen, no fzf interface.
The same happens to other similar tools: skim, peco.

I'm running playbook like this

Works

runme run --filename test-fzf.md --index 0
hello

Empty blank screen

runme run --filename test-fzf.md --index 1

[sourishkrout]

Okay, I can locally repro this and under the issue. With the markdown below I confirmed my suspicion that it's connected to the piping into fzf. This is a key-limitation in Runme's Runner v1 which is why we've created v2. However, we haven't fully completed the migration (mainly the CLI).

You can see the difference running: runme run pipe-fzf (broken) versus runme beta run pipe-fzf (works). The runme beta CLI interface is incomplete, unfortunately.

Completing the Runner v2 migration in the CLI is open the agenda but unclear when we'll get to it.

[eshepelyuk]

1. how can i get this runme beta ?
2. why does it work within vs code ?

[sourishkrout]

1. how can i get this runme beta ?
2. why does it work within vs code ?

For 1. just insert the word beta between runme and run. Please note that the CLI interfaces don't overlap 100%.
It's got something to do with how the Pseudoterminal (pty) is allocated which is something the extension delegates to VS Code through the extension API whereas the CLI implements it directly. This implementation is different in beta versus stable.

[eshepelyuk]

Hello @sourishkrout

I've tried to use runme beta and I'm receiving

/nix/store/ciarnmsx8lvsrmdbjddpmx0pqjrm8imb-bash-5.3p3/bin/bash: line 10: fzf: command not found
could not execute command: exit status 127

when I've tried to run following echo $PATH as a playbook

I'm receiving

/no-such-path

[sourishkrout]

Mind running runme --version and posting the output here please, @eshepelyuk?

[eshepelyuk]

Mind running runme --version and posting the output here please, @eshepelyuk?

I can't provide exact output now, but the version is pinned to 3.15.4

[eshepelyuk]

Hello @sourishkrout

this is an requested output

runme version 3.15.4 (v3.15.4) on 1970-01-01T00:00:00Z

[sourishkrout]

Okay, that looks like the right version.

I have had issues with bash locally, too. Let me take a look into it. Looks like an issue in Runner v2.