Neovide registers .toml files with the org.vim.toml-file UTI, which prevents Syntax Highlight from handling their Quick Look previews.
With Neovide 0.16.2 installed:
$ mdls -name kMDItemContentType -name kMDItemContentTypeTree mise.toml
kMDItemContentType = "org.vim.toml-file"
kMDItemContentTypeTree = (
"org.vim.toml-file",
"public.plain-text",
"public.text",
"public.data",
"public.item",
"public.content"
)
Neovide declares the association in its Info.plist:
<key>LSItemContentTypes</key>
<array>
<string>org.vim.toml-file</string>
</array>
Syntax Highlight 2.1.30 recognizes TOML syntax, but its File Inquiry reports these files as Supported but not handled. The extension currently declares public.toml and io.toml in QLSupportedContentTypes, but not org.vim.toml-file.
Could org.vim.toml-file be added as a supported TOML UTI in a future release, as io.toml was added for #336?
Neovide registers
.tomlfiles with theorg.vim.toml-fileUTI, which prevents Syntax Highlight from handling their Quick Look previews.With Neovide 0.16.2 installed:
Neovide declares the association in its
Info.plist:Syntax Highlight 2.1.30 recognizes TOML syntax, but its File Inquiry reports these files as Supported but not handled. The extension currently declares
public.tomlandio.tomlinQLSupportedContentTypes, but notorg.vim.toml-file.Could
org.vim.toml-filebe added as a supported TOML UTI in a future release, asio.tomlwas added for #336?