luukvbaal

I don't see a straightforward way to pass the line number to the callback. We could add it to the `StlClickDefinition` struct, but we would have to change the callback...

> Alternatively, we could create only a single clickable region for the entire number column Scratch that, it would remove all of the flexibility of defining clickable regions in the...

> Moreover, I think we can freely reassign the first argument of the click def callback function to be the line number instead of the tab number. Actually I'm a...

I guess in theory this could solve https://github.com/neovim/neovim/issues/20447, could be cool.

Added work so far on click support in a separate commit @famiu. Further consideration on my part has my preference on just relying on `getmouspos().line` in the callback. No need...

> I'm using using minwid as the function id I see, that might be intended yeah but not entirely sure from the help docs tbh. Still wondering then if we...

Was looking to refactor the click_def allocation for win/statusbar/numbercolumn, which has some duplication. Is it an improvement? I think this is finished BTW, although some of the earlier mentioned points...

I'm not sure what's up with the asan build but it does seem to fail consistently the last few commits so perhaps it indicates an issue? EDIT: Fixed

I wonder if it will be worth it to add some plumbing to get the sign/fold column into the 'numbercolumn' format somehow. I was thinking we might add new stl-expr...

> > Still wondering then if we can/should pass along the line number as first argument for 'numbercolumn' instead. > Another solution might be to introduce a format code (only...