vim 2018-12-07 | Slack Archive

hkupty15:12:04

Hey folks, quick poll about acid.nvim. React with the appropriate response: Would you like using acid through a lua API? 👍 - Yes, please 👌 - I don't care, as long as I can use it 👎 - No, Python/VimL is much better 😕 - I don't even know what acid.nvim is 😒 - I don't care, I use {fireplace,vim-iced,something else} Also, please DM me or respond to this if you have suggestions and/or complaints about acid. Thanks in advance!

👌 8

😕 28

devth20:12:39

i wasn't able to get acid.nvim working when i tried it a few weeks ago (i had it working in the past). let me try again. i think i'm ready to move on from fireplace at this point

devth20:12:12

i don't understand the implications of moving to lua. would that mean we can't configure it in init.vim?

hkupty22:12:06

It will be configured through lua. That can happen in the init.vim through the :lua command , but most importantly, it'll allow it to be seen as a library for other plugins and customization from the user.

👍 4

dave15:12:22

@ingvij what would be the user impact there? like, would i need to use lua to configure the plugin, or what?

hkupty16:12:31

#Also sent to the channel

That's correct. Same thing as in iron.nvim, you'll use lua to configure it.

dave16:12:13

interesting

hkupty16:12:31

replied to a thread:@ingvij what would be the user impact there? like, would i need to use lua to configure the plugin, or what?

That's correct. Same thing as in iron.nvim, you'll use lua to configure it.

2018-12-07

Channels