Hi guys,
I've fixed this infamous "\r" issue (as of rev.911). This was a bug in my
jallib.py script, during sample generation. This bug only occured on OS
using "\r\n" (or any linefeed with 2 chars), which resulted in "\r\r\n"
instead of "\r\n" ("\r\n" is mac format, "\r\r\n" is known to be Seb's
format). (Joep, I remember you're under kind-of cygwin which gives "\r\n"
-- mine gives "\n" as standard linefeed char-- , Albert are you under Mac OS
?)
I've also changed the way reindentation is done: the script now uses
OS-defined linefeed, instead of hard-coded "\n". This should be transparent.
Let me know if you have any more problems. And if you have time to
re-generate samples (I could do this, but under Linux, "\n" is the standard
linefeed chars, and there wasn't any problem about it).
Cheers,
Seb
>> My editor call this mac-format. We've been there before...
>
>
> So has the bug... I'm digging this.
>
> Seb
>
>
--
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
