On Sat, Feb 27, 2010 at 10:39 AM, Roman Kyrylych <[email protected]> wrote: > On Sat, Feb 27, 2010 at 01:38, Thomas Bächler <[email protected]> wrote: >> Am 26.02.2010 22:01, schrieb Aaron Griffin: >>> Your terminal is configured wrong. What is $TERM set to? If you are in >>> screen it should be screen (or some variant such as screen-bce) > > TERM is linux. Changing it does not help. > >> "xm console" is a rather primitive terminal, not nearly as powerful as >> screen. > > Ah, didn't know this. > > I tried iptraf, and the output was a broken too (in another way), > so it's not just pacman that experiences this problem. > > However, -Sy falls back gracefully, i.e. > via lish (screen to /dev/hvc0): > testing 14.5K 52.4K/s 00:00:00 > core 36.1K 85.7K/s 00:00:00 > extra 445.6K 60.8K/s 00:00:07 > via ssh: > testing 14.5K 56.2K/s 00:00:00 [#####################] > 100% > core 36.1K 91.1K/s 00:00:00 [#####################] > 100% > extra 152.0K 75.8K/s 00:00:03 [#######--------------] > 34% > > -Ss is broken too. > It looks like the breakage occurs on spaces after some column, > so -Ql doesn't break even very long lines, > because there is no space in package paths. > > It would be nice to have -Ss/-Si/-Qi usable too, > but it seems like a very low priority > (I don't know if there are many people who run pacman > on such limited terminals as xm console)
Define usable. Nothing you posted showed any sort of corruption whatsoever, it just linebreaked where you didn't expect. If you are using a crappy terminal that doesn't support queries for size, then use this as a workaround: pacman -Qi glibc | cat -Dan
