-
Notifications
You must be signed in to change notification settings - Fork 36
Unknown function: dist#ft# FTVB #91
Comments
I've been having the same issue, this may be a rough workaround but I managed to avoid this error by using the following configuration: local filetype_ok, filetype = pcall(require, "filetype")
if not filetype_ok then
vim.api.nvim_command([[echoerr "Error while loading filetype.nvim"]])
return
end
filetype.setup({
overrides = {
extensions = {
bas = "basic"
}
}
})
-- Do not source the default filetype.vim
vim.g.did_load_filetypes = 1 |
I was just coming to report the same error, since I finally took the time to figure out what was breaking. I was able to open javascript files just fine, but typescript or .sh files were where I was getting the errors. I did try the solution suggested by @Penaz91, and I'm not getting errors for *.ts files anymore, but I am still getting them for *.sh files |
Neovim removed the flie that defined these functions in neovim/neovim@042eb74. The plugin should be updated to use the new filetype detection functions. |
I've got the same issue since a couple of weeks.
Is only to get rid of the error but does not solve any highlighting or code completion issues. |
especially if you pair it with auto-session plugin, you get error everytime it tries to restore session |
I get the same issue trying to open .html files. I found a temporary solution to add line: ["html"] = "html", to mappings/extensions.lua file. This seem to work with other currently broken extensions as well. Highlighting and autocompletion works for me. This is probably just the same answer as above, I'm not very into lua. |
FWIW, newer versions of nvim have their own "filetype lua script" integrated which can be activated as follows:
You can see more here: https://neovim.discourse.group/t/introducing-filetype-lua-and-a-call-for-help/1806 |
Adding to @Penaz91's comment, if you're using Nvim v0.8+, |
i am getting this error on opening
.bas
filefull error
The text was updated successfully, but these errors were encountered: