(I am sending this again because you may not have gotten it the first time.)
Justin,
The ninth character of good and bad lines differs.
The ninth character of the good line is char#32=space.
The ninth character of the bad lines is char#160=32+128.
My sloppy keyboarding must have produced the special character.
Too bad "vi" does not reveal the difference.
Here is the "c" program that I used:
:r do.c =(
#include <stdio.h>
main(){
int c;
while((c=getchar()) !=EOF){
printf("%d\n",c);
}
exit(0);
}
Jim Hertzler
http://dynamicaviation.com
<To: Justin Pryzby <[EMAIL PROTECTED]>
<Date: Mon, 06 Feb 2006 17:34:40 -0500
<Subject: Re:Re: Bug#351695: Simple Bash command gives unexpected error message.
<From: Jim Hertzler <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
<
<.............................................................
<Start:What I just Did. (In responce to your email.)
<.............................................................
<
<Debian:XShells:XTerm
<
<cd Mail
<
<sh do.sh
<.............................................................
<End:What I just Did.
<.............................................................
<
<Where :r do.sh=(
<cp -bvpi tmp jay_060206m.to
<read
<cp -bvpi tmp jay_060206m.to
<read
<cp -bvpi tmp jay_060206m.to
<read
<cp -bvpi tmp jay_060206m.to
<)
<
<.............................................................
<Start:Result.
<.............................................................
<
<The first three "cp"'s each produced an error message:
< cp: invalid option --
< Try `cp --help' for more information
<The last "cp" was successful with the message:
< `tmp' -> `jay_060206m.to'
<.............................................................
<End:Result.
<.............................................................
<
<I edited the saved history file named "tmp" to produce the
< shell script named "do.sh".
<I can not spot any difference between the four lines.
<I thought "vi" would show any special characters.
<I did not expect this procedure to reproduce the effect,
< but it did.
<
<I must be doing something dumb.
<
<Jim Hertzler
<http://dynamicaviation.com
<
<<Date: Mon, 6 Feb 2006 14:45:43 -0500
<<To: Jim Hertzler <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
<<Subject: Re: Bug#351695: Simple Bash command gives unexpected error message.
<<From: Justin Pryzby <[EMAIL PROTECTED]>
<<
<<On Mon, Feb 06, 2006 at 02:46:07PM -0500, Jim Hertzler wrote:
<<> Package: bash
<<> Version: 2.05b.0(1)-release
<<>
<<> Output of "sh --version">/tmp/tmp:
<<> GNU bash, version 2.05b.0(1)-release (i386-pc-linux-gnu)
<<> Copyright (C) 2002 Free Software Foundation, Inc.
<<>
<<> Output of "cp -bvpi tmp jay_060202m.to 2>/tmp/tmp":
<<> cp: invalid option --
<<> Try `cp --help' for more information.
<<>
<<> Last few line of "history>tmp":
<<> 774 ls -rlt ~/Sh |grep txt
<<> 775 pdftotext Qte1286719.pdf
<<> 776 ls -rlt
<<> 777 vi Qte1286719.txt
<<> 778 ls -rlt
<<> 779 cp -bvpi tmp icc_joanne_060206m.txt
<<> 780 ls -rlt
<<> 781 cp -bvpi tmp jay_060206m.to
<<> 782 cp -bvpi tmp jay_060206m.to
<<> 783 cp -bvpi tmp jay_060206m.to
<<> 784 cp -bvpi tmp jay_060206m.to
<<> 785 history
<<> 786 history>tmp
<<>
<<> I cursered up to repeat the "cp" command and got the same error message.
<<> I retyped the command and it worked fine with no error message.
<<> I cursered up agian to the orginal command and the error message was
repeated.
<<> This computer is an old Pentium III.
<<> "xdm" is handling four (4) screens with twm.
<<> Six or seven xterms are running on one screen.
<<Can you reproduce this in a newly spawned bash instance?
<<
<<Justin
