Question: Don't move cursor until I select something

[hqkhan]

When I'm live grepping around, the cursor of my buffer (NOT fzf-lua's window cursor) moves to the line number of my current selection even if the selection is from different file altogether.

Is there a way for my buffer's cursor not to move until I've made a selection? Sometimes, I'm looking through the selections and decide to cancel the search but my cursor has moved me somewhere entirely different.

[ibhagwan]

Not sure I understand what's happening, why would your cursor move?

Unless I pressed enter on a selection my cursor never moves, either I'm misunderstanding this or it's a bug.

[hqkhan]

Funnily enough, it happened to me a couple more times but I can't repro it yet. I'll try to get a repro and be back lmao

[ibhagwan]

Np, keep me posted :)

[hqkhan]

Ok, this was a pain but I finally figured out the issue. TLDR; not an fzf-lua issue...

I had:

vim.wo[0].cursorbind = true
vim.schedule(function()
  vim.cmd.wincmd('p')
  vim.wo[0].cursorbind = true
  vim.cmd.wincmd('p')
end)

in fugitiveblame.lua so cursor shows up for this buffer and binded it together so they move together...

Now that we're on the topic, how do you use git blame option? I use it quite a bit to see who wrote what. I'm assuming this will need an aucmd where it implements the above and un-does it on leaving...

[ibhagwan]

Now that we're on the topic, how do you use git blame option? I use it quite a bit to see who wrote what. I'm assuming this will need an aucmd where it implements the above and un-does it on leaving...

I have a toggle to enable git blame virtual text in git signs or a pop up for git blame for the specific line I’m on

Line blame popup

Line blame virtual text

[hqkhan]

I see. That's interesting although I much prefer a longer version of git blame for all lines on my screen. Either way, I'm glad this was resolved cuz it was bothering me a lot lol.