mschrage

11 ms·

61.
by mschrage 5y ago
When you login with your work email, you can share shortcuts and completions for internal CLI tools and scripts with your team.
62.
by mschrage 5y ago
Fig does not "phone home" when you type! When you install Fig, we download the most up-to-date completions specs using the Github release API. (You can see them in ~/.fig/autocomplete). We got rate limited this morning (
63.
by mschrage 5y ago
That's how we think about the completion spec standard. It essentially is a type-safe DSL that describes the structure of CLI tools. It should be pretty easy to 'compile' a Fig completion spec down to zsh, fish, or bash. This
64.
by mschrage 5y ago
We're building out integrations with CLI libraries like cobra and oclif[0], so you can generate a Fig completion spec automatically the same way! Then it just comes down to the Fig popover UX. [0] https://github.com/wit
65.
by mschrage 5y ago
Autocomplete will always be free for individuals. We plan on charging for team-based collaboration, like private completion specs for internal scripts and CLI tools.
66.
by mschrage 5y ago
Fig already works inside of VSCode and VSCode Insiders! Also to clarify: we don't require node.js on the client. The completion specs are interpreted by the Fig macOS app. re: LSP. Super cool idea, are you imagining Fig autocomplete in
67.
by mschrage 5y ago
haha :) We actually send the name of the completion spec rather the initial token. In this case, it would be "dotslash".
68.
by mschrage 5y ago
For 'dangerous' commands, Fig requires you to press enter twice - once to select suggestion and insert it into the terminal and then again to execute it!
69.
by mschrage 5y ago
Did you use this link: https://fig.io/hn ? Let me know if you still can't get access. matt [at] fig.io
70.
by mschrage 5y ago
This is our approach! Nothing you type in the terminal is sent to Fig precisely to avoid this type of situation.
71.
by mschrage 5y ago
We started with macOS because I have a background in Swift development. Linux is definitely not an after thought to us! As for the telemetry concerns, I totally get that. We've tried to strike a balance and it seems like we've got
72.
by mschrage 5y ago
Windows is also in the works! The core autocomplete logic is easy to port over - the tricking thing is building out all of the OS level integrations! If you know any win32 devs, let me know :)
73.
by mschrage 5y ago
Thanks! Fig does a bunch of macOS specific hacks to find the cursor location, find link your tty session to a OS window id and determine your current edit buffer (the text you've typed). We then map then look for a corresponding comple
74.
by mschrage 5y ago
We do integrate with Hyper. Does Fig work in other terminals for you? Or are you potentially on the canary build of Hyper? (You can check in ~/.hyper.js)
75.
by mschrage 5y ago
This makes sense. Thank you for the feedback! :)
76.
by mschrage 5y ago
We just want people using Fig and enjoying it! That's our top priority. Don't feel bad at all about opting out of telemetry :)
77.
by mschrage 5y ago
Great to hear that everything is working. We were getting rate limited by Github when downloading the newest completion specs earlier - that might have been the issue as well!
78.
by mschrage 5y ago
Thanks so much for this! We've heard the feedback on telemetry loud and clear - definitely will rework this in the future.
79.
by mschrage 5y ago
We are planning on going cross platform! What distro / terminal emulator do you use?
80.
by mschrage 5y ago
We ask people to sign in with their work email, so you can share private completions for scripts and internal CLI tools with teammates. (You can use your personal email, if you prefer!)
81.
by mschrage 5y ago
This is something we definitely should add as a fallback when a Fig completion spec doesn't exist! The reason we created our own standard is because traditional shell autocomplete doesn't always provide metadata, like descriptions
82.
by mschrage 5y ago
Love to hear it! Autocomplete is free and always will be. Our plan is to monetize by charging for collaboration features at the team-level.
83.
by mschrage 5y ago
Hi HN! We’re Matt and Brendan, co-founders of Fig ( https://fig.io/hn ). Fig adds VSCode-style autocomplete to your existing terminal. We built Fig because of our own struggles in the terminal: we were tired of context switch
84.
Launch HN: Fig (YC S20) – Autocomplete for the Terminal(fig.io)
559 points by mschrage 5y ago|378 comments
85.
by mschrage 5y ago
Just joined! Also love the idea of a headless shell. Excited to chat more
86.
by mschrage 5y ago
One of the things that we discovered when trying to build out a declarative standard is that it can never encompass everything, precisely because many CLI tools implement their parsing logic imperatively! Our solution was to start off with
87.
by mschrage 5y ago
Glad you like the UI! Cobra and other CLI libraries, like oclif, can help you generate the skeleton of the CLI, stuff like subcommands, options, etc. (I'm in the process of writing the integration so you can generate a Fig completion s
88.
by mschrage 5y ago
First off, I've been a big fan of Oil shell for a while! Love the blog. :) Fig currently works with bash, zsh and fish. Since we are operating at the OS level rather than in the shell, we can get around the inflexibility of readline&#x
89.
by mschrage 5y ago
Yeah, we don't want this to be a '15th standard' situation [0] The biggest issue with traditional shell completions is that they are kind of tricky to build. Everything is defined imperatively and written as a shell script. W
90.
by mschrage 5y ago
The core focus right now is autocomplete, but this is definitely an area that we want to explore more in the future!

More ›