Configuring mini.clue #2469
Unanswered
rbpatt2019
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm currently migrating my nvim setup from a manually maintained
Lazy.vim
config to a nixvim/mini.nvim setup, and I've stumbled on a challenge that has me absolutely stumped. When I enablemini
's plugin, I then enable modules within that. Currently, I'm only using 3 modules: mini.clue, mini.files, and mini.starter. If I enable mini.clue by itself, the clue module works exactly as intended in all cases (hint window pops up). When all 3 are active, mini.clue behaves correctly for any file I open from the command line (nix run .# -- test.txt
) or through normal commands (:e test.txt
in vim), but does not trigger for any file opened frommini.files
ormini.starter
.I originally thought this was an issue with
mini.nvim
, but when I replicate my minimal nix setup in standard lua and run a normal nvim instance withmini.nvim
installed, everything works as expected. This leads me to suspect that how configs are sourced/created in nixvim is doing something mini.nvim isn't expecting.I'm working with the standalone usage, and have
config
set as below. An insights would be greatly appreciated!nixvim config
config = {
globals.mapleader = " ";
globals.maplocalleader = ";";
keymaps = [
# Files
{
mode = "n";
key = "e";
action = "lua MiniFiles.open()";
options = {
desc = "File Browser";
};
}
];
plugins.mini = {
enable = true;
};
}
Really loving the tool!
Beta Was this translation helpful? Give feedback.
All reactions