[BUG] I dont see any color and unable to jump to error in laguage like typescript

[Mofiqul]

Existing Issues

• I have searched the existing issues

Describe the bug

I can not see color out for any compilation error. Also, can not jump to error in language like typescript and elixir

Typescript

C

Steps To Reproduce

1. Open a typescript file 
2. Run `Compile tsc`

Expected Behavior

No response

Neovim Version

NVIM v0.10.4
Build type: RelWithDebInfo
LuaJIT 2.1.1720049189

Plugin Version

Latest

Configuration

return {
  "ej-shafran/compile-mode.nvim",
  -- tag = "v5.*",
  -- you can just use the latest version:
  branch = "latest",
  -- or the most up-to-date updates:
  -- branch = "nightly",
  dependencies = {
    "nvim-lua/plenary.nvim",
    -- if you want to enable coloring of ANSI escape codes in
    -- compilation output, add:
    { "m00qek/baleia.nvim", tag = "v1.3.0" },
  },
  config = function()
    ---@type CompileModeOpts
    vim.g.compile_mode = {
        -- to add ANSI escape code support, add:
        baleia_setup = true,
    }
  end
}

Additional Context

##  Chechhealth: 
compile-mode: require("compile-mode.health").check()

compile-mode.nvim report ~
- OK everything checks out

[ej-shafran]

Huh, seems weird. Maybe this has to do with Neovim 0.10.4?

[ej-shafran]

The tests seem to pass for 0.10.4, so jumping to errors should work, but we don't test for highlights...

• Can I get you to provide the lines that start with "CompileMode" when you run :highlight?
• Does running :NextError not work as well? Can you not jump to errors?
• Please also note that TypeScript does not have a default regex in error_regexp_table. If you want to add parsing for typescript errors, you could use something like this:

vim.g.compile_mode = {
     error_regexp_table = {
          typescript = {
            regex = "^\\(.\\+\\)(\\([1-9][0-9]*\\),\\([1-9][0-9]*\\)): error TS[1-9][0-9]*:",
            filename = 1,
            row = 2,
            col = 3,
          },
    }
}

[Mofiqul]

Highlight groups are cleared for CompileMode

• Adding them manually works
• Jump to error for typescript also working after adding the regex

[ej-shafran]

I can only seem to reproduce this during the first installation of the plugin using Lazy.nvim, since plugin/highlights.vim doesn't seem to be loaded in that instance;

• Is this happening consistently, even when you reopen Neovim?
• If you manually edit $HOME/.local/share/nvim/lazy/compile-mode.nvim/plugin/highlights.vim and add a line with echo "Hello", does that line get logged when you open Neovim?
• Are there any error logs from Lazy? What does :mes log out when you open Neovim?

[Mofiqul]

Is this happening consistently, even when you reopen Neovim?
Yes.

If you manually edit $HOME/.local/share/nvim/lazy/compile-mode.nvim/plugin/highlights.vim and add a line with echo "Hello", does that line get logged when you open Neovim?
Yes

Are there any error logs from Lazy? What does :mes log out when you open Neovim?
No

Currently, I added the highlights manually in my config after color scheme load and it's working

[ej-shafran]

Looking at this again

Is anyone else able to reproduce this issue?

@Mofiqul is there perhaps some other colorscheme in use than what you've shown in the reproduction config? Maybe something is clearing the highlights...?

[rainbow-bash]

i have this error but with c :(( the $HOME/.local/share/nvim/lazy/compile-mode.nvim/plugin/highlights.vim does echo hello when i put it there
everything else works fine just the colors are not showing for some reason

[Mofiqul]

Looking at this again

Is anyone else able to reproduce this issue?

@Mofiqul is there perhaps some other colorscheme in use than what you've shown in the reproduction config? Maybe something is clearing the highlights...?

I have checked and found nothing that clears the highlights. So, I had to add those highlight groups to the color scheme to make the color to work.

[ej-shafran]

Hey @Mofiqul @lampda - can you give #120 a look and see if it resolves this problem for you?

[ej-shafran]

Okay - since I haven't gotten a response, I'm guessing the issue is resolved.