New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Terminal does not support reporting screen size s via the TIOCGWINSZ ioctl" #8259
Comments
Patch welcome |
This comment was marked as outdated.
This comment was marked as outdated.
No, that's unrelated. You'll need to make the https://bazaar.launchpad.net/~leonerd/pangoterm/trunk/view/head:/main.c#L62 |
Apparently there's already a TIOCSWINSZ callback in: neovim/src/nvim/os/pty_process_unix.c Line 124 in b3ce001
However the icat script fails because it's expecting pixel width/height in addition to columns/lines. Furthermore, even if I set the pixel size for a given neovim term, the script fails with "terminal does not support graphics, please use kitty". It seems to be a much bigger change than expected. |
#include <stdio.h>
#include <string.h>
#include <sys/errno.h>
#include <sys/ioctl.h>
int main(void)
{
struct winsize w;
if (ioctl(1, TIOCGWINSZ, &w) < 0)
{
fprintf(stderr, "Couldn't get window size: %s\n", strerror(errno));
}
else
{
printf(
"chars w,h: %4u, %4u\npixels x,y: %4u, %4u\n",
w.ws_row,
w.ws_col,
w.ws_xpixel,
w.ws_ypixel);
}
return errno;
} |
I’m also willing to put out a $100 bounty on this. |
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 of |
any updates on this? |
no |
I'm running into a similar issue, I believe, when running neovim inside a container in Fedora Silverblue. |
nvim --version
: NVIM v0.2.3-975-g84bac9f50$TERM
: xterm-256colorSteps to reproduce using
nvim -u NORC
Requires kitty terminal emulator and its
icat
scriptActual behavior
Terminal does not support reporting screen sizes via the TIOCGWINSZ ioctl
Expected behavior
An image should be displayed.
The text was updated successfully, but these errors were encountered: