Open sandeep-ad opened 1 year ago
I have the same issue. Some file types work, others don't. File types that don't work are, e.g.:
I am also facing this issue (with sh
files). Was anyone able to find the cause?
Uninstall the plugin. ¯\(ツ)/¯ From what I can tell, it's not needed in newer versions of vim/neovim any more. Maybe someone can confirm?
Uninstall the plugin. ¯_(ツ)_/¯ From what I can tell, it's not needed in newer versions of vim/neovim any more. Maybe someone can confirm?
This is indeed the right solution for this issue. Uninstall filetype.nvim and set vim.opt.filetype = "on"
in your config.
I uninstalled the plugin and added filetype=on, now the behaviour is when I open the main.tf it does not show syntax highlighting. But when I do telecope search of the file and open it it shows all the nice highlighting etc. here are two different screen shots.
You do not need vim.opt.filetype = "on"
. It is enabled by default.
If you are using Neovim 0.8 or later you do not need to do anything to enable Lua based filetype detection. It is all enabled by default.
While opening dot file I get following error message.
Error detected while processing BufReadPost Autocommands for "": E5108: Error executing lua vim/_editor.lua:0: BufReadPost Autocommands for ""..script nvim_exec2() called at BufReadPost Autocommands for "*":0: Vim(call):E1 17: Unknown function: dist#ft#CSH stack traceback: [C]: in function 'nvim_exec2' vim/_editor.lua: in function 'cmd' ...r/start/filetype.nvim/lua/filetype/mappings/function.lua:525: in function 'name' ...te/pack/packer/start/filetype.nvim/lua/filetype/init.lua:17: in function 'set_filetype' ...te/pack/packer/start/filetype.nvim/lua/filetype/init.lua:65: in function 'try_lookup' ...te/pack/packer/start/filetype.nvim/lua/filetype/init.lua:171: in function 'resolve' [string ":lua"]:1: in main chunk