docopt VS autocomplete

Symfony Console closely follows the well-established docopt conventions. Docopt, based on longstanding conventions from help messages and man pages, ensures a consistent and intuitive interface for describing a program's interface. Symfony Console's adherence to docopt conventions guarantees that your command line tools maintain a standardized and predictable user experience, simplifying development and user interaction.

You probably already know, but just in case you don't, you might read about http://docopt.org/ It seems to me a lot of your usage ideas could be refinements of / tooling around docopt-style interfaces.

http://docopt.org/

Not quite what you asked for, but close: type example invocations to generate the CLI, and just pull the arguments from a dictionary at runtime.

I've been using docopt to handle CLI arguments for years now.

http://docopt.org/

If you aren't averse to using a third party package, on my personal projects I always found https://github.com/docopt/docopt to be nice.

You can kill 2 birds with one stone by documenting your scripts while also providing the argument structure / parsing.

As for the implementation differences, complgen uses a trivial DSL that’s everybody is already familiar with more or less because it’s a slightly more rigorous version of what tools usually spit out when you do command --help (projects like docopt even use that for command line arguments parsing). Those happen to be regular languages and therefore can be represented as a Deterministic Finite Automata. complgen compiles the grammars to DFAs, minimizes the DFA and spits out shell-specific shell completions scripts that simply walk the DFA to match and complete the current input.

The current completion system has a list of rules of which completions to use at which time. It's purposely simple to make it as flexible as possible. The current things I'm planning is a derive macro like what clap has to generate these rules. I'm also considering introducing a plugin that let's you write rules in the format of docopt

For anyone unfamiliar, docopt is an established standard for specifying arguments in a script’s doc string. I use it for Python and it’s lovely. You’re going to write a docstring with examples anyway, why not make them functional?

http://docopt.org/

I like http://docopt.org/ a lot. You seem like someone who might have opinions on that.

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!

8. Fig

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?

How is this different than https://fig.io/?

AWS CloudWatch Evidently The worst. No comment. AWS seems to perpetually lack a good DX for developers. It appears that they don't recognize or continually undervalue the importance of roles other than engineers, such as Product Managers or Designers. Very disappointing. However, AWS has recently acquired Fig, so looks like they're now pursuing an acquisition strategy instead. Let's see how it turns it out, and let's hope they don't ruin Fig, since it's such an useful tool.

slightly tangential, but where do people get awesome landing pages like linear(https://fig.io/. has similar landing page) etc. Do they build them in-house or buy templates somewhere? Many of the recently launched YC companies have awesome landing pages. eg. https://automorphic.ai/,

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