-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support denite as selector UI #289
Comments
Just bumping this. If one of the maintainers can lead me in the right direction, I'd be willing to look into putting together a PR for this. |
@nosami ? |
Sorry, I haven't worked in C# or vim for a long time now. @thinca is the maintainer |
Sorry just went off who had the most commits. Thanks for pinging the right person! |
PR is welcome! |
@tulsileathers I'm not a maintainer but I've been tinkering with OmniSharp-vim for a while. I've also just recently been updating some of the fzf/ctrlp/unite integration code to update the plugin to use 'v2' of the roslyn /codeactions functionality which is far superior (see #342). As I said in that PR, I don't have any experience with unite or denite. If you do have experience with unite, perhaps a good place to start would be to take a look at the PR and see if you can get the existing unite functionality to use 'v2' instead of 'v1', as I've done for fzf and ctrlp? Adding denite as a 4th option after that shouldn't be too complicated. |
@tulsileathers are you still interested in having a look at this? Previous PRs are now merged, and I worked out the unite stuff so that's up-to-date too. If you want to have a go at adding denite now, that'd be great! |
Shougo new plugin replacing Unite is Denite, from the Readme:
Unite.vim is anything.el like interface for Vim. But the implementation is ugly and very slow. Denite.nvim resolves unite.vim problems. It is 10 times faster than unite.vim.
It would be nice to be able to choose it as the selector UI for Omnisharp
The text was updated successfully, but these errors were encountered: