Errors from BufEnter/BufWinEnter Autocommands on opening after installing trouble about trouble.nvim

[folke]

Yeah, you should definitely not do that. Most people use a Lua config folder for that. /Lua/config/...

Plugins will definitely break the way you do it right now, since you're overwriting their global namespace.

[folke]

I don't see this error. Could you open that runtime file and post what's on that line (and surrounding lines)?

What commit is that Neovim built?

[nkhlmn]

Code is below. I'm on 0.5.0 stable installed using homebrew on macos.

1075
1076   if resolve_optional_value(config.update_in_insert) then
1077     M._clear_scheduled_display(bufnr, client_id)
1078   else
1079     local mode = vim.api.nvim_get_mode()
1080
1081     if string.sub(mode.mode, 1, 1) == 'i' then
1082       M._schedule_display(bufnr, client_id, config)
1083       return
1084     end
1085   end
1086
1087   M.clear(bufnr, client_id)
1088
1089   diagnostics = diagnostics or M.get(bufnr, client_id)
1090
1091   vim.api.nvim_command("doautocmd <nomodeline> User LspDiagnosticsChanged")
1092
1093   if not diagnostics or vim.tbl_isempty(diagnostics) then
1094     return
1095   end
1096
1097   local underline_opts = resolve_optional_value(config.underline)
1098   if underline_opts then
1099     M.set_underline(diagnostics, bufnr, client_id, nil, underline_opts)
1100   end

[nkhlmn]

Looks like this was only happening when I have my config for this plugin in a lua/trouble.lua file. Renaming this file to something else fixes it. I do this with other plugins without any problems (e.g. I can have a lua/telescope.lua file). Not sure if you consider this a bug or not.