-
Notifications
You must be signed in to change notification settings - Fork 158
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
feh --auto-zoom --scale-down inconsistent behavior for same command on i3? #494
Comments
Same problem on dwm |
Can confirm it is happening on dwm, and it also happen when simply calling feh without any option. The image gets tiled across the whole windows, the issue seems random, as running the same command multiple times will sometimes lead to a correct behaviour, without any identifiable pattern. |
I suspect it is caused by window resizing. |
Possibly related: #504 |
I'm having this issue on bspwm, too. |
Same here on bspwm |
Seems that if you use --reload 0.1 in the command the image will fix itself, tested on BSPWM. |
It does "fix" it, but also causes a reload, making you unable to zoom, pan, resize or do anything since it will reload every 0.1s. It's not a feasible workaround. Reverting the commit mentioned in #504 should probably do it. |
Can confirm that this is still an issue on the latest version of main when tested on dwm |
Greetings!
I've noticed that feh does not always behave consistently when called from i3.
To Reproduce:
cd
to a directory containing images.feh --auto-zoom --scale-down
Observed behavior:
About 80% of the time, the behavior is as expected and feh displays the first image, scaled to fit half the screen.
If I close the window and then recall the command a bunch of times, however, about 20-25% of the time, the image instead appears tiled in a 4x4 grid.
Any idea what could be causing this? It seems like sometimes the geometry estimation is occurs too soon perhaps. I'm wondering if compton could be affecting this? (e.g. due to lag ocurring during composition?)
Versions
The text was updated successfully, but these errors were encountered: