Hi Seb,
Sebastien Lelong wrote: > By "correctly formatted", I mean that if there's a mix with linefeed > chars (eg. "\n" and "\r\n") vim, guessing which is the one, will > choose "\n" and thus will display "\r" as part of the line content, > not linefeed. I haven't used the reindent command with Jallib.py very much, therefore I didn't care to report a little problem I have with it. But now the subject is 'hot' I'll take my chance.... My platform (eComStation,OS/2) uses the 0x0D0A convention for line end. After a reindent this has been changed to 0x0D0D0A (thus a 0x0D is added by jallib.py). When I reindent that output a second time the 0x0D0D0A is not changed anymore. I suppose the same happens under Windows. The extra 0x0D is no problem for JalV2, and it is also easy to remove from the source file, but better there would be no additional 0x0D in the first place. I thought it must be possible in a Python program to determine the platform on which it is running and react accordingly w.r.t. line end convention. I searched and found a string sys.platform which displays as 'os2knix' on my PC. I found also a 'platform' which could be useful. platform.platform() returns 'OS-2-1-i386-32bit' on my PC. Please take this in consideration (low priority). Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
