Repository navigation
How can I specify which neovim config to use? #369
|
Hello, So I have a bunch of different config files ( I would like to be able to point kitty-scrollback to a lua file that's not my I was reading through nvim_args = parse_nvim_args(args) + (
'--cmd',
' lua'
' vim.api.nvim_create_autocmd([[VimEnter]], {'
' group = vim.api.nvim_create_augroup([[KittyScrollBackNvimVimEnter]], { clear = true }),'
' pattern = [[*]],'
' callback = function()'
f' vim.opt.runtimepath:append([[{ksb_dir}]])'
' vim.api.nvim_exec_autocmds([[User]], { pattern = [[KittyScrollbackLaunch]], modeline = false })'
f' require([[kitty-scrollback.launch]]).setup_and_launch([[{kitty_data}]])'
' end,'
' })')I think I could hack this a bit and point to a different config file but wanted to see if there was a better/built-in/recommended way. Thanks (this is bomb ass plugin btw !!! really useful) |
Replies: 3 comments
|
Yes, this is supported without patching For a single lightweight Lua config, pass Neovim's If that file does not load your normal package manager setup, make sure it can still find this plugin. The README's minimal example appends the plugin directory to require('kitty-scrollback').setup({
-- your scrollback-specific options
})If you want a full separate Neovim profile instead of one So for your case I would start with |
|
Thanks! @krotname answered it (thanks! 🙂). Check out the README https://github.com/mikesmithgh/kitty-scrollback.nvim#separate-neovim-configuration for additional info. |
|
oh wow y'all; I feel so dumb... I totally missed this in the README 😬 appreciate y'all! |
Yes, this is supported without patching
kitty_scrollback_nvim.py.For a single lightweight Lua config, pass Neovim's
-uthrough the kitten's--nvim-args:If that file does not load your normal package manager setup, make sure it can still find this plugin. The README's minimal example appends the plugin directory to
runtimepathand then calls:If you want a full separate Neovim profile instead of one
minimum.lua, useNV…