-
Notifications
You must be signed in to change notification settings - Fork 109
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
glitches after opening new windows? #35
Comments
This looks to be caused by the anysize patch. I can replicate this by making the st terminal floating and resizing it vertically. It's a bit silly that it tries to center the content of the terminal, other terminals don't do this as far as I can see. |
so is there a fix for this? |
Try this, enabled via |
You are right, I see it as well. It comes from the sixel patch, I am not entirely sure why it is needed: #if SIXEL_PATCH
case 't':
/* TODO should probably not be hard-coded */
ttywrite(";420;720t", 10, 1);
break;
#endif // SIXEL_PATCH |
what is that case for? |
I don't know, I checked https://github.com/charlesdaniels/st and it's the same behaviour there. Thankfully the commit comment has an explanation: |
i also just realized sixel doesn't work in my terminal. |
#if SIXEL_PATCH case 't': /* TODO should probably not be hard-coded */ ttywrite(";420;720t", 10, 1); break; #endif // SIXEL_PATCH This would result in printing ";420;720t" when exiting neovim. Without this code a line is written to standard err instead: erresc: unknown csi ESC[23;0t The ttywrite was added as part of this commit: - charlesdaniels/st@b50be82 which states: > When a S or T CSI escape was encountered, the lines which were scrolled > away would be deleted from the scrollback buffer. This has been > corrected - the lines are now preseved. > > This fixes a bug where issuing `clear` followed by `lsix` would cause > the line on which the `lsix` was issued to disappear from the scrollback > buffer. > > Note that the line may scroll out of view and thus dissapear, but it > will now be preserved in the scrollback buffer. Given that we could not reproduce the above bug without the ttywrite in this case I am not convinced that this is actually needed. Leaving this here in case this comes up again in the future.
I removed the case, couldn't replicate the scenario about the scrollback buffer. |
As for sixel, you may want to try img2sixel as well. If it doesn't show anything then maybe double check that you indeed still have the |
img2sixel is in libsixel package right? |
I'm not aware of a binary for it, I use the aur/libsixel installed using paru. |
i tried and img2sixel isn't working |
I don't know then, maybe double check if sixel graphics is working in other terminals. There's mlterm where this works out of the box (although the placement of the image is always at the top of the terminal window and is subject to cropping). In xterm you can enable sixel support by adding this to your ~/.Xresources file:
I must say I like how smooth the scrolling of images is in xterm. |
yeah they work in xterm |
eh it's fine, i don't need sixel that much anyway |
@godspeedfw Yeah the current hint in the patches.def.h about removing lines to get SIXEL to work is a bit misleading. Lines 11 to 12 in 245c409
I cloned the repo again, added that, run make and sudo make install and lsix just worked.
|
nope, still doesn't work for me |
and I think it was removed because SIXEL_C is defined in config.mk which is included in the Makefile |
So what is in your config.mk? |
|
Do you still have #define SIXEL_PATCH 1 |
yes |
I went through the patches again from your first post. Looks like there is a conflict between the w3m patch and the sixel patch that causes this. |
You're right, sixel works after I disable w3m. |
@schrmh I moved all of the ligatures and sixel stuff out of the Makefile into config.mk to make it easier and more consistent for people, i.e. you only need to uncomment things in config.mk now instead of having to fiddle in both that and the Makefile. I'll update the misleading comment in patches.def.h. |
so, can the conflict between w3m and sixel be fixed? |
So to get w3m images to show you need to have both But as far as I can tell you can't combine the above with the |
do w3m images not show even when transparency is 0 with |
nvm i checked and they don't |
no idea what causes this
the patches i have enabled are:
The text was updated successfully, but these errors were encountered: