Re:Launch HN: Fig (YC S20) – Autocomplete for the Terminal
by ljm on Tuesday May 25, 2021 @04:49PM
(#27282445)
> generate the suggestions to know which commands to prioritize
What does 'prioritize' mean in this context? Other completion tools (like fasd) write command history to a local dotfile so they can build up knowledge of 'frecency'. This makes sense, it's no different to your ~/.bash_history file really. I wouldn't trust any single tool that tried to build a parallel history through an analytics integration.
Fig claims that it 'loads up once then remains entirely local', though, and it's adorned with an icon that suggests it remains offline.
What you're saying here seems to contradict that. If the tool is entirely local/offline, how is it phoning home with the commands you type? And does it send along the arguments you pass to the command if you happened to complete them?
What does 'prioritize' mean in this context? Other completion tools (like fasd) write command history to a local dotfile so they can build up knowledge of 'frecency'. This makes sense, it's no different to your ~/.bash_history file really. I wouldn't trust any single tool that tried to build a parallel history through an analytics integration.
Fig claims that it 'loads up once then remains entirely local', though, and it's adorned with an icon that suggests it remains offline.
What you're saying here seems to contradict that. If the tool is entirely local/offline, how is it phoning home with the commands you type? And does it send along the arguments you pass to the command if you happened to complete them?