I can’t debug .net in cursor and the UI throws me off so I have to keep opening it… getting the answer… close it… go back to VSCode… Does this bother anyone else ?
cursor decided to go the “let’s just fork it” route instead making all manner of weird issues arise, but maybe necessary?
VSCode extensions have very limited control over the UI of the editor
Our Command-K and Copilot++ features aren’t possible as extensions. Same for much of what we want to build in the future!
I can understand that. Is there a reason why it doesn’t let us use the CMD+I for Copilot’s inline? is it a limitation of the fork? I still prefer Cursor’s CMD+K (and I’m really liking Copilot++ so far); I’m just curious.
then how come all the others have a plugin? (phind, cody, cosine, copilot… etc…)
Copilot can do the ctrl-k inline… and others you can highlight and rt click
and copilot++ im not sure what that is… but anyways thats my number 1 request be far … I don’t want to learn a fork of vscode… I like my vscode