Fig now supports JetBrains IDEs

I don't understand what Fig is actually for. Why would I want a "visual autocomplete" when I already get what I want out of bash-complete + fzf, a more technically complete and understood solution?

Hey HN! Didn't expect to see Fig here this morning.

We just released a new version of Fig that allows users to install a custom input method on macOS. This means we now work with over a dozen new terminals, including all JetBrain IDEs, Alacritty, Kitty, WezTerm and more.

The engineering behind it was surprisingly tricky since these APIs are not as well documented as you'd hope. (Indeed, the best place to look is the C header files [0])

But with a lot of trial and error, we've managed to get an implementation we're happy with. (That said, if anyone has tips on how to install an input method, without requiring a system restart, I'd love to hear them!)

I'll be around all day to answer any questions about how Fig works under the hood!

--

Also just to address some stuff that generally comes up when we're posted on HN:

1. Why is there a login?

Autocomplete is just our first product, and it's part of a suite of tools focused on improving developer experience in the terminal. The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices.

2. Is there telemetry?

Yes, but you can opt-out entirely by running a single command.

fig settings telemetry.disabled true

3. How will Fig make money?

Fig will always be free for individuals. Teams pay for Fig for collaboration and discovery of internal scripts and for managing dev environment setup and onboarding.

4. Is there a Linux/Windows version?

We are making really good progress and will have a prototype in the next month or so. See the Github issues for Linux[1] and Windows[2]

[0] https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX10...

[1] https://github.com/withfig/fig/issues/34

[2] https://github.com/withfig/fig/issues/35

I think there are two main areas where we improve the default experience.

1. Zero configuration needed to get started.

With Fig, the experience just works out of the box. A lot of developers - especially people less comfortable with the terminal - don't feel confident installing a bunch of 3rd party zsh completions or creating a custom setup.

2. Extensibility.

We've worked really hard to make the experience of writing your own completions very easy and powerful. Lots of teams are using Fig to make internal scripts and CLI tools more ergonomic and discoverable.

In my experience, writing custom shell completion scripts is not very much fun.

Fig is macOS-only, proprietary, requires e-mail and has telemetry

Fig relies on free labour to add completions and does not support open-source completion formats

Fig is VC-funded and at some point will have to generate revenue for it’s investors - at your cost

don’t use Fig!

if you have zsh you can use zsh-autocomplete, which is no worse than Fig

https://github.com/marlonrichert/zsh-autocomplete

edit: this comment was the most popular before HN moderators pinned it down, turns out Fig is YC-sponsored, so i’m not surprised

Is anyone else getting this warning? I am using macOS 12.3.1, iTerm2 3.4.15 and bash 3.2.57(1)

bash: trap: __bp_install: invalid signal specification