Christian Clason

Sorry, I'm with @lervag here: the current mappings are _good_ -- and they are good for a reason: they follow basic Vim grammar that matches both builtin text objects and...

Done now, and API bike-shedding is over as well. Here the documentation should be good, too, and require very little expanding on.

But apparently there's some confusion about user autocommands -- people seem not to be aware that these are just standard autocommands with `User` as the event and `Whatever` as the...

With 0.7, you can now set highlights in pure Lua: ```lua vim.api.nvim_set_hl(0, "Search", { fg = '#2E3440', bg = '#E2A478', bold = true }) vim.api.nvim_set_hl(0, "IncSearch", { link = "Search"...

While the current state is fine for _personal_ `ftdetect` settings, it doesn't help filetype plugins like https://github.com/lervag/vimtex that extend and/or correct Vim's default `filetype.vim` detection logic. I strongly believe that...

**PSA:** `filetype.lua` is now the default on Neovim master (and 0.8.0, when that is released). It has full parity with `filetype.vim` (including `scripts.vim` and `setf FALLBACK` support), passing Vim's filetype...

Core is well aware of this plugin, and pretty much of the same opinion: worthwhile, but should be done carefully to avoid regressions. The more people test it now, the...

An intermediate step could be to move this into https://github.com/nvim-lua/plenary.nvim (the "Neovim nursery") -- in particular, integrating this into https://github.com/nvim-lua/plenary.nvim#plenaryfiletype.

In the meantime, it would be useful for this plugin to stay (reasonably) up-to-date with the [`filetype.vim` updates from upstream](https://github.com/neovim/neovim/commits/master/runtime/filetype.vim) -- I'm sure these would be welcome and straightforward PRs...

Note that the built-in Lua filetype detection behaves somewhat differently (for the above-mentioned reasons), so you might still prefer to use this plugin.