Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On 2005-12-24 00:06:07 +0100, [EMAIL PROTECTED] wrote: It's a regression. I thing regressions should prevent packages from entering testing otherwise code can degrade if nobody fixes it. The correct way would be to ask for a tag regression in the BTS, then use -T regression in apt-listbugs. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
reassign 348111 bash merge 343471 348111 thanks -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On Thu, Jan 26, 2006 at 11:51:51AM +0100, Vincent Lefevre wrote: On 2005-12-24 00:06:07 +0100, [EMAIL PROTECTED] wrote: It's a regression. I thing regressions should prevent packages from entering testing otherwise code can degrade if nobody fixes it. The correct way would be to ask for a tag regression in the BTS, then use -T regression in apt-listbugs. Which would be great, but not be used enough to actually help people prevent regressions.. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Why didn't you prevent bash 3.1-1 entering to testing if you knew about this fucking regression? I really think bash 3.0 should be in testing until a fix for this bug is found. Prueba el Nuevo Correo Terra; Seguro, R�pido, Fiable.
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On Fri, Dec 23, 2005 at 09:36:47PM +0100, [EMAIL PROTECTED] wrote: Why didn't you prevent bash 3.1-1 entering to testing if you knew about this fucking regression? I really think bash 3.0 should be in testing until a fix for this bug is found. Why? It was rated a 'normal' severity bug by the submitter, and nobody changed it. I think this is the correct severity. Since it isn't RC, it doesn't prevent testing propogation. Is there some reason why this is highly important to you? -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Justin Pryzby wrote: On Fri, Dec 23, 2005 at 09:36:47PM +0100, [EMAIL PROTECTED] wrote: Why didn't you prevent bash 3.1-1 entering to testing if you knew about this fucking regression? I really think bash 3.0 should be in testing until a fix for this bug is found. Why? It was rated a 'normal' severity bug by the submitter, and nobody changed it. I think this is the correct severity. Since it isn't RC, it doesn't prevent testing propagation. Is there some reason why this is highly important to you? It's a regression. I thing regressions should prevent packages from entering testing otherwise code can degrade if nobody fixes it. I had to downgrade to 3.0 because of this regression. Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On Sat, Dec 24, 2005 at 12:06:07AM +0100, [EMAIL PROTECTED] wrote: Justin Pryzby wrote: On Fri, Dec 23, 2005 at 09:36:47PM +0100, [EMAIL PROTECTED] wrote: Why didn't you prevent bash 3.1-1 entering to testing if you knew about this fucking regression? I really think bash 3.0 should be in testing until a fix for this bug is found. Why? It was rated a 'normal' severity bug by the submitter, and nobody changed it. I think this is the correct severity. Since it isn't RC, it doesn't prevent testing propagation. Is there some reason why this is highly important to you? It's a regression. I thing regressions should prevent packages from entering testing otherwise code can degrade if nobody fixes it. I had to downgrade to 3.0 because of this regression. Regressions are bad, of course. But, whereas the regression was known before testing propogation, there were of course other changes made, which fixed other problems, and included other enhancements, such has possibly made bash more easily maintainable. -- Clear skies, Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On 2005-12-16 00:49:11 +0100, Matthias Klose wrote: please could you explain sometimes? I've done more tests. The problem always occurs (not only in xterm), except when I do a reset from bash. To reproduce it, press 'a' and wait for the a's to reach the right of the terminal. I have the prompt: [EMAIL PROTECTED]:~$ Then I press 'a' and wait: [EMAIL PROTECTED]:~$ aaa bash: aa: command not found [EMAIL PROTECTED]:~$ See? Then I type 'reset' and retry, try again after starting a bash subshell, and another time after exiting this subshell: [EMAIL PROTECTED]:~$ aa bash: aa: command not found [EMAIL PROTECTED]:~$ bash [EMAIL PROTECTED]:~$ aaa bash: aa: command not found [EMAIL PROTECTED]:~$ exit [EMAIL PROTECTED]:~$ aa bash: aa: command not found [EMAIL PROTECTED]:~$ Same problem after removing by .bash_profile and .bashrc files. But this problem doesn't occur when executing bash --norc. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On 2005-12-16 10:42:52 +0100, Vincent Lefevre wrote: Same problem after removing by .bash_profile and .bashrc files. But this problem doesn't occur when executing bash --norc. Still without my .bash_profile and .bashrc files: When I start bash with bash --rcfile /etc/bash.bashrc, the problem occurs. But if I type bash --norc then source /etc/bash.bashrc, it doesn't occur. What's the difference between them? -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Same problem on PowerPC after upgrading from bash 3.0-17 to bash 3.1-1 (bash 3.0-17 didn't have this problem). The problem isn't related to $TERM, I can reproduce it with TERM=vt100 for instance. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
I have been trying the Vincent tests. My results: # TEST 1 ## [EMAIL PROTECTED]:~$ aaa... = BAD [EMAIL PROTECTED]:~$ [After Enter] aaa.. = OK # TEST 2 ## [EMAIL PROTECTED]:~$ aaa... = BAD [EMAIL PROTECTED]:~$ [Starting a subshell] bash [EMAIL PROTECTED]:~$ aaa... = BAD [EMAIL PROTECTED]:~$ [After Enter] aaa..= OK [EMAIL PROTECTED]:~$ [Existing subshell] exit [EMAIL PROTECTED]:~$ aaa... = OK # TEST 3 ## [EMAIL PROTECTED]:~$ [Starting a subshell] bash [EMAIL PROTECTED]:~$ aaa... = BAD [EMAIL PROTECTED]:~$ [After Enter] aaa..= OK [EMAIL PROTECTED]:~$ [Existing subshell] exit [EMAIL PROTECTED]:~$ aaa... = OK # TEST 4 ## [EMAIL PROTECTED]:~$ reset [EMAIL PROTECTED]:~$ aaa... = OK # TEST 5 ## [EMAIL PROTECTED]:~$ [Starting a subshell] dash [EMAIL PROTECTED]:~$ aaa... = OK [EMAIL PROTECTED]:~$ [Existing subshell] exit [EMAIL PROTECTED]:~$ aaa... = OK # TEST 6 ## [EMAIL PROTECTED]:~$ [Starting a subshell] bash -norc [EMAIL PROTECTED]:~$ aaa... = OK etc. Same results are obtained from a terminal emulator (xterm, gnome-terminal) and from the console. Greetings, Luis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Vincent Lefevre wrote: On 2005-12-16 10:42:52 +0100, Vincent Lefevre wrote: Same problem after removing by .bash_profile and .bashrc files. But this problem doesn't occur when executing bash --norc. Still without my .bash_profile and .bashrc files: When I start bash with bash --rcfile /etc/bash.bashrc, the problem occurs. But if I type bash --norc then source /etc/bash.bashrc, it doesn't occur. What's the difference between them? The difference is that readline initializes itself after /etc/bash.bashrc is read in the former case, and before it's read in the latter. That would seem to point to /etc/bash.bashrc. Your initial message leads me to believe that readline is getting wrong information when it initially reads the terminal capabilities, and the value for `xn' is wrong. What's in debian's /etc/bash.bashrc, and has it been changed on your system? (I can't reproduce this at all, so someone else who can will have to feed information into this process.) 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://cnswww.cns.cwru.edu/~chet/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On 2005-12-16 13:47:21 -0500, Chet Ramey wrote: Vincent Lefevre wrote: When I start bash with bash --rcfile /etc/bash.bashrc, the problem occurs. But if I type bash --norc then source /etc/bash.bashrc, it doesn't occur. What's the difference between them? The difference is that readline initializes itself after /etc/bash.bashrc is read in the former case, and before it's read in the latter. That would seem to point to /etc/bash.bashrc. Possibly another problem: it seems that --rcfile is buggy. dixsept:~ bash --norc bash-3.1$ dixsept:~ bash --rcfile /dev/null [EMAIL PROTECTED]:~$ Shouldn't I have got the same prompt? -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On 2005-12-16 13:47:21 -0500, Chet Ramey wrote:
What's in debian's /etc/bash.bashrc, and has it been changed on your
system?
Without the comments:
[ -z $PS1 ] return
shopt -s checkwinsize
if [ -z $debian_chroot ] [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
PS1='${debian_chroot:+($debian_chroot)[EMAIL PROTECTED]:\w\$ '
and /etc/debian_chroot doesn't exist. I've never changed
/etc/bash.bashrc (this is Debian's default file).
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Vincent Lefevre wrote: On 2005-12-16 13:47:21 -0500, Chet Ramey wrote: Vincent Lefevre wrote: When I start bash with bash --rcfile /etc/bash.bashrc, the problem occurs. But if I type bash --norc then source /etc/bash.bashrc, it doesn't occur. What's the difference between them? The difference is that readline initializes itself after /etc/bash.bashrc is read in the former case, and before it's read in the latter. That would seem to point to /etc/bash.bashrc. Possibly another problem: it seems that --rcfile is buggy. dixsept:~ bash --norc bash-3.1$ dixsept:~ bash --rcfile /dev/null [EMAIL PROTECTED]:~$ Shouldn't I have got the same prompt? Nope. Debian compiles bash to source /etc/bash.bashrc at startup, before the user rcfile is sourced. If --norc is supplied, that is suppressed. 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://cnswww.cns.cwru.edu/~chet/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
On 2005-12-16 20:53:13 -0500, Chet Ramey wrote: Vincent Lefevre wrote: dixsept:~ bash --norc bash-3.1$ dixsept:~ bash --rcfile /dev/null [EMAIL PROTECTED]:~$ Shouldn't I have got the same prompt? Nope. Debian compiles bash to source /etc/bash.bashrc at startup, before the user rcfile is sourced. If --norc is supplied, that is suppressed. OK, then this is the man page that is incorrect. I've just reported this bug. -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Package: bash Version: 3.1-1 Severity: normal With the bash command line (interactive shell), when the command I'm typing reaches the last column of the terminal, this sometimes goes on at the first column of the same line instead of the next line. This problem occurs in an xterm, even an xterm I've just opened. I have no such problem with zsh and with the cooked mode (e.g. with cat /dev/null). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4-20051012 Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) Versions of packages bash depends on: ii base-files3.1.9 Debian base system miscellaneous f ii debianutils 2.15.2 Miscellaneous utilities specific t ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an ii libncurses5 5.5-1 Shared libraries for terminal hand bash recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Vincent Lefevre writes: Package: bash Version: 3.1-1 Severity: normal With the bash command line (interactive shell), when the command I'm typing reaches the last column of the terminal, this sometimes goes on at the first column of the same line instead of the next line. This problem occurs in an xterm, even an xterm I've just opened. I have no such problem with zsh and with the cooked mode (e.g. with cat /dev/null). Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) please could you explain sometimes? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
