exrc.vim VS persistence.nvim

exrc can enable untrusted arbitrary execution. See https://github.com/ii14/exrc.vim that tries to mitigate this.

'exrc' option or https://github.com/ii14/exrc.vim

Yeah, here's my plugin that does that: https://github.com/ii14/exrc.vim

:set exrc and and create .exrc file in your project directory with your project settings, or use a plugin like https://github.com/ii14/exrc.vim or https://github.com/jenterkin/vim-autosource

I did basically the same thing, but without recursive lookup: https://github.com/ii14/exrc.vim

https://github.com/ii14/exrc.vim for local vimrc. Basically a reimplementation of the 'exrc' option that keeps track of file hashes, so you don't evaluate anything malicious, without the limitations of 'secure' option.

persistence.nvim for using session management which is useful

i use persistence.nvim plugin, and i map the commands on my dashboard so i can open my last session

I've been using vim sessions for a while now. Sessions can have their own configuration files and that's what I use for projects. For this to be actually convenient you'll need plugin like persistence.nvim to handle the sessions themselves (or make your own workflow).

I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.

persistence.nvim: Small session manager. I use some of its functions to also manage project local configs. It is because of this plugin I can use language servers the way I want.

persistence.nvim * Automatically save active session to a configurable directory * API to load most recent or current session based on cwd * No direct support for a telescope picker but could probably be setup with vim.ui.select()

yeah, I was planning on shimming this functionality out to another plugin. sessions have little to do with a startup gui imo. i mention in the docs using something like https://github.com/folke/persistence.nvim