You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: Right/Left advance/detract pages like most pdf readers #436
* Xreader version 2.6.4
* Distribution - Fedora fc33.x86_64
This is not a bug report. Feel free to ignore it, as I am sure you are busy.
Issue
Right/left arrow keys do not advance to next/prev page like behavior in most pdf viewers, requiring my most hated activity: reading of directions.
Steps to reproduce
Open pdf
Want to move to next page
Press right arrow key
notice nothing's happening
look up the docs for xreader
notice that it uses ctrl-pgdn/ctrl-pgup instead
install evince in avoidance of accessing mental functions
Expected behaviour
Right/Left to advance/detract page
Other information
This is a feature request. I'd love to use x Reader, as I love pretty much everything about Cinnamon, but I cannot abide such blatant disregard of non-explicit, unplanned, defacto standardization.
Cinnamon is greatly appreciated by us mindless creatures of habit because it's basically just like a better version of Windows. I try what I need and it responds how I expect, and that makes me feel warm and fuzzy inside.
Like hot coco on a cold winter morning, chicken soup when you're sick, getting wasted on mixed flavors of alcohol you stole from your parents and puking all over the dance floor the night of your HS prom. Some things should just be like they always have been.
Therefore, I implore you modify xReader to behave more closely to Adobe Reader, otherwise you risk confusing people like me with short attention spans and long muscle memory.
I have a feeling that there is no actual reason for such a thing.
PS: I just remembered having changed shortcuts in xreader, albeit not the ones you want changed. I think I edited ~/.config/xreader/accels, but if I change the keys n and p to Right and Left, it has no effect, and xreader restores the previous values n and p.
PPS: I forgot to uncomment those lines. Oddly, xreader reacted to n and p anyway. After uncommenting the lines, xreader didn’t overwrite the values, but didn’t react to n/p or Right/Left. After changing the keys to n and p again, xreader reacted to n and p again, but commented the two lines. After uncommenting the keys gtk_accel_path "<Actions>/MenuActions/GoNextPage" and gtk_accel_path "<Actions>/MenuActions/GoPreviousPage", using Right and Left only works when the Zoom is set for a page to fit inside the window’s height. I think this is what wujastyk has reported in November. I would consider this a bug.
@scytho yes, I did. When the page is bigger than fitting in a window, key behaviour changes (or appears to change).
I often find that my attempts to page through a document end up rotating the pages on the screen, because my years-old muscle-memory was trained on other programs.
Up! Yes, this drives me mad. It's always strange whenever I need to use xreader and the left/right arrows don't work as habit from all the other pdf readers I've ever used. ctrl+pg up/down is not a viable solution.
it's really telling that there has been no progress on this issue, just searching for "key" in issues shows that many people have come to point out the obvious. I honestly wonder what's going on with the maintainers
it's really telling that there has been no progress on this issue, just searching for "key" in issues shows that many people have come to point out the obvious. I honestly wonder what's going on with the maintainers
Completely normal. They wait for the issue to go stale, hoping in the meantime that an update has (slightly) changed the steps to reproduce. Then they'll close the issue (even if it's still there, but the steps to reproduce don't apply anymore, so 🤷♂️), and if you try to say anything they'll lock it to contributors only.
Activity
scytho commentedon Feb 28, 2021
+1!
(Oh Github, remove that device verification …)
wujastyk commentedon Nov 15, 2021
+1
or, more generically, allow keystroke shortcuts to be user-defined.
scytho commentedon Nov 15, 2021
I am afraid we may as well wish for us to grow telekinetic powers, or so …
#466
rgreen5 commentedon May 13, 2022
+1 to the request. Or at least an easy way to change shortcut preferences.
scytho commentedon May 13, 2022
I have a feeling that there is no actual reason for such a thing.
PS: I just remembered having changed shortcuts in xreader, albeit not the ones you want changed. I think I edited ~/.config/xreader/accels, but if I change the keys
nandptoRightandLeft, it has no effect, and xreader restores the previous valuesnandp.PPS: I forgot to uncomment those lines. Oddly, xreader reacted to n and p anyway. After uncommenting the lines, xreader didn’t overwrite the values, but didn’t react to n/p or Right/Left. After changing the keys to
nandpagain, xreader reacted to n and p again, but commented the two lines. After uncommenting the keysgtk_accel_path "<Actions>/MenuActions/GoNextPage"andgtk_accel_path "<Actions>/MenuActions/GoPreviousPage", using Right and Left only works when the Zoom is set for a page to fit inside the window’s height. I think this is what wujastyk has reported in November. I would consider this a bug.wujastyk commentedon May 13, 2022
@scytho yes, I did. When the page is bigger than fitting in a window, key behaviour changes (or appears to change).
I often find that my attempts to page through a document end up rotating the pages on the screen, because my years-old muscle-memory was trained on other programs.
tcubano commentedon Apr 20, 2023
Up! Yes, this drives me mad. It's always strange whenever I need to use xreader and the left/right arrows don't work as habit from all the other pdf readers I've ever used. ctrl+pg up/down is not a viable solution.
SkullHex2 commentedon Jul 24, 2023
Up, this should really be implemented
jerkey commentedon Apr 21, 2026
it's really telling that there has been no progress on this issue, just searching for "key" in issues shows that many people have come to point out the obvious. I honestly wonder what's going on with the maintainers
SkullHex2 commentedon Apr 22, 2026
Completely normal. They wait for the issue to go stale, hoping in the meantime that an update has (slightly) changed the steps to reproduce. Then they'll close the issue (even if it's still there, but the steps to reproduce don't apply anymore, so 🤷♂️), and if you try to say anything they'll lock it to contributors only.