Co-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!
I'm pretty sure this is just a wrapper for Fig.
Show HN: Inshellisense – IDE style shell autocomplete
71–80 of 161 posts
Re: Show HN: Inshellisense – IDE style shell autocomplete
#72Re: Show HN: Inshellisense – IDE style shell autocomplete
#73Earlier quoted context omitted.
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`
Or just add ‘echo’ in front: echo rm ... . Especially when the command is in a loop of some sort.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#74I wish I had something like this without it replacing the shell prompt with `>`.
I'd guess you could source it and then override the PS1 env variable with whatever prompt formatting you wanted.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#75Earlier quoted context omitted.
then what makes it better than withfig/autocomplete?
I downloaded fig, then immediately deleted it after it requested way too much access to my github account to even start. So... that's a big thing.
And this will deter me from ~~ever~~ trying Fig. :/
Re: Show HN: Inshellisense – IDE style shell autocomplete
#76[deleted]
Re: Show HN: Inshellisense – IDE style shell autocomplete
#77Earlier quoted context omitted.
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.
> It is very possible to write sub 100ms procedures in TS, […] I won’t dispute this statement since I currently lack the means to assess inshellisense. Would it be possible for you (or someone with a functional Node + NPM setup) to install inshellisense and share the actual performance figures? You could use a tool like hyperfine ( https://github.com/sharkdp/hyperfine ) for this purpose. As an attempt to test this my…
I'm pretty sure that the scripts generated by inshellisense are CRLF, and the carriage returns aren't recognized by unix shells.
You should be able to fix it with:
vi $HOME/.inshellisense/key-bindings.zsh -c "set ff=unix" -c ":wq"Re: Show HN: Inshellisense – IDE style shell autocomplete
#78Earlier quoted context omitted.
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`
As much as I can, I do a 'mv ... /tmp' instead of 'rm -rf'. It gets the files out of the way, and provides a way out if that's not what I wanted.
'/tmp' will eventually be cleaned by the OS so no (prolonged) space worries.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#79I 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…
As a user of this project, Typescript is 100% irrelevant, it's compiled to JS and is just a nodejs process and regular javascript at that point. You can go look at what's installed via `npm list -g`, find the path and notice there's not a single Typescript file in the build output.
I wish those aboard the TS/JS hate-train knew what they were even complaining about.
Re: Show HN: Inshellisense – IDE style shell autocomplete
#80For those who haven't read the code:
This reuses Fig.io's internal completion engine to actually get the job done.
Because of that, it forces the language choice of Typescript, and the heavy lift is done by Fig's engine.
I hope the OP continues with the work and improves it. I was looking forward to trying Fig on Linux. This sounds like a step towards that.