Up/Down arrows swapped when marking text in rxvt-unicode

[ltning]

Hiya! I'm using Turbo Pascal for DOS more often than I'd like to admit, so this project is like an early xmas present (yeah, I just discovered it). But turns out there's a weird problem: When I attempt to mark text, left/right arrows (with shift) work fine, but up/down are swapped!

So if I press shift-down, it marks the line above, and continues upwards if I hit down-arrow again. Funky, funny, but ultimately mostly confusing.

I'm running rxvt-unicode version 9.31 on FreeBSD 15.

[magiblot]

Hi @ltning! Excuse me for the late reply.

In order to figure out what's exactly happening, I need the following information:

• What is the value of the TERM environment variable? (run the command echo $TERM in the shell)

• Could you please try this program and check what it displays when pressing Shift+KeyUp/Shift+KeyDown?

  input_test.cc

  #include <ncurses.h>
  #include <string>
  #include <cstdio>
  #include <cstring>
  #include <iostream>
  #include <clocale>
  #include <bitset>
  
  using namespace std;
  
  template<typename int_t>
  string toHex(int_t n) {
      char expr[32];
      char hexa[32];
      sprintf(expr, "%%0%lullX", 2*sizeof(int_t));
      sprintf(hexa, expr, n);
      return string(hexa).substr(int(strlen(hexa))-2*sizeof(int_t));
  }
  
  template<typename int_t>
  string toBinary(int_t n) {
      return bitset<8*sizeof(int_t)>(n).to_string();
  }
  
  int main()
  {
      setlocale(LC_ALL, "");
      initscr();
      raw();
      keypad(stdscr, TRUE);
      set_escdelay(10);
      nodelay(stdscr, FALSE);
      noecho();
      do {
          int key = wgetch(stdscr);
          if (key == 'C' - 'A' + 1) // ^C
              break;
          nodelay(stdscr, TRUE);
          do {
              cerr << "> " << (key < 10 ? "00" : key < 100 ? "0" : "") << key << " <> 0x" << toHex(key)
                  << " <> 0b" << toBinary(key) << " < (" << keyname(key) << ")\r\n";
              key = wgetch(stdscr);
          } while (key != ERR);
          cerr << "\r\n";
          nodelay(stdscr, FALSE);
      } while (1);
      endwin();
  }
  

  You can run it like this:

  g++ -std=c++11 -o input_test input_test.cc -lncursesw
  ./input_test

Cheers.

[ltning]

Hola!

I'm using rxvt-unicode, and the TERM is usually rxvt-unicode-256color. However, with that setting, arrow keys don't work at all (for selecting):

> 259 <> 0x00000103 <> 0b00000000000000000000000100000011 < (KEY_UP)

> 258 <> 0x00000102 <> 0b00000000000000000000000100000010 < (KEY_DOWN)

> 027 <> 0x0000001B <> 0b00000000000000000000000000011011 < (^[)
> 091 <> 0x0000005B <> 0b00000000000000000000000001011011 < ([)
> 097 <> 0x00000061 <> 0b00000000000000000000000001100001 < (a)

> 027 <> 0x0000001B <> 0b00000000000000000000000000011011 < (^[)
> 091 <> 0x0000005B <> 0b00000000000000000000000001011011 < ([)
> 098 <> 0x00000062 <> 0b00000000000000000000000001100010 < (b)

However if I set TERM=rxvt, the output is different (and I get the reversed shift-arrow movements):

> 259 <> 0x00000103 <> 0b00000000000000000000000100000011 < (KEY_UP)

> 258 <> 0x00000102 <> 0b00000000000000000000000100000010 < (KEY_DOWN)

> 336 <> 0x00000150 <> 0b00000000000000000000000101010000 < (KEY_SF)

> 337 <> 0x00000151 <> 0b00000000000000000000000101010001 < (KEY_SR)

These two samples are from the exact same key events:

1. key_up
2. key_down
3. shift+key_up
4. shift+key_down

Hope this helps. :)

[ltning]

And here's in an xterm, with TERM=xterm - the shift-arrow events are reversed (compared to urxvt) indeed, and selection works as expected..

> 259 <> 0x00000103 <> 0b00000000000000000000000100000011 < (KEY_UP)

> 258 <> 0x00000102 <> 0b00000000000000000000000100000010 < (KEY_DOWN)

> 337 <> 0x00000151 <> 0b00000000000000000000000101010001 < (KEY_SR)

> 336 <> 0x00000150 <> 0b00000000000000000000000101010000 < (KEY_SF)

[ltning]

Note: In nano, arrow keys and shift+arrow keys works as expected, with any terminal and TERM settings. So I'm not sure what's going on here..