key problems with Ctrl+arrow and Shift-tab in rxvt-unicode

[hramrach]

Hello,

I use rxvt-unicode and running the brick demos I noticed

• in edit demo tab moves to next edit but Shift-tab does not move to previous
• in demos using Ctrl+arrow keys the part with Ctrl+arrow does not work

Using brick 0.4.1 on Debian Stretch

constraints: StateVar ==1.1.0.1,
adjunctions ==4.2.2,
array ==0.5.1.0,
base ==4.8.2.0,
base-orphans ==0.4.4,
bifunctors ==5,
binary ==0.7.5.0,
blaze-builder ==0.4.0.1,
bytestring ==0.10.6.0,
comonad ==4.2.7.2,
containers ==0.5.6.2,
contravariant ==1.3.3,
data-default ==0.5.3,
data-default-class ==0.0.1,
data-default-instances-base ==0.0.1,
data-default-instances-containers ==0.0.1,
data-default-instances-dlist ==0.0.1,
data-default-instances-old-locale ==0.0.1,
deepseq ==1.4.1.1,
directory ==1.2.2.0,
distributive ==0.4.4,
dlist ==0.7.1.2,
exceptions ==0.8.0.2,
filepath ==1.4.0.0,
free ==4.12.1,
ghc-prim ==0.4.0.0,
hashable ==1.2.3.3,
integer-gmp ==1.0.0.0,
kan-extensions ==4.2.3,
lens ==4.12.3,
mtl ==2.2.1,
old-locale ==1.0.0.7,
parallel ==3.2.0.6,
parsec ==3.1.9,
prelude-extras ==0.4.0.2,
pretty ==1.1.2.0,
primitive ==0.6.1.0,
profunctors ==5.1.1,
reflection ==2,
rts ==1.0,
semigroupoids ==5.0.0.4,
semigroups ==0.16.2.2,
stm ==2.4.4,
tagged ==0.8.2,
template-haskell ==2.10.0.0,
terminfo ==0.4.0.1,
text ==1.2.1.3,
text-zipper ==0.3.1,
time ==1.5.0.1,
transformers ==0.4.2.0,
transformers-compat ==0.4.0.4,
unix ==2.7.1.0,
unordered-containers ==0.2.5.1,
utf8-string ==1.0.1.1,
vector ==0.10.12.3,
void ==0.7.1,
vty ==5.3.1

[jtdaugherty]

Thanks for the report!

I've just pushed d0cabf9 to add Shift-Tab support to the editor demo.

As for your control-arrow keys, that is dependent on your terminal emulator sending the expected control sequences, which they do not all do by default. It looks like you can probably fix it by using the Xresources tip mentioned at https://bbs.archlinux.org/viewtopic.php?id=71462. For more information, please take a look at #32. If that works for you, please close this issue (or let me know what else I can do).

[jtdaugherty]

I'm closing this due to inactivity; if my response didn't clarify things for you or if you need anything else, please re-open or file a new issue. Thanks!