Picking a library

[octvs]

I'm trying to configure lazy loading via nixvim therefore I'm having a hard time which part of the stack is causing the issue, but it should be straight-forward for case of papis.nvim. Does papis.nvim only take the default-library into account? If so, is there a way to change this somewhere?

[jghauser]

Yes, unfortunately papis.nvim only supports one library. It should be somewhat simple to implement picking a non-default library though this isn't currently possible. Support for multiple libraries simultaneously would be more complex to implement (and I'm a bit weary of it since I'm hoping to switch to Papis' sqlite database once that's released.

[octvs]

Thanks for the response.

It should be somewhat simple to implement picking a non-default library though this isn't currently possible.

At least an env var to tweak it when it is necessary would have been more ideal
than changing papis config continously.

[jghauser]

I think there used to be an option to set the desired library, but that got dropped when I made this automatic 🤔. We could either do the env var route or just change the neovim config (though I guess given the nix setup that wouldn't be very useful?). However, switching back and forth between different libraries is unlikely to be enjoyable since it would require repopulating the database each time.

[octvs]

I think there used to be an option to set the desired library, but that got dropped when I made this automatic 🤔.

That is what I sought first, I guess it was under papis_python["dir"] key. I
was trying to search my way through and saw it at this issue.

We could either do the env var route or just change the neovim config (though I guess given the nix setup that wouldn't be very useful?).

Well my personal way of deploying the config is just a single case. But both
seem feasible solutions. Env var just popped to my mind since I often use such
overrides for per-project settings via direnv. Considering rest of the config
doesn't rely on env vars but lua config, I think it rather makes sense to stick
to lua.

However, switching back and forth between different libraries is unlikely to be enjoyable since it would require repopulating the database each time.

Oh yeah. In this context would it make sense to create the database with the
name of the library? But take my suggestions with a grain of salt, I'm alien to
the inner workings of this plugin.

[jghauser]

Hey! I just realised I never answered this message, sorry! You're right, creating dbs with the names of the libraries would be a good approach. However, it would still require some rather complicated refactoring because there might then be different neovim instances associated with different libraries that would have to know about each other. Because this part of the code base will hopefully go out the window once Papis supports sqlite, I don't think I'll tackle this for now. Once Papis does support sqlite I will make sure to implement this feature when I start directly relying on Papis' db.

[octvs]

Thanks for the response, this is all the reason more to wait for papis/papis#1007 to be finalized!