Mike Frysinger wrote:
> Configuration Information:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-pc-linux-gnu-gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
> -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -O2 -march=k8 -pipe
> -D_FORTIFY_SOURCE=1
> uname output: Linux vapier 2.6.14.3-grsec #4 PREEMPT Wed Dec 21 16:10:15 EST
> 2005 x86_64 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux
> Machine Type: x86_64-pc-linux-gnu
>
> Bash Version: 3.1
> Patch Level: 5
> Release Status: release
>
> Description:
> when you first launch bash-3.1, the long-line wrapping ability appears to be
> broken. very long lines at first will start to wrap one character too soon
> and overwrite the current line rather than start on the next line. resizing
> the terminal, executing a program, or similar operations appear to "fix" the
> issue, it's just the initial run where things are screwed up. observered on
> both Gentoo and Debian. bash-3.0 works correctly.
>
> Repeat-By:
> - run 'bash'
> - hold down a letter until it gets to the edge of the terminal
> - observe the line wrapping too soon and overwriting current line
> - hit enter/resize terminal/etc...
> - hold down a letter until it gets to the edge of the terminal
> - observe the line wrapping properly now
I can't reproduce it on MacOS X or Linux, using Terminal, xterm, or
aterm. It sounds like readline is getting an incorrect value for
the terminal autowrap capability.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live Strong.
Chet Ramey, ITS, CWRU [EMAIL PROTECTED] http://tiswww.tis.case.edu/~chet/
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
