Coming next: auto-complete for punch cards.
Show HN: Inshellisense – IDE style shell autocomplete
21–30 of 161 posts
Re: Show HN: Inshellisense – IDE style shell autocomplete
#22Great idea! Also terrifying :) Given how often I accidentally commit the wrong text in vscode, I shudder to think of the damage I could do with this on my shell, hah! What safety measures are there/could there be?
Type/command aware tooling is a night and day difference.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#23I wish they had written inShellisense in a more efficient programming language than TypeScript. I recall disabling bash_completion.sh on my computer some time ago due to its negative impact on the startup speed of each iTerm2 session and the delay it introduced when using the key for autocompletion. Before I disabled this feature, I consistently experienced delays of over 300ms between triggering autocomplete and rec…
This was the first thing I noticed, too. Why TypeScript? Is it: a) efficient enough, esp. compared to a Bash/Zsh/PWSH alternative, that spawning a JS interpreter for each autocomplete is no biggie? Is b) TypeScript just much more efficient than I thought? Or c) is TypeScript Microsoft's hammer, and everything looks like a nail?
Re: Show HN: Inshellisense – IDE style shell autocomplete
#24It’s really cool to see alternative implementations of IDE-style autocomplete in the terminal. Nice work!
Re: Show HN: Inshellisense – IDE style shell autocomplete
#25Great idea! Also terrifying :) Given how often I accidentally commit the wrong text in vscode, I shudder to think of the damage I could do with this on my shell, hah! What safety measures are there/could there be?
Generally, a destructive shell command prompts for approval. But I suppose overfumbly fingers could still cause grief. Type/command aware tooling is a night and day difference.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#26Great idea! Also terrifying :) Given how often I accidentally commit the wrong text in vscode, I shudder to think of the damage I could do with this on my shell, hah! What safety measures are there/could there be?
Generally, a destructive shell command prompts for approval. But I suppose overfumbly fingers could still cause grief. Type/command aware tooling is a night and day difference.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#27Earlier quoted context omitted.
Generally, a destructive shell command prompts for approval. But I suppose overfumbly fingers could still cause grief. Type/command aware tooling is a night and day difference.
I feel like I've trashed millions of files I shouldn't have with `rm` and trying to be clever with regular expressions.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#28Re: Show HN: Inshellisense – IDE style shell autocomplete
#29Co-founder of Fig here! Just want to say that I think this is awesome. It’s really cool to see alternative implementations of IDE-style autocomplete in the terminal. Nice work!
Re: Show HN: Inshellisense – IDE style shell autocomplete
#30I wish they had written inShellisense in a more efficient programming language than TypeScript. I recall disabling bash_completion.sh on my computer some time ago due to its negative impact on the startup speed of each iTerm2 session and the delay it introduced when using the key for autocompletion. Before I disabled this feature, I consistently experienced delays of over 300ms between triggering autocomplete and rec…
Don’t bring TypeScript into this. It is very possible to write sub 100ms procedures in TS, but an inelegant algorithm will be slow in any language, eventually.