live_grep + path shortening

[shushtain]

I have two query files:

• queries/markdown_inline/highlights.scm that contains "offset"
• queries/markdown/highlights.scm that doesn't contain "offset"

When I search for "offset" with live_grep, it brings me to the correct line in the wrong file. I have path shortening on, so, I guess, both files would be que/mar/highlights.scm. Is this just an expected, unavoidable trade-off? For some reason I thought that the shortening is purely visual.

[nenahp]

I thought that the shortening is purely visual.

it's not visual, it's processed before piped into fzf.

It's possible to process the text only visually via nvim_set_decoration_provider: https://github.com/phanen/fzf-lua-overlay/blob/5fdc194ddfe2e64a7fd6780492d8838553c06008/lua/fzf-lua-extra/providers/file_decor.lua#L18
but this will break ansi highlighting, so you have to rebuild total line, and it's a bit tricky to get the "matched" part then apply correct highlighting (still possible with nvim__inspect_cell).

I'm not sure if snacks can do this correct, since it can apply treesitter hl on live_grep result by rebuild the line totally via a ripgrep option: https://github.com/folke/snacks.nvim/blob/f2f05e5cffcedf153ff5c669dab79454618f8cbb/lua/snacks/picker/source/grep.lua#L17 (EDIT: maybe this is not related, it's about content, not path name)

[shushtain]

Okay, thanks. At least, it's not because of some silly mistakes in my config. I'll live with that :)

[nenahp]

Just found conceal won't break highlight also since it allow single character at most, which can be a usage case for path shortening

although the conceal part won't show match hl

Here's a poor example

local makeline = function(buf, lnum, line)
  local off, content = line:match('^(%s*)(%S+)')
  if not off or not content then return end
  local icon, hl = require('mini.icons').get('file', content)
  if not icon then return end
  local parts = vim.split(content, '/')
  local current_col = #off
  local n = #parts
  for i, part in ipairs(parts) do
    if i == n then return end
    vim.api.nvim_buf_set_extmark(buf, ns, lnum, current_col, {
      end_col = current_col + #part,
      hl_group = hl,
      conceal = part:sub(1, 1),
      ephemeral = true,
    })
    current_col = current_col + #part + 1
  end
end

[ibhagwan]

Just found conceal won't break highlight also since it allow single character at most, which can be a usage case for path shortening

although the conceal part won't show match hl

very nice! Can we use it then for all shortening?

[nenahp]

This allow single char only. So only work for opts.path_shorten = 1

EDIT: although we can create two extmarks for one part then we get path_shorten=2..

[ibhagwan]

This allow single char only. So only work for opts.path_shorten = 1

EDIT: although we can create two extmarks for one part then we get path_shorten=2..

I think it’s worth it, we can limit it to one char, the only reason to use more than one is due to these kinds of conflicts, if there are no conflicts why use 2+?