Skip to content
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

Keyboard shortcut modifications #334

mbryantms opened this issue Feb 13, 2019 · 3 comments


4 participants
Copy link

commented Feb 13, 2019

The keyboard shortcuts work well but aren't customizable as far as I know. Vi/Vim shortcuts are j for down and k for up. For miniflux it's actually the oppose. k moves down and jmoves to the previous item.

I know it's not feasible to modify for everyone but is it possible to allow to customize as I always have issues when switching between the two.


This comment has been minimized.

Copy link

commented Mar 1, 2019

This is something that bothers me as well. Unless a global switch is okay, perhaps there could be a simple toggle for this through environment variables, something like KEYS_JK_SWAP=1.


This comment has been minimized.

Copy link

commented Jun 12, 2019

I actually dislike the recent change with 2.0.16. Many Feedreaders (google reader, feedly, ..) used to have the same behavior as versions up to 2.0.15.

Saying that as a all time vim user (middle finger for skipping through articles is easier, maybe?! I don't really know).

I know that features should be limited to really being benefical. Maybe making this (keyboard shortcuts) configurable would be an option nevertheless.

Should not be a very very big issue for most people anyway.


This comment has been minimized.

Copy link

commented Jun 24, 2019

Just a counterpoint to the last comment. I signed up for the free trial 3 or 4 times in the past, but never stuck with it because of the pre-2.0.16 shortcuts even thought I liked it otherwise. I happened to try it again recently, and I just paid for a subscription since the shortcuts make sense to me now.

Of course I have no problem if it were configurable :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.