elixir-editors / elixir-editors/vim-elixir

syntax highlighting broken for `.*eex` files

Open
#562 12 comments 8 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
1.3k
Forks
154
PR merge metrics
No merged PRs in 30d

Description

After the recent change that [removed ftdetect](https://github.com/elixir-editors/vim-elixir/pull/560), syntax highlighting is no longer working for `.*eex` files (`.heex`, `.leex`, etc). It appears that the default filetype detection marks these files as e.g. `ft=heex` instead of `ft=eelixir`, as the previous `ftdetect` plugin did.

# Actual

```
set ft?
filetype=heex
```

![image](https://user-images.githubusercontent.com/18172185/161129232-d9a1605a-9e09-426f-8f88-9a220a9f7f07.png)

# Expected

If I run `set ft=eelixir`, I get this:

![image](https://user-images.githubusercontent.com/18172185/161129310-245ce1bf-8fa5-4f75-86ba-e01de2b59ad6.png)

However, if I first run `let b:eelixir_subtype = 'heex'`, I get this:

![image](https://user-images.githubusercontent.com/18172185/161129496-f12b9596-8268-47de-8966-30655750b0f6.png)

Not sure which of these is correct.

```
$ nvim --version
NVIM v0.7.0-dev+1348-g524f6294a
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by a80323765@USC02F834HMD6N

Features: +acl +iconv +tui
See ":help feature-compile"

system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-524f629/share/nvim"

Run :checkhealth for more info
```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.