You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues of plugins related to this issue
Neovim version (nvim -v)
v0.10.0-dev-836+g6d93bdd45
Operating system/version
Mac Ventura 13.5
Describe the bug
When opening a file that has a modeline, strange things happen when opening/closing the command line and triggering completion. Moreover, I see the following error in my debug logs:
Error detected while processing nvim_exec2()..modelines[1365]..OptionSet Autocommands for "filetype":
E12: Command not allowed in secure mode in current dir or tag search
Executing OptionSet Autocommands for "*"
autocommand <Lua 310: ~/.local/share/nvim/lazy/dropbar.nvim/lua/dropbar.lua:70>
Disclaimer that I've been able to reproduce the issue when using noice and dropbar.nvim. Given the above stack trace I originally created an issue there, but I was advised to report it to noice instead.
Steps To Reproduce
Save the configuration file above under minimal.lua.
In the same directory, create a file with the following content:
A text file.
vim:tw=78:ts=8:sw=2:et:ft=help:norl:
Open Neovim with nvim --clean -u minimal.lua test.txt
Type :h he<Tab> (trigger command line autocompletion).
Notice how Noice's command line get's stuck.
Exit Neovim with qa. Repeat step 4 but opening Neovim with nvim --clean -u minimal.lua test.txt -V10mynvim.log
Open mynvim.log and search for Error.
Notice the errors about incorrectly processing autocommands.
Expected Behavior
For neovim to behave normally.
Repro
-- DO NOT change the paths and don't remove the colorschemelocalroot=vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .reprofor_, nameinipairs({ "config", "data", "state", "cache" }) dovim.env[("XDG_%s_HOME"):format(name:upper())] =root.."/" ..nameend-- bootstrap lazylocallazypath=root.."/plugins/lazy.nvim"ifnotvim.loop.fs_stat(lazypath) thenvim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
{ "folke/noice.nvim", dependencies="MunifTanjim/nui.nvim", config=true },
{ "Bekaboo/dropbar.nvim", config=true },
-- add any other plugins here
}
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
The text was updated successfully, but these errors were encountered:
Did you check docs and existing issues?
Neovim version (nvim -v)
v0.10.0-dev-836+g6d93bdd45
Operating system/version
Mac Ventura 13.5
Describe the bug
When opening a file that has a modeline, strange things happen when opening/closing the command line and triggering completion. Moreover, I see the following error in my debug logs:
Disclaimer that I've been able to reproduce the issue when using
noice
anddropbar.nvim
. Given the above stack trace I originally created an issue there, but I was advised to report it tonoice
instead.Steps To Reproduce
minimal.lua
.nvim --clean -u minimal.lua test.txt
:h he<Tab>
(trigger command line autocompletion).qa
. Repeat step 4 but opening Neovim withnvim --clean -u minimal.lua test.txt -V10mynvim.log
mynvim.log
and search forError
.Expected Behavior
For
neovim
to behave normally.Repro
The text was updated successfully, but these errors were encountered: