autocomplete

People do! See: https://pixi.carapace.sh/ or https://github.com/withfig/autocomplete It's still a hard problem as lots of tools format --help differently. One of the things I'm jealous in Poweshell is their standardized completions

As far as I understand, the autocompletion specs, which is what powers this tool, are the only part of fig that is in fact Open Source https://github.com/withfig/autocomplete

Having contributed to the Fig autocomplete specs, I find this sad. The Amazon product Fig was built into basically works as replacement, which is good. Still, the core value of this product are the open-source autocomplete specs: https://github.com/withfig/autocomplete. What's going to happen to that? It looks like they are still using it in the Amazon product. It should definitely be possible for an open-source re-implementation of the Fig UI to use those specs. There is a lot of knowledge encoded in there!

Fig is awesome but with signups blocked[1] for 2+mo already it's also as good as dead ¯\_(ツ)_/¯ * [1]: https://github.com/withfig/autocomplete/issues/2068

https://github.com/withfig/autocomplete is it this?

I love this product, have contributed several times to it, and I'm a little torn. One thing I am thinking about now, is that the completion specs are MIT-licensed, and it should be possible to use them to re-implement a basic open-source version of the autocompletion product... https://github.com/withfig/autocomplete

You might find Fig completion specs useful for this: https://github.com/withfig/autocomplete

Hi HN! I’m Rahul, an engineer at Fig, and I led the development of Dotfiles. Our goal was to build a structured editor[0] for shell dotfiles - with a keyboard-driven editing experience that is as fast as a traditional text editor, while offering more guidance. We built this because in the process of onboarding users to autocomplete[1], we saw first-hand how much difficulty many developers have managing their shell configuration. Once you get the hang of it, editing configuration files, like your .zshrc or .bashrc, unlocks a lot of powerful customization. However, there is a substantial learning curve. When you manage your dotfiles using Fig, your development environment follows you across devices, operating systems and even between different shells. Any changes you make sync automatically. And, if you want, you can easily share your shell

aside: do you guys know of a Python-based TUI/prompt library that allows multi-line output? the idea is to be able to do what IDEs like vscode, or recently, Fig[1] do. they autosuggest, but at the same time include documentation at the prompt. prompt_toolkit[2] does not do that afaik. [1]: https://github.com/withfig/autocomplete [2]: https://github.com/prompt-toolkit

Sounds like they are actively working on adding support for Windows and Linux; https://github.com/withfig/autocomplete#does-fig-work-on-win...

Writing shell completions is a surprisingly tricky - especially for larger CLI tools or when you want to provide more advanced suggestions. Everything has to be done imperatively, usually as a shell script! It can get hairy quickly. As a point of comparison, see the difference between the git completions written in bash [1] vs the declarative equivalent [2]. [1] https://github.com/git/git/blob/master/contrib/completion/gi... [2] https://github.com/withfig/autocomplete/blob/master/src/git....

> In our timeline, maybe some file format could be standardized that describes the particular inputs and options a command takes, and e.g. shells would hook into it. Kind of like header files, but distributed either in a community repository or by each of the tools themselves. This sort of sounds like what we're working on at Fig. We've defined a declarative standard for specifying the inputs to a CLI tool and have a community repo with all supported tools: https://github.com/withfig/autocomplete Disclosure: I'm one of the founders

If you want to play around with writing more 'interesting' completions, check out Fig (https://github.com/withfig/autocomplete). You can write completions declaratively and use TypeScript to generate dynamic suggestions. Disclosure: I'm one of the founders.