Cannot open fzf file picker with the `fzf_terminal_command` in Kitty about fzf.kak

[andreyorst]

Sorry for the delayed reply.

I don't use Kitty, so I can't really help here, but the error shows me that the terminal-tab command is not defined.

Can you use terminal-tab outside of fzf.kak? Maye something with kitty.kak not being loaded?

[dssgabriel]

Hi!

It indeed seems to be that kitty.kak is not loaded, as none of the commands defined in this file work/are recognized by Kakoune when run outside of fzf.kak.

I'm not sure what the fix is though? How can I manually load the missing kitty.kak on Kakoune's startup?

[andreyorst]

I believe it is loaded by the https://github.com/mawww/kakoune/blob/021da117cf90bf25b65e3344fa8e43ab4262b714/rc/windowing/detection.kak script. However, it will load only one of these modules, so I guess you'll have to manually specify that you're running Kitty. I think its a question for upstream why kitty.kak is not loaded, but my wild guess would be that you have some other terminal that is found by the script above.

[andreyorst]

Perhaps something to do with this check: evaluate-commands %sh{ [ -z "${kak_opt_windowing_modules}" ] || [ "$TERM" = "xterm-kitty" ] || echo 'fail Kitty not detected' } Check what your TERM env. variable is set to

[andreyorst]

Perhaps something to do with this check: evaluate-commands %sh{ [ -z "${kak_opt_windowing_modules}" ] || [ "$TERM" = "xterm-kitty" ] || echo 'fail Kitty not detected' } Check what your TERM env. variable is set to

[dssgabriel]

Sorry for the delayed reply, I haven't had much time to look further into this.

It indeed seems that this issue is related with upstream, so I'm closing this one.
From what I could test though, even when launching Kakoune with TERM=xterm-kitty kak, the check above fails. I don't know what's causing this. It seems that the windowing detection scripts aren't even called by Kakoune, as none of the alternatives defined in that module seem to be run.
Thanks anyway!