I don't really understand what's so different from the ZSH completions which I already have in my terminal but with no data leaving my machine?
[deleted]
Launch HN: Fig (YC S20) – Autocomplete for the Terminal
41–50 of 390 posts
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#42So the added benefit of Fig over completion provided by zsh/fish together with say Cobra is the “slick” ui and the (community?) sourced completion based on man pages etc without the apps themselves having to provide completion data?
I’m having quite some trouble understanding why I would add a tool that potentially sends all my terminal to the web…
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#43This seems really amazing. Please excuse my paranoia. Your privacy policy is very well written and easy to read. That's rare. However, Is there someway I can make Fig not send any data to anyone else? From what I understand, Fig does send telemetry information, but I'd like to be made aware of it before it asks me to give it "accessibility" powers. Also, while Fig may not send the data to anyone. Does this also cover…
Thanks! We do need to put in place a proper privacy policy. But we wanted to be transparent with how Fig uses your data (hence what we have currently). You can run `fig settings app.disableTelemetry true` to disable all telemetry except for one daily ping. You also make a good point: in our onboarding we should move our privacy information to before granting accessibility! We will make this more clear
I can't imagine that daily ping being worth the loss of trust from having a "disable telemetry" setting that doesn't really disable all telemetry. People who care about disabling telemetry will care about the daily ping, too.
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#44Earlier quoted context omitted.
Serious question: why didn't you just give a fake or temporary email address? That's what I do all the time.
They go as far as asking to validate the email with a code... That plus the fact that they do send data to their servers for some reason...
Do you consider your email to be all that private?
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#45Absolutely stunning - I've often wondered myself about why the terminal doesn't behave like this already, it just makes sense . My only worry would be this is obviously so great it's only a matter of time before Apple/Microsoft see the light and build something similar into their OS - however hopefully this happens via acquisition rather than what happened to Flux, Watson and Duet.
There was this rather janky IDE for Powershell, way before VSCode even existed, called Powershell ISE, that had very similarly looking autocomplete behavior in it's terminal window.
It's still around, I just used it today. I rarely use Powershell but when I do it helps (somewhat) to use this vs straight command line. I want to like Powershell but there is so much about it that just feels off as a long time bash script writer. I am admittedly a novice at Powershell though, so maybe it is just me.
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#46This seems really amazing. Please excuse my paranoia. Your privacy policy is very well written and easy to read. That's rare. However, Is there someway I can make Fig not send any data to anyone else? From what I understand, Fig does send telemetry information, but I'd like to be made aware of it before it asks me to give it "accessibility" powers. Also, while Fig may not send the data to anyone. Does this also cover…
Thanks! We do need to put in place a proper privacy policy. But we wanted to be transparent with how Fig uses your data (hence what we have currently). You can run `fig settings app.disableTelemetry true` to disable all telemetry except for one daily ping. You also make a good point: in our onboarding we should move our privacy information to before granting accessibility! We will make this more clear
I think you should reconsider daily pinging still taking place when the user explicitly asks to disable telemetry.
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#47Any plan to support vscode terminal?
Also, this experience really is great. Without knowing anything I was able to disable the "Menubar Icon" simply by guessing commands.
And to try for any constructive feedback, I personally don't like logo at all. It doesn't seem to make sense to me and is the reason for hiding the icon in the first place.
Feels like a window management icon like this: https://magnet.crowdcafe.com/
Great job, will follow this closely!
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#48I have been using zsh-autosuggestions [1] to achieve something similar, so seeing a new product that seems infinitely easier to configure and much more powerful is very.. heartening. I might not move over right this moment, but I'll be cheering you on.
PS: I read the fine print and I (and many others, I'm sure) would really, really like to pay some money for you to not send ANY telemetry data at all. Would be great if you kept this demographic in mind.
Congrats on the launch, and all the best!
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#49Iterm can do this for you as well
Re: Launch HN: Fig (YC S20) – Autocomplete for the Terminal
#50I don't really understand what's so different from the ZSH completions which I already have in my terminal but with no data leaving my machine?
Traditional shell completions are quite difficult to make. Many CLI tools have completions for subcommands and options, but not for arguments. Only the big CLI tools like `git` and `docker` have arguments completions (e.g. git push [remote] [branch]`.
Fig's declarative schema makes building the completions for subcommands, options and arguments very easy. This means we can support much more powerful autocomplete for many more CLIs.
Fig's standard format also makes it possible to suggest shortcuts for standard workflows (similar to aliases but more visual).
Finally, zsh and fish have good support for traditional autocomplete, but bash does not. Fig works the same across all shells (even when in an SSH session or a docker container).