Live data from Hacker News

Show HN: Inshellisense – IDE style shell autocomplete

github.com

21–30 of 161 posts

Re: Show HN: Inshellisense – IDE style shell autocomplete

#22

Great 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

#23

I 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?

I tend to think since VSCode plugins are javascript all new tooling from Microsoft seems to be written in typescript. As a non front end dev though `npm install` is an instant turnoff for me.

Re: Show HN: Inshellisense – IDE style shell autocomplete

#25

Great 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.

Generally? Do you have examples in mind? The ones I think of are destroy first and ask questions only if told to do so: mv cp rm redirection tee

Re: Show HN: Inshellisense – IDE style shell autocomplete

#26

Great 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.

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

#27
post #26

Earlier 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.

I've done this enough times I use `ls` first, then `rm`

Re: Show HN: Inshellisense – IDE style shell autocomplete

#28
post #4

Earlier quoted context omitted.

Did you check the page? It's MIT-licensed and isn't about GPT or text generation. It's Intellisense, for the shell.

then what makes it better than withfig/autocomplete?

That’s what it’s based on.

Re: Show HN: Inshellisense – IDE style shell autocomplete

#30

I 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.

100ms is a long time to wait for each completion suggestion.
Post reply on HN