Fujita Hitoshi

The details you've given are very helpful for me, thank you. I will look into the cause of the problem.

Hi @xfzv, thank you for your reporting it. However, the original issue was reported before v0.10 is released, so a v0.10-only problem could come from other causes. Please open another...

@xfzv, Sorry for my confusing you with a wrong direction. I made a mistake and thought the Neovim v0.10 has just released. The original reporter, Nitestack could use v0.10 as...

Updating this plugin should make it work for you with setting correct file type even in Neovim v0.10.

Thank you for your explaining the situation in detail. This issue likely stems from the [`pattern` rule](https://neovim.io/doc/user/autocmd.html#_6.-patterns) of `autocmd` that's applied in the following line of your `init.lua`: ```lua pattern...

Hmm... Would removing the brackets (`{}`) from around the `pattern` work? ```lua -- pattern = { vim.fn.escape(home:gsub('\\', '/') .. '/.local/share/chezmoi/*', '.~$[ ') }, pattern = vim.fn.escape(home:gsub('\\', '/') .. '/.local/share/chezmoi/*', '.~$[...

The `chezmoi#source_dir_path` option seems to be set to a list somewhere, as indicated by the error message. However, I haven't been able to reproduce this issue in my Windows environment...

You shouldn't need to submit a PR. Thank you. You should not need to modify `chezmoi.lua`, so revert it to its original state. Instead, set the `HOME` environment variable to...

You may need to replace backslashes (`\`) with forward slashes (`/`) in the `HOME` environment variable if you are still encountering an error. Backslashes (`\`) in file paths can sometimes...

Making your `autocmd` rules that detects file type belong in the `filetypedetect` group could make it work for you because this plugin runs all `autocmd`s only belonging in the `filetypedetect`...