copy - strange behaviour when using shell

[Raziel]

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?

[tonyw]

No, it can't be fixed, there is nothing wrong.

The behaviour is according to the ANSI standard.

[Raziel]

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

[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!

[nbache]

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

[Slayer]

lol

too easy nbache!

[tonyw]

Damn! Why didn't I think of that?

On ya, Niels!