When I start the w3m web browser in kitty, images are only shown for a fraction of a second after the page loads and then they vanish again.
Images can be brought back for an other fraction of a second while I scroll in the kitty window but then they disappear again.
Here an example using kitty:

Also a video to better see the issue: kitty images in w3m - vimeo
And here using xterm, where it works as it should:

Note: this issue is not due to the 0.12 release, I've had this issue with earlier versions as well.
OS: Arch
WM: i3
w3m uses a horrible hack to display images. It will not work with any GPU based terminal emulator. Since those are repainted independent of the X server.
@kdarkhan are there any terminal based browsers that work with kitty that you know of?
@kureta I never used images in terminal functionality. So don't know.
This is literally just wrong, you are clearly lying just because you disdain w3m without any actual reasoning for why it shouldn't work in a GPU terminal.

Here's a screenshot of another GPU accel terminal (Alacritty) where w3m images work perfectly fine.
Do you lack reading comprehension? Go read what I wrote again. As for it working in alacritty, what bullshit: https://github.com/jwilm/alacritty/issues/1021
And if you ever use that tone in a post on this project again, you will be blocked.
I don't, but I question whether you even remember what you said which was
"It will not work with any GPU based terminal emulator"
you made a misleading statement about other terminal emulators which are not your own simply because you seem to have a personal vendetta against w3m. adieu to you, and your project.
there is literally nothing wrong with hating w3m, or tmux, or other hacky bullshit.
w3m-img doesn't use any "hacks" to display images at all. The current de facto method to displaying images in the terminal is to render an X window and reparent it to the terminal window.
Do you lack reading comprehension? Go read what I wrote again. As for it working in alacritty, what bullshit: jwilm/alacritty#1021
This isn't necessarily accurate either. w3m-img displays can vary largely based on the users configuration for whatever calls w3m-img. Finicky at best, surely, but most definitely not out of the question. Also, if you see here, the issue _did_ get resolved by some users, further justifying that it could be a user configuration error.
If this does end up being implemented at some point, or fixed rather, you may want to consider properly handling X focus events (I haven't seen the source for Kitty myself, but speaking from experience, a lot of terminal emulators _don't_ properly handle refocus events, and they redraw when focus changes, causing images to "disappear" from the terminal).
Unrelated, but try and conduct yourself in a semi-professional manner at least (even if people don't have a tone you necessarily like, it's not in your best interest to be aggressive in return). I'm just a third party providing input, and it doesn't look good to someone on the outside looking in.
w3m-img doesn't use any "hacks" to display images at all. The current de facto method to displaying images in the terminal is to render an X window and reparent it to the terminal window.
it is a hack. also try changing focus to another tag/workspace, see if this crap still works.
w3m-img doesn't use any "hacks" to display images at all. The current de facto method to displaying images in the terminal is to render an X window and reparent it to the terminal window.
it is a hack. also try changing focus to another tag/workspace, see if this crap still works.
I mentioned how that could be averted in my post. Also, I'd like to add that the word hack was in quotes for a reason. Strictly speaking yes, it is, but I went on to explain that it is just the accepted way to do this.
Unrelated, but try and conduct yourself in a semi-professional manner at least (even if people don't have a tone you necessarily like, it's not in your best interest to be aggressive in return). I'm just a third party providing input, and it doesn't look good to someone on the outside looking in.
Thank you very much, I'll decide what's in my best interest. Dealing with people like @ZoeFiri is not. Life is too short, and too many people seem to be laboring under the delusion that I owe them something for having the temerity to make free software. You think I am unprofessional, feel free to not use my software.
I have about had it with dealing with rude and entitled people on the internet.
Most helpful comment
w3m-img doesn't use any "hacks" to display images at all. The current de facto method to displaying images in the terminal is to render an X window and reparent it to the terminal window.
This isn't necessarily accurate either. w3m-img displays can vary largely based on the users configuration for whatever calls w3m-img. Finicky at best, surely, but most definitely not out of the question. Also, if you see here, the issue _did_ get resolved by some users, further justifying that it could be a user configuration error.
If this does end up being implemented at some point, or fixed rather, you may want to consider properly handling X focus events (I haven't seen the source for Kitty myself, but speaking from experience, a lot of terminal emulators _don't_ properly handle refocus events, and they redraw when focus changes, causing images to "disappear" from the terminal).
Unrelated, but try and conduct yourself in a semi-professional manner at least (even if people don't have a tone you necessarily like, it's not in your best interest to be aggressive in return). I'm just a third party providing input, and it doesn't look good to someone on the outside looking in.