Skip to content
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

Integration with ivy/helm #24

Open
arnavsharma93 opened this issue Dec 29, 2018 · 6 comments
Open

Integration with ivy/helm #24

arnavsharma93 opened this issue Dec 29, 2018 · 6 comments

Comments

@arnavsharma93
Copy link

First of all, thank you for the feature rich package.

I was curious if you had integration with ivy/helm in the future roadmap. It would be possible to do away with the buffers and power the package through actions.

@danielfm
Copy link
Owner

I'm not particularly familiar with ivy nor helm, so can you give a more detailed explanation of how such integration would work?

Thanks for the suggestion.

@arnavsharma93
Copy link
Author

Ivy/Swiper/Counsel is like a completion UI where object at point can be an argument to an action. Action is a function mostly. Completion can be done using regex, fuzzy matching etc. Helm is something similar.

Here, instead of putting the search result in a buffer, it can be fed to Ivy as candidates. Actions can be configured on candidates like select artist, select album, select song, add to queue etc. The queue itself can be powered through occur - allowing rearranging, removal, addition etc. Ivy can be configured to use virtual buffers removing the need to create search result buffers.

@danielfm
Copy link
Owner

Sounds nice. I don't promise anything, but I'll take a look at ivy when I get the chance.

@jkdufair
Copy link
Contributor

@danielfm @arnavsharma93 I'm an ivy/counsel/swiper user. I've been digging around how to do ivy integration. Would it be best to have this package offer ivy completion instead of the existing buffers? As an alternative via configuration?

@cole-brown
Copy link

Definitely don't force it, @jkdufair. Not everyone uses ivy/counsel/swiper, helm, or whatever. I'm currently using helm instead of ivy myself.

So I'd vote it as an alternative via configuration. Or some do it via another package that hooks into the original and alters it to work with ivy/helm.

@vilst3r
Copy link

vilst3r commented May 16, 2020

@arnavsharma93 I've managed to get a working implementation of this feature in the PR referenced.

@cole-brown Thank you for your input to this issue, in my PR I've integrated helm through configuration of a flag variable after reading your comment.

As for Ivy, I'm not particularly familiar with it so I didn't attempt to integrate it but if someone out there is & willing to contribute to this change then that'd be a great addition to this package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants