582 karma · joined December 17, 2009
If there's a post about Zig, you don't see people saying how they don't use Zig.
It's hard to understand how any other way is usable. If you have a dozen concurrent shell sessions, some running a long running process for example, and you had to restart one of them, you wouldn't be able to just Ctrl-C and go to the previous command. For me it's way better shell sessions live their own life but the history is accumulated to a single pool.
Use the @ thing to prod it read some relevant files for context (kind of like with Aider)
That's what the body of the commit message is for.
It works over UDP so it doesn't even send any acknowledgement or error response to unauthenticated or non-handshake packets.
https://opensource.stackexchange.com/questions/4008/can-i-us...
https://opensource.stackexchange.com/questions/5188/software...
https://github.com/disable-gatekeeper/disable-gatekeeper.git...
CopilotChat.nvim solves this somewhat elegantly for neovim, providing a streamlined UI to interact with an LLM in a way that allows accepting suggested diffs to your currently open buffer. The problem however is that it only works with GitHub's Copilot chat, as the name suggests. Not sure how well Copilot stacks up against gpt-4o for example but I'd imagine not that well.
edit: Quick demo of CopilotChat.nvim: https://github.com/raine/ghtool/assets/11027/e8d5820b-eafb-4...
This is pretty much the kind of UI I'd want for interacting with LLMs, aside from the typical Copilot style ghost autocomplete.