Bart Lateur wrote: > > On Tue, 14 Nov 2000 17:36:30 -0500, Chris Nandor wrote: > > > thing is printed > >>> > > to STDOUT all looks fine, but the copied line > >>> > > > >>> > > \xDB\xAA\t\n > >>> > > > >>> > > pastes as > >>> > > > >>> > > \xDB\xAA\n\n > >>> > > > >>> > > where \n is mac CR. any idea what's up??? if instead i print OF to HD, > >>> > > it prints > >>> > > > >>> > > \xDB\xAA\t\n > >>> > > > >>> > > just as it should. > > >I am not sure what the bug is here. What is this about "paste" and "copy"? > > I think I do have a clue what this person is talking about. I, too, have > occasionally noticed that if you copy text from MacPerl's output window, > and paste it into a text editor, you may paste some slightly different > text than what's been printed out. Er... I'm not sure I can think of an > example. Let's try: > > ($\, $,) = ("\n", "\t"); > for(32..126) { > print $_, chr; > } > > This should print a character table, for each character first the Ascii > code, then a tab, then the character, then a newline. But if you > copy/paste the text, the line for space (Ascii code 32) isn't > copied/pasted exactly. Er... yes: I get "32\n \n". > > Yup, it is a bug. I'm not sure I really think it's that important... ;-) > Thanks Bart, Yes. This is just what I was talking about. It's important only sometimes, most when I use regex to search a text file, copy the results and paste into a text editor's find window (to edit the file): the find fails. Not important really, but sometimes a minor annoyance. I'd be curious to know the cause. -R # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org