I don't think it's useful to have the same effect bound to two keys. I
get that changing the default behaviour might confuse a part of the
userbase, but I'd personally opt for removing the Page Up/Down bindings
from the default keybindings. If someone needs them, they can just
re-add them. I feel like most users will probably go through their
config at least once.
Why would you remove them. Page Up/Down are keys in configures in nearly
all applications and is imo easier as <C-b>.
BTW: There also other duplicated binds like the next field on composing:
<C-j> and <tab>. Removing here the tab also is weird for many users ig.
> Why would you remove them. Page Up/Down are keys in configures in nearly> all applications and is imo easier as <C-b>.
Duplicated keybinds tend to cause confusion (at least they cause
frequent calls to the support department where I work).
I agree that PgUp/Down is probably more user-friendly than C-b and it's
ultimately up to the user
> BTW: There also other duplicated binds like the next field on composing:> <C-j> and <tab>. Removing here the tab also is weird for many users ig.
Just on another note: removing any keybinding here does not affect your
user experience, because the binds.conf is in your userdir. I am also
for removing this duplicate, but this is not part of this patch.
I am also not of the opinion that my opinion is the be-all and end-all,
so feel free to reason with me here :D