Local leader key not active when open scm files about conjure HOT 7 CLOSED

Hi there! Sorry that you're having issues with this, it's almost definitely a timing related issue since it's intermittent. When and where do you configure your localleader key in your configuration? If you, temporarily, configure your local leader just before you manually initialise Conjure that'll tell us a lot. If the problem goes away then we know it's because sometimes the localleader key is being set after Conjure tries to initialise.

-- For example...
vim.g.maplocalleader = "\\"
require("conjure.main").main()
require("conjure.mapping")["on-filetype"]()

The other thing to try would be to remove the lazy loading entirely, just let Conjure load it's core which lazily loads the rest of the modules when they're required as you enter supported filetypes. You could even let Conjure's core load but configure it to only work with Scheme buffers

So you could set that list to just Scheme and see how that behaves / impacts your startup. The core of Conjure that loads and creates the filetype autocmd to load everything else is pretty tiny. The entire plugin is designed to lazily load all of it's internal modules as late as possible.

I'll still try to help you work out the issue with the current setup, but this is just another suggestion that might help you move forward.

from conjure.

Hi!

I try to use vim.g.maplocalleader = "\" like you said but it had no effect. I put lazy = false but I don't know if that's what you meant, it's also set to scheme only.

return {
	"Olical/conjure",
	ft = { "scheme" },
	dependencies = {
		{
			"PaterJason/cmp-conjure",
			config = function()
				local cmp = require("cmp")
				local config = cmp.get_config()
				table.insert(config.sources, {
					name = "buffer",
					option = {
						sources = {
							{ name = "conjure" },
						},
					},
				})
				cmp.setup(config)
			end,
		},
	},
	config = function()
		vim.g.maplocalleader = "\\"
		require("conjure.main").main()
		require("conjure.mapping")["on-filetype"]()
	end,
	init = function()
		-- Set configuration options here
		vim.g["conjure#debug"] = true
	end,
	lazy = false,
}

This is my current configuration, I discovered another way to activate the menu with \ I press <leader> g to show the menu and then the ESC key, from that moment on the \ key works again.

Regards,
Marcelo Módolo

from conjure.

Sorry for the delay, had a very busy week! That's very very odd, so \ doesn't work until you press <leader>g, then after that point you can use \ as your local leader no problem? This still feels like an issue to do with lazy loading to me, maybe not Conjure but maybe some other plugin that has some other config that loads later because of some filetype or event.

I'm afraid I can't think of any tips right now, everything looks okay to me in general, maybe try ruling out laziness by disabling globally? Just to check if it's a race condition somewhere? I've never run into this myself so I don't have much advice to offer 😞

from conjure.

Sorry for the delay, had a very busy week! That's very very odd, so \ doesn't work until you press <leader>g, then after that point you can use \ as your local leader no problem? This still feels like an issue to do with lazy loading to me, maybe not Conjure but maybe some other plugin that has some other config that loads later because of some filetype or event.

I'm afraid I can't think of any tips right now, everything looks okay to me in general, maybe try ruling out laziness by disabling globally? Just to check if it's a race condition somewhere? I've never run into this myself so I don't have much advice to offer 😞

Hi!
No problem, I've gotten the hang of it, and it's not such a bad thing.

Thanks,
marcelo Módolo

from conjure.

Hm okay then, I still think this is something local to your config somehow and not really something I can fix, I'm just sorry you're having to deal with it. Are you happy to close this issue for now and re-open if you can reproduce it with a minimal configuration that I can also reproduce with? Or if someone else turns up with the same issue of course.

from conjure.

Hm okay then, I still think this is something local to your config somehow and not really something I can fix, I'm just sorry you're having to deal with it. Are you happy to close this issue for now and re-open if you can reproduce it with a minimal configuration that I can also reproduce with? Or if someone else turns up with the same issue of course.

from conjure.

Hi!

I did a test on another lazyvim installation (another computer) and the behavior was the same, but it could be the result of other installed plugins. But it's no reason to waste time, otherwise everything works very well.

Thanks,
Marcelo Módolo

from conjure.