mschrage

9 ms·

1. 31.▲
   by mschrage 4y ago

   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 ter
2. 32.▲
   by mschrage 4y ago

   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,
3. 33.▲
   by mschrage 5y ago

   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 po
4. 34.▲
   by mschrage 5y ago

   > 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 reposi
5. 35.▲
   by mschrage 5y ago

   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
6. 36.▲
   by mschrage 5y ago

   Writing shell completions is such a pain (and fish is still way ahead of zsh or bash). Btw if you like fish autocomplete, you might be interested in fig.io. We've spent a bunch of time making is super easy to add your own completions
7. 37.▲
   by mschrage 5y ago

   To clarify, a decent number of Fig users (not employees) have been running into this issue. We host our answers to common support requests on Github Discussions!
8. 38.▲
   by mschrage 5y ago

   kicks has such a fun & distinctive visual style. Came to comment that the design reminded me of https://www.kickscondor.com/ and now I understand why!
9. 39.▲
   by mschrage 5y ago

   Thanks for your insight here! We are still deciding the exact implementation, but completely agree - Linux is a challenge due to the heterogeneity of distros, window managers, compositors, etc. Our macOS approach might not work everywhere.
10. 40.▲
    by mschrage 5y ago

    Out of curiosity, do the scripts you write take options or arguments? Or are they generally just invoked directly?
11. 41.▲
    by mschrage 5y ago

    The aws-cli is a monster! This exactly the type of situation where we envision Fig being really helpful :)
12. 42.▲
    by mschrage 5y ago

    We totally agree! This is exactly where we want to take Fig. The autocomplete product is built using an API that extends terminals with visual apps and shortcuts. Using the same API, you can build an app that interactively displays photos o
13. 43.▲
    by mschrage 5y ago

    Thanks for the feedback :) If you run into bugs or gave any suggestions, run `fig issue` to quickly create a new Github issue!
14. 44.▲
    by mschrage 5y ago

    Currently, Fig only supports macOS.
15. 45.▲
    by mschrage 5y ago

    The current implementation of Fig is a native macOS app (Swift/ObjC) that exposes an API to access terminal specific information - edit buffer, working directory, current process, etc. On every platform we support, we'll implement
16. 46.▲
    by mschrage 5y ago

    These are all such cool projects. We took some early inspiration from TermKit! I think the tricky thing is that you need to switch terminal emulators in order to use the new features. We've tried to make everything as backwards compati
17. 47.▲
    by mschrage 5y ago

    Thanks Ramiro! Glad to hear you're finding Fig useful :)
18. 48.▲
    by mschrage 5y ago

    To get autocomplete working, you just need to install the macOS app. ( https://fig.io/hn ) These instructions only apply if you want to develop your own completion specs and are setting up the dev environment!
19. 49.▲
    by mschrage 5y ago

    No worries. We determine who is on your 'team' based on email domain excluding webmail domains, like gmail.com and hey.com. If there are a bunch of people at the same company using Fig, we'd probably reach out to understand w
20. 50.▲
    by mschrage 5y ago

    Autocomplete is just our first product. We've built an API that makes it possible to add visual extensions to any terminal. We want to expand into stuff like runbooks, UIs for deployment, internal infra, etc..
21. 51.▲
    by mschrage 5y ago

    Thanks! We currently work with the VSCode integrated terminal and will add support for Jetbrains IDEs, if possible!
22. 52.▲
    by mschrage 5y ago

    > Is the VC backing for another product and the CLI tool is just a PR thing? Autocomplete is our first product. The bigger vision that Fig can enable an ecosystem of terminal extensions. Here are some early prototypes we built [0] and he
23. 53.▲
    by mschrage 5y ago

    Just to clarify, the text you type into the terminal NEVER leaves your device. Fig does not store or collect this information. We send an event when you insert something using Fig's autocomplete, so we can get a sense for how frequentl
24. 54.▲
    by mschrage 5y ago

    The reason we suggest logging in with your work email is so that you can share shortcuts and completions for internal CLI tools with your team. We should probably add this explanation to the login page because I can see how this would be co
25. 55.▲
    by mschrage 5y ago

    Thanks for reporting this. This is definitely not the expected behavior. Would love to figure out what was going wrong. matt [at] fig.io
26. 56.▲
    by mschrage 5y ago

    Totally agree! The closer autocompletion lives to the source code, the better. We've started off writing completions by hand, but to scale we will need more robust integrations. For instance, aws has 100+ subcommands and thousands of o
27. 57.▲
    by mschrage 5y ago

    I honestly feel the same way. Once you use Fig, it feels like such an obvious idea. It didn't require new APIs or anything like that. As far as I can tell, no one tried it because to 10x the existing shell experience requires working a
28. 58.▲
    by mschrage 5y ago

    It looks like this is an issue with the completion spec for kubectl[0]! I'm not super familiar with k8s, so you wanted to help fix this (eg. writing the generator to list pods) that would be amazing! <3 [0] https://github.
29. 59.▲
    by mschrage 5y ago

    Thanks for the advice! We have a telemetry opt-out which turns this off. Currently, we would still send a daily ping so we can track retention, but after the feedback from HN, we'll turn this off as well.
30. 60.▲
    by mschrage 5y ago

    That's awesome to hear! Glad that everything is working!