|
|
|
Show HN: Copilot Next Edit Suggestions in VS Code
(twitter.com)
|
|
4 points
by alexdima
498 days ago
|
|
Hi HN, long time reader here, working on VS Code since before it was called so. You probably don't know me, but among other things, I'm probably responsible for the silent eradication of mixed line endings from your code ;-). Please don't upvote https://github.com/microsoft/vscode/issues/127 I wanted to get your honest feedback on the new UX we've built for Next Edit Suggestions or NES for short. For the past few weeks, we've been doing, tweaking and redoing many things trying to get NES to feel right. But I think we can still improve it. The team would love if you could please try it out for a few minutes and give us some honest feedback (you need to sign in with GitHub, install the Copilot extension and enable `"github.copilot.nextEditSuggestions.enabled": true`). Please open issues at https://github.com/microsoft/vscode-copilot-release/issues or let me know in comments how it feels. Thank you! |
|
When I tried Cursor this feature blew my mind. Not enough to completely make the switch (Cursor annoyingly overrides some default keyboard shortcuts and settings from VSCode) but enough to make me miss it when I don’t have it.
I know it will probably require a few iterations to become its best version, but I’m glad it’s been worked on. For a time it felt like Copilot Chat got all the love but it’s useless to me.