luukvbaal

I don't know, if it doesn't crash there is no backtrace. I cannot imagine what would cause Nvim to quit from the information you provided. Does it happen with the...

Does `nvim_msg_set` also emit the message? In that case maybe it fits in `nvim_echo` which already has an `opts` field?

The line number returned is correct, if you do `:set conceallevel=0` after CTRL-Y you'll see that the topline is actually 2. Not sure there is an issue here, I think...

If anything is to be adjusted it would be the scroll logic, which I guess could make sense.

No, feature request welcome if you have an idea of how that could look.

I refrained from providing the option through 'statuscolumn' as I [thought](https://github.com/neovim/neovim/pull/20621#issuecomment-1335979705) it would be sub-optimal: > Although easy to implement here for all signs, I think it would probably be...

I guess even that would be possible with the same one-line change in `get_statuscol_str()` but that would place the burden on the 'statuscolumn' plugin/user. In theory you could only repeat...

(In the mean time?) it is possible to do this on a per-sign basis when implementing custom sign segments for `'statuscolumn'` through `sign_getplaced()`/`nvim_buf_get_extmarks()`. I recently added support for this in...

It should probably exclude windows that are either hidden or non-focusable.

No I don't think so. Those are API's that list all windows, only the caller knows whether they are interested in hidden/unfocusable windows. Actually I'm not sure `winnr('$')` should exclude...