I was initially disappointed because I had to look up cursor movement bindings in vi and emacs, but beyond that I really didn't care.Can confirm that it's the "Capture the entire screen" Action bound to "PRINT". Take this away and we can use the up key normally again.
Was ultimately disappointed when I pkg upgrade and this started. xD
Agree. It's not really much of an issue. I just kind of wondered why the PRINT would fallback to arrowkey UP if the keyboard's key for PrintScreen is unrecognized.I was initially disappointed because I had to look up cursor movement bindings in vi and emacs, but beyond that I really didn't care.
The commits referenced in the git thread show the capture key bindings coming in, and as I said I really don't use the keybindings.
It was nice to see other people running into the same problem.
Yep, I went through all of that too. It made no sense, especially looking at the commit diffs. In WPrefs if I did "capture" for the print screen and selected the PrtScr key and that made the up arrow work until I restarted WindowMaker, then it was broken again. Mucking about with the capture, it recognized up arrow and prtscr as different, so something is going on in the code.Agree. It's not really much of an issue. I just kind of wondered why the PRINT would fallback to arrowkey UP if the keyboard's key for PrintScreen is unrecognized.
Then again, since no issue I strive away from digging deeper only to find out this minor.
I have started an internal questionnaire to find out what key would be least hurtful to be reassigned to printscreen. It's a hard choice. Becomes even harder if the function keys should be disregarded. I think I would sac '§' right below Esc.Yep, I went through all of that too. It made no sense, especially looking at the commit diffs. In WPrefs if I did "capture" for the print screen and selected the PrtScr key and that made the up arrow work until I restarted WindowMaker, then it was broken again. Mucking about with the capture, it recognized up arrow and prtscr as different, so something is going on in the code.