Integrate Autocomplete with Kitty Terminal about fig

[mschrage]

Support for kitty is landing in v1.0.49!

[mschrage]

You no longer need to be on a beta version of either Fig or Kitty. However, currently the integration is a bit tricky to setup which is why it is hidden by default.

Instructions for those who are brave enough to attempt it:

1. Run fig settings integrations.experimental true and then restart the Fig app
2. Click the Fig menubar icon > Integrations > Kitty > "Attempt to Install"
3. Go to a terminal and run fig debug ime enable. A System Preferences window will appear and prompt you to install a third party Input Method.
4. Run fig debug ime select
5. Restart Kitty and autocomplete should appear🤞

[magus]

Any update on when this is going to land?

[risc12]

The other day a mailing got sent out that there is beta Kitty-support. How can one enable this? I've already set Fig to download the Beta-versions.

This is what was in the email:

[tomsvogel]

i reinstalled fig, after that it was possible to install the plugin for kitty, it works now 🎉

[mschrage]

We are waiting for the next release of Kitty since our integration require a kitty.conf parameter (watcher) that is not supported currently.

I misjudged how close the newest build of Kitty would be take to be released. But rest assured, everything else is ready to go for Fig to work with Kitty.

[kovidgoyal]

Yes, this release of kitty is delayed because of waiting for
kovidgoyal/kitty#3948 to mature.

But, note that nightly builds of kitty are available if needed.

[chrismilleruk]

FYI, the Kitty dependency mentioned above was closed and released earlier today:

kovidgoyal/kitty#3948 (comment)

[mschrage]

We are going to do a sprint on this next week. I believe that I've figured out a reliable way install (and enable) the input method.

[kingluddite]

@mschrage You rock! Works like a charm!!!

[mschrage]

Thanks again for helping adding the watcher parameter to Kitty @kovidgoyal. It makes our integration much more robust.

[mschrage]

We still need to push a new build @jim-at-jibba!

[Liquidmantis]

Looks like I found fig just at the right time!

Thanks for the work on this, @kovidgoyal @mschrage

[matsdahlin]

We are going to do a sprint on this next week. I believe that I've figured out a reliable way install (and enable) the input method.

That sounds promising! Thanks for all your hard work ❤️

[matsdahlin]

@mschrage the instructions worked fine for me! Seems to be working as expected so far 👌🏻
Thank you!

[smileart]

@mschrage as I understood, it's not supposed to be experimental any more. Although I did not try enabling/installing Kitty support as per the instruction you're referring to, it started working out of nowhere. Before I surely tried reloading terminal, shell, tmux, laptop, triple checked all the .zshrc and such, it did not work, but yesterday it just suggested me some autocomplete. So, it'll remain a mystery why it did not start right away. 🤷

[mschrage]

For those who find this in the future, the command to enable Fig autocomplete in Alacritty is fig install --input-method

[mschrage]

Some helpful links to Kitten API:

• Remote Control
• List all window
• kitty.conf located in ~/.config/kitty/kitty.conf
• Documentation on the remote control protocol

Enabled allow_remote_control true in kitty.conf and the run kitty @ ls to view all windows and additional metadata.

[mschrage]

Alright I think I've figured out a way to get the information we need without polling!

1. Update the user's kitty config to set allow_remote_control true
2. Add --watcher ~/.fig/tools/kitty-integration.py to ~/.config/kitty/macos-launch-services-cmdline
3. Write a watcher in kitty-integration.py that notifies the macOS app when the focus changes.

def on_resize(boss, window, data):
    # Here data will contain old_geometry and new_geometry

def on_focus_change(boss, window, data):
    # Here data kill contain focused

def on_close(boss, window, data):
    # called when window is closed, typically when the program running in
    # it exits.

[mschrage]

Ah so close! This automatically sets up the watcher for the first window, but doesn't for subsequent tabs and sessions. We could potentially define a custom startup_session for this? (I think this is more likely to collide with user's existing customizations.)

[kovidgoyal]

You are welcome!

[mschrage]

Thanks for letting me know @chrismilleruk

[jim-at-jibba]

