Replies: 8 comments 16 replies
-
JetBrains |
Beta Was this translation helpful? Give feedback.
6 replies
-
vim / neovim / terminal |
Beta Was this translation helpful? Give feedback.
4 replies
-
visual studio |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ghidra (reverse engineering app) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We recently decided that the approach to integrating Cursorless into other IDEs need not be a one-size-fits-all approach. There are three possible approaches:
In all cases, the Cursorless core maintainers will be responsible for the part of the Cursorless inside the “interface boundary”, ie the Cursorless LSP server, the Cursorless NPM package, or the Cursorless wasm. The IDE-specific code that interacts with the Cursorless interface will be maintained by someone who is responsible specifically for the integration with the given IDE.
Given that we are considering three possible ways to integrate, we have decided not to go with a waterfall approach where we invest in picking one approach, implementing it, then letting IDE-specific contributor build the client.
Instead, we’d like to work closely with a couple IDE client maintainers so that we can figure out which approach makes the most sense for their IDE. If you’re interested in being one of those IDE client maintainers, and have some capacity to hack in the next couple months; leave a message in this discussion, and then drop into a meet-up so we can get started!
See the repos in https://github.com/cursorless-everywhere/ for some of the current work
Beta Was this translation helpful? Give feedback.
All reactions