Highlight selected line about compiler-explorer.nvim HOT 10 CLOSED

Hi. I think you may have sent the same link twice there. If you refer to source to assembly and assembly to source line highlighting (as it happens on the compiler explorer website) then the feature is already supported. All you have to do is add
open_qflist = true to the setup function. I am sorry if the documentation is not yet up to par, but I haven't had the chance to add some vimdocs or a features section to the README just yet. Let me know if this is the feature you were referring to.

from compiler-explorer.nvim.

Oh, got, thank you!

from compiler-explorer.nvim.

@krady21 I tried setting

require("compiler-explorer").setup({
  open_qflist = true,
})

But it stopped to use Telescope for selection.

from compiler-explorer.nvim.

oops, my bad. I meant to give give you another option:

require("compiler-explorer").setup({
  autocmd = {
    enable = true,
    hl = "Search",
  }
})

The enable is the important part, while hl allows you to change the highlight group. I think that i am using CursorLine as the default highlight group so that it would match well if you have the set cursorline option on.

open_qflist = true opens the quickfix list which should be populated by the errors, warnings and diagnostics received from compiler-explorer.

from compiler-explorer.nvim.

I meant to give give you another option:

Same here, with this configuration I losing selection through Telescope. Is this expected?

from compiler-explorer.nvim.

What do you mean by losing selection? To be fair, I've only tested the plugin very briefly with telescope as the backend for dressing.nvim because i mainly use fzf-lua. Could you walk me through the commands and the source code that you used in this scenario?

from compiler-explorer.nvim.

Without any configuration :CECompile opens selection (expected!):

But if I call setup() selection looks like this after calling :CECompile:

from compiler-explorer.nvim.

Sorry for the late reply. I could not reproduce this with telescope and by running the setup() function. The setup code does not interfere with the other plugins that override vi.ui, so I'm not exactly sure why this happens. Maybe you resourcing your init.lua or init.vim switches back to the default vim.ui.select.

from compiler-explorer.nvim.

Sorry for the late reply. I could not reproduce this with telescope and by running the setup() function. The setup code does not interfere with the other plugins that override vi.ui, so I'm not exactly sure why this happens

I think I know why it happens. These lines:

from compiler-explorer.nvim.

Opened #4.

from compiler-explorer.nvim.