Evgeni Chasnovski

I am afraid I have to close with resolution "'mini.tabline' can have only predefined set of full tab colors". Another way to put it is "an output of `config.format` will...

> I guess I’ll have to configure my tabline manually now. :P It's a bit more tedious than statusline specifically for the reason mentioned here: the content can not fit...

> hello, Is this issue solved? Hi! It is *re*solved with "sorry, it brings more troubles than usefulness". See [this comment](https://github.com/echasnovski/mini.nvim/issues/1279#issuecomment-2419762549) for more details.

> if there's some other unicode char we can use, suggestions welcome. Two ideas: - For me `eob` character should convey the "there is nothing here" message. So maybe a...

> I have tried a vertical line. Middle-dot is the best compromise, from my testing. @justinmk, what seems important to note here is that end-of-buffer symbol should not be **too**...

Thanks for the PR! Although the change looks okay, I *think* it worked as is a month or so ago. Maybe there were changes in 'blink.cmp' that made it not...

Yes indeed it does look like an issue with 'blink.cmp' (Saghen/blink.cmp#1856), either with docs or code. And indeed possibly a long standing one. I've pushed a fix with proper test...

I'd like to share couple of observations based on experience of using most of them: - Getting/setting whole lines is used *far* more frequently than getting/setting text. Having `start_col` and...

> > Maybe having [default] `start_col = 0` and `end_col = -1` would make more sense? On a similar note maybe also having `start_row = 0` and `end_row = -1`...

> That all sounds good! Except: "whole buffer" is easy to specify (-1), but the "insert" case is a bit awkward (`from` and `to` must both be passed and identical)....