Daniel Serodio

Thanks for the explanation, I understand that Portuguese is a complex language. I tested this using the webapp at https://languagetool.org/pt-BR 

I don't think it will be supported because this is part of the [spec](https://editorconfig.org/): > ### Where are these files stored? > > When opening a file, EditorConfig plugins look...

> There is already an AWS icon availabe so GCP would be useful as well. @jamesturner where?

Yes, I'd also love to have `due:10am` or `due:tomorrow`

@pecigonzalo [ContainerLabs/terraform-unused-vars](https://github.com/ContainerLabs/terraform-unused-vars) is gone, do you have any replacements to suggest?

Not working for me either. I also have other Markdown extensions installed ([Markdown Preview Github Styling](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-preview-github-styles) and [GitHub Markdown Preview](https://marketplace.visualstudio.com/items?itemName=bierner.github-markdown-preview))

```bash $ echo $TERM xterm-256color $ echo $COLORTERM truecolor echo $NO_COLOR ```

For some reason, `grep` (BSD, macOS default) doesn't use colors by default either, but `grep --color` and `grep --color=auto` do. For `ug`, even `--color=always` doesn't use colors

Don't worry, I didn't feel ignored, but I have no idea why this is happening. I normally use iTerm2 with zsh (both heavily customized), but I just tried with Terminal.app...

Nailed it! 🙌🏼 `ugrep --color=always --colors='ms=hr'` works! So I checked that `GREP_COLORS` is set to `1;32`. If I unset it, both `ugrep zsh /etc/shells` and `ug zsh /etc/shells` highlight as...