filetypes are not split when using lazy loading.

[marcoslopes]

basically the following works:

Plug 'mattn/emmet-vim', { 'for': [ 'jinja.html',  'html', 'mustache', 'jinja' ] }

but just jinja or just html does not:

Plug 'mattn/emmet-vim', { 'for': [ 'html', 'mustache', 'jinja' ] }

I am happy to leave jinja.html in my config, but based on this help it seems that it should take into consideration either.

latest

• Type:
  • [X] Bug
  • [X] Enhancement
  • [X] Feature Request
  • [ ] Question
• OS:
  • [ ] All/Other
  • [X] Linux
  • [ ] OS X
  • [ ] Windows
• Vim:
  • [X] Terminal Vim
  • [ ] GVim
  • [ ] Neovim

[petRUShka]

This is still the issue.

[komputerwiz]

Workaround (tl;dr)

Adding wildcards to the 'for' option makes on-demand loading work as expected for sub-filetypes:

Plug 'mattn/emmet-vim', { 'for': '*html*' }

It should also be noted that Emmet has its own support for lazy-loading:

let g:user_emmet_install_global = 0
autocmd FileType html,css EmmetInstall

Details

For on-demand loading, e.g., of

Plug 'mattn/emmet-vim', { 'for': 'html' }

vim-plug creates the following autocommand:

autocmd PlugLOD FileType html call <SID>lod_ft('html', ['emmet-vim'])

As this stands, the html filetype must be matched verbatim in order for the autocommand to execute. The pattern argument (:h autocmd-pattern) can use wildcards (*) for looser matching, which is why the above workaround works. However, this may have implications behind the scenes since the wildcards are also passed to s:lod_ft:

autocmd PlugLOD FileType *html* call <SID>lod_ft('*html*', ['emmet-vim'])

From what I can tell, the filetype argument to s:lod_ft ultimately gets treated as a glob pattern anyway.

Discussion

Some ideas to consider are:

1. Does the above workaround and subsequent passing of wildcards to s:lod_ft constitute intended behavior?

   If yes, then no code modifications are necessary, but this use case should be documented in the README.

   If no, then...

2. Should wildcards be added to the autocommand pattern whenever 'for' is used? That is, should the template in plug.vim:413 look like autocmd FileType *%s* call <SID>lod_ft(%s, %s)?

   If yes, then users would lose the ability to restrict on-demand loading to verbatim filetype patterns. This probably isn't a significant issue, but just something to be aware of. Perhaps a 'strict' option could prevent the addition of wildcards.

   if no, then...

3. Should wildcards, if used like in the workaround above, be stripped when passed to s:lod_ft?