Paul Evans

Should now be fixed upstream in libvterm; added a test also ``` revno: 828 committer: Paul "LeoNerd" Evans branch nick: libvterm timestamp: Wed 2023-05-10 00:18:48 +0100 message: Remember to still...

No, that's unrelated. You'll need to make the `ioctl(TIOCSWINSZ, ...)` call somewhere in nvim source. See for reference https://bazaar.launchpad.net/~leonerd/pangoterm/trunk/view/head:/main.c#L62

If you need to know the pixel size then the best you can do is just have nvim ask the real terminal and then relay that information back. Be careful...

@ZyX-I I'd suggest using an OSC or similar sequence here, rather than a "raw" escape. Those already have a standard multiplexing and termination arrangement, so it should be relatively straightforward...

@ZyX-I Ahyes, an APC. That's the one I was thinking of. Yes, an APC with a prefix of `nvim:` would be an excellent choice in this area. Do that.

I think the errant code is the part around here: https://github.com/neovim/neovim/blob/master/src/nvim/tui/tui.c#L287

Ah, your terminfo probably claims `max_colors#256` in that case. Yours is indeed splitting the range into 0-7 => SGR 30-37, 8-15 => SGR 90-97, 16-255 => SGR 35;8;16-255

Does it help if you wrote `return app->start` instead?

> That sucks. We probably need an FAQ entry for this and recommend against the use of the `v5.38` bundle with Mojolicious. You can just ```perl feature->unimport( 'module_true' ) if...

Added one comment about the implementation, but I think overall the intent of the behaviour is good. It means that with that feature enabled, the behaviour of "Name->foo" is simpler...