4 ms·

Why does the emulator have to do this? Can’t it be a plug-in for bash/zsh/whatnot? Those already support tab completion. It could even be a cli: prompt “comman

by spockz 2y ago

Why does the emulator have to do this? Can’t it be a plug-in for bash/zsh/whatnot? Those already support tab completion. It could even be a cli: prompt “command that you want it to generate”. Then inspect it and run it. If you are feeling very lucky type “$(prompt “command you want to run”)” and poof it executes. Why does this need to be in one of the most privileged apps on my machine?

jedberg 2y ago
It certainly could be built into the shell. But the people who did it first make a terminal. No reason it couldn't be ported to the shell though.
tzs 2y ago
> Why does the emulator have to do this? Can’t it be a plug-in for bash/zsh/whatnot? I've no interest in using it because I'm a cheap bastard and am not going to pay $20/month for a key, but if I were going to use it I'd want it in the terminal emulator. If it were a shell plugin I'd have to install it in my shell on my Mac, the shells on my two Raspberry Pis, the shell on my Amazon Lightsail instance, and the shells on the half-dozen or so servers at work that I regularly ssh to from home. Oh, and also the shells in the Linux VMs I run my work test environment in.
- Xelynega 2y ago
  Why can it not be a plugin for the terminal emulator? I understand why people don't like that "integrates with third party LLM services" was just added as a core feature to their terminal emulator(which are typically very minimal applications when it comes to business logic). I can also see the usefulness of having it in the terminal emulator, but I think most people's reaction comes from the confusion of it being included in the core code instead of an extra module you download. This whole things feels like if vim added a copilot integration into the core app. It make a lot more sense as an additional download than core functionality.
- bakkoting 2y ago
  API keys are unrelated to the $20/month product, and the keys are pay-as-you-go. The newest model is $15 per million tokens of output, which is to say, you would be extremely hard-pressed to spend $20/month on the API.

by spockz 2y ago

jedberg 2y ago

It certainly could be built into the shell. But the people who did it first make a terminal. No reason it couldn't be ported to the shell though.

tzs 2y ago

> Why does the emulator have to do this? Can’t it be a plug-in for bash/zsh/whatnot? I've no interest in using it because I'm a cheap bastard and am not going to pay $20/month for a key, but if I were going to use it I'd want it in the terminal emulator. If it were a shell plugin I'd have to install it in my shell on my Mac, the shells on my two Raspberry Pis, the shell on my Amazon Lightsail instance, and the shells on the half-dozen or so servers at work that I regularly ssh to from home. Oh, and also the shells in the Linux VMs I run my work test environment in.

Xelynega 2y ago
Why can it not be a plugin for the terminal emulator? I understand why people don't like that "integrates with third party LLM services" was just added as a core feature to their terminal emulator(which are typically very minimal applications when it comes to business logic). I can also see the usefulness of having it in the terminal emulator, but I think most people's reaction comes from the confusion of it being included in the core code instead of an extra module you download. This whole things feels like if vim added a copilot integration into the core app. It make a lot more sense as an additional download than core functionality.
bakkoting 2y ago
API keys are unrelated to the $20/month product, and the keys are pay-as-you-go. The newest model is $15 per million tokens of output, which is to say, you would be extremely hard-pressed to spend $20/month on the API.