Alexandre GV.

Hi, thanks for the report Unfortunately, I can't manage to reproduce the bug locally I reproduced your setup from your screenshot, with a folder under my home, a sub-folder named...

Hi, thanks for the detailed infos! I reproduced your setup on my arch install and also on WSL2 (Ubuntu 18.04), but couldn't manage to reproduce the bug :/ I couldn't...

I'm also using neovim, so this shouldn't be the problem. Guess you will have to do the classic "plugin-by-plugin" debug haha Really strange that another plugin could be in conflict,...

Nice catch! `~/.norminette/norminette.rb` is ok since "Not a valid file" is an error returned by norminette. The problem is with the opened file (`test.c`). My guess is that syntastic/norminette-vim gets...

Well, I think the real problem is on syntastic or rooter side since I don't manually run the linter or define the filepath in norminette-vim, I just configure the linter...

Well, this is really weird since looking at debug infos, cwd and makeprg seem correct.. If you can reproduce this bug with other syntastic linters, you should probably open an...

Since this problem seems to only affect norminette v2 (ruby) and the official version is now v3 (python) everywhere for more than a year, I will close this issue.

FYI I use tmux and the colors are fine. I have fx v24.0.0 and tmux v3.3a Try to set your `TERM` environment variable to `xterm-256color`, and also add this to...

What solution is better in your oponion ? - A simple one-liner, usable without even having to clone the repo ``` docker run -v ${PWD}:/tmp golang sh -c 'go get...

Repo moved to https://github.com/42Paris/hall-voice, please make a new Pull Request