Hey,

Now that this is done show Fig work in Kitty? I still get told its not suported

[jim-at-jibba]

Ace, sorry for jumping the gun. Just wanted to check I had not missed anything.

Thanks

[hakamadare]

@mschrage also really looking forward to kitty support!

[sandangel]

hi, I updated to beta version, and saw an option for kitty integration. but it's saying that could not install the input method. could you let us know what should we do?

[mschrage]

Run fig debug ime status and share the output here?

[tomsvogel]

i also tried the kitty nightly with the beta of fig and no success,

$ fig debug ime status
input method is not running.

[mschrage]

@tomsvogel can you try running the following commands one at a time and share the output here?

fig debug ime register
fig debug ime enable
fig debug ime select
fig debug ime status

[tomsvogel]

$ fig debug ime register
Registered input method!

$ fig debug ime enable
Enabled input method!

$ fig debug ime select
An error occured when selecting input method: The operation couldn’t be completed. (OSStatus error -50.)

$ fig debug ime status
input method is not running.

[mschrage]

Could you try restarting the macOS app and then running fig debug ime select again? @tomsvogel

[tomsvogel]

$ fig debug ime select              
Selected input method!

[sandangel]

~/.dotfiles on  master [✘!+] took 14s  76%
λ fig debug ime select
Input method is already selected!

~/.dotfiles on  master [✘!+]  76%
λ fig debug ime status
Input source is not enabled

[mschrage]

Seems like there is still some room to improve the install process - the TextInputServices APIs are super finicky.

[kingluddite]

I followed all the instructions above but fig still says kitty is not supported. I upgraded kitty with brew to latest version. I reinstalled fig. No luck. Fig works in iTerm but wish I could get it working in Kitty (FYI - fig also not working in Alacritty)

[tomsvogel]

@kingluddite you tried kitty knightly and fig beta?

[kingluddite]

@kingluddite you tried kitty knightly and fig beta?

Not yet. @tomsvogel Is there a link to the fig beta install? Can't seem to locate it.

I found that the kitty nighly can be installed with:

$ curl -L https://sw.kovidgoyal.net/kitty/installer.sh | sh /dev/stdin \
    installer=nightly

source

[dbowling]

I got a "Learn More" button on a message when running the debug command, which gave me a 404 on the fig site.

Other than that, following the instructions was easy and everything is working as expected. I'm really happy to be able to use this with Kitty!

[liby]

@mschrage

A System Preferences window will appear and prompt you to install a third party Input Method.

I have some questions about this. After downloading the third-party input method, don't you need to apply it? I don't see it in the list.

[pistazie]

Worked well for a few days and then stopped. tried repeating with no success :(

[mschrage]

@pistazie run fig doctor --verbose

[pistazie]

thanks @mschrage in my case the issue was that Secure keyboard input disabled was not disabled.
I fixed it using your documentation and fig+kitty are awesome again.

[smileart]

Here's the output of my fig doctor --verbose and still, it does not work in kitty:

Let's check if you're logged in...
✔ Logged into Fig

Let's check your dotfiles...
✔ .bashrc contains valid fig hooks
✔ .profile contains valid fig hooks
✔ .zshrc contains valid fig hooks
✔ .zprofile contains valid fig hooks

Let's make sure Fig is running...
✔ Fig bin exists
✔ PATH contains ~/.local/bin and ~/.fig/bin
✔ Fig Integration
✔ Fig is running
✔ Fig socket exists
✔ Daemon
✔ Figterm socket
✔ Insertion lock does not exist
✔ PATH and PseudoTerminal PATH match

Let's check if your system is compatible...
✔ OS is supported

Let's check fig diagnostic...
✔ Installation script
✔ Compatible shell
✔ Fig app installed in the right place
✔ Autocomplete is enabled
✔ Fig CLI path
✔ Accessibility enabled
✔ Secure keyboard input disabled

Let's check your terminal integrations...
✔ VSCode integration is enabled


Fig still not working? Run fig issue to let us know!
Or, email us at [email protected]!

[mschrage]

@smileart have you followed the steps outlined here? #26 (comment)