Page 2 of 2
Re: copy - strange behaviour when using shell
Posted: Mon Mar 05, 2012 10:06 am
by Raziel
tonyw wrote:Actually, a cut 'n' paste from that last quote shows the problem just fine.
What happens is that the console (once it has received the SO (Shift Out) character), adds 0x80 to every character before it is displayed, thus in effect selecting an alternate character set. This state is reset by a SI (Shift In) issued by the Shell before every command prompt.
Thanks.
Can it be "fixed" (for a copy operation at least)?
If i understand it right it isn't a bug per se, but triggered by those special char 0 byte files.
If you would need them for further testing i could try to pack the archive and send it your way?
Re: copy - strange behaviour when using shell
Posted: Mon Mar 05, 2012 1:07 pm
by tonyw
No, it can't be fixed, there is nothing wrong.
The behaviour is according to the ANSI standard.
Re: copy - strange behaviour when using shell
Posted: Mon Mar 05, 2012 1:51 pm
by Raziel
tonyw wrote:No, it can't be fixed, there is nothing wrong.
The behaviour is according to the ANSI standard.
Okidoki
Then i get rid of those bad files
Thank you
Re: copy - strange behaviour when using shell
Posted: Tue Mar 06, 2012 6:17 am
by Slayer
Perhaps put them in archive?
Tar then Bz2
Used to be the way I'd store everything once lzx was discontinued, Tar was good for recognising softlinks and have the -h switch that write the actual file not the softlink if desired, worse for space for sure but more portable? but I'm wondering way of topic here!
Re: copy - strange behaviour when using shell
Posted: Tue Mar 06, 2012 10:33 pm
by nbache
Raziel wrote:Can it be "fixed" (for a copy operation at least)?
Of course. The fix is to use the QUIET switch in your copy command
.
Best regards,
Niels
Re: copy - strange behaviour when using shell
Posted: Tue Mar 06, 2012 10:51 pm
by Slayer
lol
too easy nbache!
Re: copy - strange behaviour when using shell
Posted: Tue Mar 06, 2012 11:04 pm
by tonyw
Damn! Why didn't I think of that?
On ya, Niels!