Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed: When todo-comments.nvim as optional and report an error #129

Merged
merged 1 commit into from
Oct 2, 2022
Merged

fixed: When todo-comments.nvim as optional and report an error #129

merged 1 commit into from
Oct 2, 2022

Conversation

yibuma
Copy link
Contributor

@yibuma yibuma commented Sep 16, 2022

When todo-comments.nvim is optional, the first time it is used vim.defer_fn does not block and returns immediately, causing later code to read config.options as nil.

…rst time you use it.

When `todo-comments.nvim` is optional, the first time it is used `vim.defer_fn` does not block and returns immediately, causing later code to read config.options as nil.
@yibuma
Copy link
Contributor Author

yibuma commented Sep 16, 2022

How to reproduce.
Using packer.nvim configuration

-- Lua
use {
  "folke/todo-comments.nvim",
  requires = "nvim-lua/plenary.nvim",
  config = function() require("todo-comments").setup {} end,
  cmd = { 'TodoTelescope' },
}

The first time you execute :TodoTelescope you get an error.

@Weissle
Copy link

Weissle commented Oct 2, 2022

This commit may fix this issue. #138

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants