-
Notifications
You must be signed in to change notification settings - Fork 74
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
[Request] Integration with vim-airline #64
Comments
Rather than checking " check if VM is active
return exists('b:VM_Selection') && !empty('b:VM_Selection') I'm sure it's possible to achieve airline integration, but I don't know how since I don't use it. I'll add a function that returns some infos that can be useful for statusline integration. |
You can call a new function now, it returns a dictionary with useful infos for a statusline. You should be able to build a statusline section with those. If you have more questions you can reopen this. |
@mg979, What does the status key in the |
It's a bit outdated, it's |
Yes, I saw this, but was not sure because of the |
It's |
Oh, sorry, for unknown reason I thought it was |
Hi, It seems like the wiki is missing for statusline integration. I want to integrate with lualine. Could you please help with that? |
You can use built-in statusline, change this value to 3 if it gets overwritten. Or you can use the aforementioned function inside lualine, but I can't help you with that. |
Your wiki shows how to integrate with lightline.
I'd love to see this integrated with vim-airline, to support showing both cursor and extended mode. I see
g:Vm.is_active
can be used to show in lightline that the plugin is active. How would one differentiate further, to tell between cursor and extended modes?Integration would probably require changes in vim-airline code. Once I know how to differentiate between cursor and extended modes, I can open an issue with vim-airline and see if they'll add support for it.
EDIT: Ahh, I see.
g:Vm.is_active
then useg:Vm.extend_mode
to differentiate. Opened an issue with vim-airline asking for support.Up to you if you want to close this, help contribute to vim-airline, or leave this open for a while to see what they do.
The text was updated successfully, but these errors were encountered: