Setting up plugins with post-install scripts

[redbeardymcgee]

For Firenvim, the setup process is rather unique compared to all the other plugins I've ever installed. There is a post-install script executed by ":call firenvim#install(0)", but otherwise it just autoloads itself as necessary and doesn't require any special lazy-load handling AFAICT. For now, I'll just run this manually from an existing nvim instance.

Is this something that nixCats can gracefully handle in some way? I think it could, but I'm not sure if an approach is documented anywhere.

[BirdeeHub]

Well, usually you would make a derivation which runs that. You would use the default plugin overlay thing or mkPlugin, and then use overrideAttrs to add the step to postInstall hook probably.

Does pkgs.vimPlugins.firenvim not work though? I havent tried the plugin personally, but make sure pkgs.vimPlugins.firenvim doesnt work before trying to build it yourself.

[redbeardymcgee]

the nixpkgs plugin works, but it doesn't call the install script.

[BirdeeHub]

actually, can you just call it? It actually looks like it might not modify its own directory. It looks like it gets a list of browsers and stores them in a data dir, or modifies some browser data dirs. You might just be able to call it at runtime

[redbeardymcgee]

Yes, the approach I mentioned in the original post was that I'll run the post-install setup manually. It works fine, but is something I would like to eliminate from the setup process.

[BirdeeHub]

Well, you could add some lua code to your config which checks existence of a file, runs it, and makes a file somewhere saying it has been ran (or if you can find one of the files it adds, use that)

If you wanted to add it to the plugin itself, you could use .overrideAttrs to add a file to $out/plugin/something.lua in the postInstall hook or something, which will run at runtime and do the same thing?