|
Bugzilla – Full Text Bug Listing |
| Summary: | rxvt-unicode: Arrow keys don't work in ncurses | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Bernhard Walle <bwalle> |
| Component: | Other | Assignee: | Marcus Rückert <mrueckert> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, dickey, werner |
| Version: | Beta 2 plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bernhard Walle
2006-11-15 14:11:41 UTC
ok bernhard tested the rxvt-unicode package on 10.1, where the terminfo file is still in the rxvt-unicode package. so i run into trouble here. my current solution would be: 1. remove the file from the main terminfo package again. 2. split out terminfo-rxvt-unicode from the rxvt-unicode package so it can be installed seperately. than i can update rxvt-unicode via the buildservice. aj, werner any objections? You have a problem with a package from the buildservice. Does this occur with our delivered packages as well? the point is: including the terminfo file in the terminfo package breaks when we update rxvt-unicode e.g. from the buildservice. as long we stick to the shipped version everything is fine. but it looks like that upstream updated the terminfo file for 8.0. so we have a 7.9 terminfo and the 8.0 binary and they dont work together. i would like to avoid that for the future. as i test rxvt-unicode updates myself. so the split seems to be the best solution to me. Hmmm ... I prefere that the rxvt-unicode belongs to terminfo.
Beside this what is wrong with the current terminfo entry
for rxvt-unicode? Compare with the help of
infocmp -1 rxvt-unicode > terminfo.rxvt-unicode
The we need two rxvt-unicode entries one for rxvt-unicode-7.9 and one for rxvt-unicode-8.0 ... ok. i just compared the input files for 7.9 and 8.0 they are identical oO so it must be something else. :| will look further. really? I just compared the terminfo file that comes with 10.2-beta2 ncurses package and the one of your SUSE 10.1 package. They differ. Rejected for 10.2. Please discuss how to do it for 10.3 and later. Hmmm ... then there is a change which is 2in rxvt-basic because I generate the rxvt-unicode entry with an overwrite entry using the line use=rxvt-basic together with all required changes. OK all required changes for ncurses 5.5 but not ncurses 5.5.20060513. Andreas? I'm checking if ncurses terminfo entry is wrong for rxvt-unicode. Found following out: dch, dch1, hpa, and vpa missing, kbs wrong, kcub1, kcud1, kcuf1, and kcuu1 wrong in application mode. Go ahead and submit a new package *today* if there's really a bug... done dch/dch1 are implemented incorrectly in rxvt (and its so-called "clone"). I'll ignore any bug reports against ncurses which are due to adding those back. I havn't added dch/dch1 but simply undo the switch of rxvt+pcfkeys and vt220+keypad back to the old order to get the correct sequences of F1 upto F4. Then I've changed the rxvt+pcfkeys to reflect the application cursor and keypad mode (simply by replacing `[' with `O' for the cursor keys). This because the terminfo entries should describe the application cursor and keypad mode and not the command line mode. Ok. For the order of rxvt+pcfkeys vs vt220+keypad, I see that fix here:
20051015
+ correct order of use-clauses in rxvt-basic entry which made codes for
f1-f4 vt100-style rather than vt220-style (report by Gabor Z Papp).
rxvt and Linux console were (offhand) the only terminal types that initialized
to use the normal cursor keys rather than the application. Did you also modify
the Linux terminfo to use application keys?
Hmmm ... AFAIK the linux console use the same codes for command line and application cursor and keypad mode. I've only changed cvvis not using a block cursor. |