You are not logged in.
Pages: 1
My terminal do not work with some key binding.
When I press pagedown with shift, only "2~" shows up.
(I expected it to scroll down as I patched it, and did compile it)
Since I started to learn arch yesterday, I have no idea who handle this behavior.
I'm currently using xorg, dwm, st, zsh
Last edited by ToMmyDong (2019-12-01 16:29:13)
Offline
(I expected it to scroll down as I patched it, and did compile it)
You'll have to elaborate and "prove" this since what you describe is the stock st behavior.
- What patch?
- errors during compilation?
- did you override your former st binary? What st binary is actually invoked?
Offline
Not all terminals support all key bindings (especially some small and slim like st may not support), for example: xterm, urxvt supports Shift+PageDown/PageUp but not Shift+Home/End, termite, lxterminal, xfce4-terminal, konsole supports previously mentioned key bindings and many more.
Offline
I patch "st-scrollback-0.8.2.diff" from https://st.suckless.org/patches/scrollback/
I didn't got any error patching or compilation.
I've changed other config to make sure I'm overriding the right file.
Offline
config.def.h:
…
{ ShiftMask, XK_Page_Up, kscrollup, {.i = +1} },
{ ShiftMask, XK_Page_Down, kscrolldown, {.i = +1} },
…
don't forget to remove config.h (to have make recreate it)
Offline
Thanks, that's the point. It works now.
Btw. I'm confused with the logic behind. Why is it necessary to have such file like config.h? It looks like it is just copying config.def.h if it does not exist. But why don't it just compile with config.def.h?
Can I modify the config.def.h arbitrary? Will modify manually make future patches fail?
Offline
You're supposed to edit config.h and leave config.def.h alone, but that sucks, because everytime you apply a patch (or there's an update to st's config.def.h) you've to regenerate config.h and edit it to your likings.
Patches can"fail" all the time w/ the st approach because many features come in patches that can collide easily (in all files, not only config.def.h). You then have to reolve the conflicts locally.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Thanks for your help
Offline
Pages: 1