Closed mkubasz closed 3 years ago
Put vim.g.coq_settings
directly in init.lua
instead.
IDK about the vim.schedule
stuff. Why is that necessary?
It was necessary, not anymore.
Because I only accounted for classic plugin mangers like vimplug
and stuff, didnt know packer
existed.
it was a temp work around to let packer
people use coq
before I figured out how to do things "properly"
@ms-jpq Maybe you can share with properly solution :) I tried to put into init this part with settings but nothing happens.
move local coq = require('coq')
below vim.g.coq_settings =...
thanks
sorry im in coding mode rn and did read your ticket, i thought it was gonna be annoying to fix, but its super easy lol
ill add it in the FAQ
The issue is closed, but I thought I'd add this comment for other people's benefit trying to use coq with packer.
An easy way to ensure that the vim.g.coq_settings
is called before the local coq = require('coq')
is to add the vim.g.coq_settings = ...
to setup
event in packer and require('coq')
in config
event.
Example:
setup = function()
require('plugins.nvim-coq').setup() -- has vim.g.coq_settings
end,
config = function()
require('plugins.nvim-coq').config() -- has require('coq')
end
Hi, I just want to handle auto start, I founded closed issue with vim.schedule, but is not working.
And in packer
I will be glad for some hints :)