Feature Description

I share my nvim configuration into an offline environment via a read-only filesystem (security setup where I work). This means in the offline environment, ~/.local/share/nvim is a sym-link to the read-only filesystem. This is how I get all my plugins across. But blink wants to open the frecency db in ~/.local/share/nvim/blink/cmp/fuzzy.db, and throws an "unable to init frecency db" error.

$ ls -d ~/.local/share/nvim
lrwxrwxrwx /home/mylesp/.local/share/nvim -> /shared/readonly/filesystem/blah/blah/.local/share/nvim/

fuzzy.implementation.init_db(vim.fn.stdpath('data') .. '/blink/cmp/fuzzy.db', config.use_unsafe_no_lock)

Isn't the state stdpath more appropriate for write data? I hacked data to state and it's working fine.

Can you at least add this as a setable option if you don't change the default?

Thanks!