Summary: | util-linux/cal.c displays wrong with dumb TERMinals | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Smith <xsmith> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Smith
2005-11-13 05:51:26 UTC
Which ebuild is this about? Works fine with util-linux-2.12r here. Yes, util-linux-2.12r. I was in an emacs shell buffer. It works for me in an xterm. Try TERM=dumb cal (In reply to comment #2) > I was in an emacs shell buffer. It works for me in an xterm. Try > TERM=dumb cal Works just fine. Not reproducible here, assigning to emacs. I can't reproduce this with "cal 11 2005". Are you using any fancy PROMPT_COMMAND, PS1 etc. also, try it in an Emacs started like this "emacs -q" -- if it persists, then you can rule out your own .emacs. (In reply to comment #4) I don't see how this is emacs related, given that it happens for me in an xterm window as well. cal 11 2005 will not be interesting, I think the bug is related to trying to highlight the current day. Today I get foxboro$ /usr/bin/cal December 2005 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 91 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 on dec 10. In an xterm window TERM=dumb is required. The output is the same. emacs -q then m-x shell is the same. No fancy PS1 etc, here is my environment: NNTPSERVER=newsgroups.comcast.net MANPATH=/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/i686-pc-linux-gnu/2.15.92.0.2/man:/usr/share/gcc-data/i686-pc-linux-gnu/3.3.6/man::/opt/sun-jdk-1.4.2.09/man:/usr/qt/3/doc/man HOSTNAME=foxboro SHELL=/bin/bash TERM=dumb HISTSIZE=5000 CVSROOT=/opt/cvs QTDIR=/usr/qt/3 HISTFILESIZE=5000 NAME=Chris Smith USER=csmith EMACS=t PRELINK_PATH_MASK=/usr/lib/gstreamer-0.8 GDK_USE_XFT=1 TERMCAP= XPID=7132 PYTHONDOCS=/usr/share/doc/python-docs-2.4.2/html PAGER=evenless CONFIG_PROTECT_MASK=/etc/terminfo COLUMNS=80 XINITRC=/home/csmith/.xinitrc MAIL=/var/mail/csmith PATH=/home/csmith/bin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3.6:/opt/sun-jdk-1.4.2.09/bin:/opt/sun-jdk-1.4.2.09/jre/bin:/opt/sun-jdk-1.4.2.09/jre/javaws:/usr/qt/3/bin:/usr/kde/3.4/bin:/bin:/usr/bin:/sbin:/usr/sbin DISTCC_LOG= PWD=/home/csmith JAVA_HOME=/opt/sun-jdk-1.4.2.09 EDITOR=emacsclient JAVAC=/opt/sun-jdk-1.4.2.09/bin/javac QMAKESPEC=linux-g++ KDEDIRS=/usr PS1=foxboro\$ DISTCC_VERBOSE=0 DCCC_PATH=/usr/lib/distcc/bin TEXINPUTS=.:/home/csmith/tex: JDK_HOME=/opt/sun-jdk-1.4.2.09 SHLVL=3 HOME=/home/csmith LESS=-R PYTHONPATH=/usr/lib/portage/pym LOGNAME=csmith CVS_RSH=ssh GCC_SPECS= ROOTPATH=/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3.6:/opt/sun-jdk-1.4.2.09/bin:/opt/sun-jdk-1.4.2.09/jre/bin:/opt/sun-jdk-1.4.2.09/jre/javaws:/usr/qt/3/bin:/usr/kde/3.4/sbin:/usr/kde/3.4/bin CLASSPATH=. LESSOPEN=|lesspipe.sh %s INFOPATH=/usr/share/info:/usr/share/binutils-data/i686-pc-linux-gnu/2.15.92.0.2/info:/usr/share/gcc-data/i686-pc-linux-gnu/3.3.6/info:/usr/share/info/emacs-21 DISPLAY=:0 OPENGL_PROFILE=xorg-x11 G_BROKEN_FILENAMES=1 CONFIG_PROTECT=/var/bind /usr/lib/X11/xkb /usr/kde/3.4/share/config /usr/kde/3.4/env /usr/kde/3.4/shutdown /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/xdvi/ /usr/share/config _=/bin/printenv OLDPWD=/home/csmith I see what you mean now. Punting this bug back to bug-wranglers. Someone maintaining sys-apps/util-linux should take a look at how cal tries to highlight the current day. It looks like its trying to do so without checking terminal capabilities, or at least making a bad choice in the case of TERM=dumb. what does this have to do with busybox or coreutils ? (In reply to comment #7) > what does this have to do with busybox or coreutils ? Nothing, the title line is screwed up, it says busybox because that was the only cal.c I could find when I went looking. well, setting TERM=dumb in an xterm window just dumb anyways :p ok, found the issue and fixed it with 2.12-r2 |