[Coco] OS9 text file format

[Jeff Teunissen]

Sorry, it's not D2Deek, it's just Deek. <https://github.com/Deek/CoCoC> is
the address.

On Mon, Jan 6, 2020, 4:02 PM Jeff Teunissen <deek at d2dc.net> wrote:

> I have somewhat solved this problem in my CoCoC Git repository by storing
> all data internally as linefeed-only, but using a script (which is included
> in the repository itself) to automatically convert text files into CR-only
> form when you check them out.
>
> I believe the repo is at <https://github.com/D2Deek/CoCoC>. In other
> news, I am getting very close to having a maintainable OS9 C compiler.
>
> On Mon, Jan 6, 2020, 12:27 PM Bill Pierce via Coco <coco at maltedmedia.com>
> wrote:
>
>> The real problem with the NitrOS9 repo needing to be converted (as
>> opposed to converting one file at a time) is there is literally over 1000
>> files in the repo...
>> Even as a batch operation, that's a lot of files to be converting. It
>> needs to be done once, and kept that way.
>> The problem is we have various people posting from various machine types
>> and no one is using any form of standard.
>> The PC build process doesn't care one way or the other, but when you move
>> things to NitrOS9 to use the sources there, it REALLY makes a difference.
>>
>> Bill P.
>>
>>
>> -----Original Message-----
>> From: Allen Huffman <alsplace at pobox.com>
>> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>> Sent: Mon, Jan 6, 2020 11:38 am
>> Subject: Re: [Coco] OS9 text file format
>>
>> In other environments, such as Microware official distributions, there
>> were native, Unix and PC hosts and the files were, I believe, in their
>> local formats. Microware switched to just PC hosted during my time there,
>> but I know for sure the native packages were all OS-9 format.
>>
>> Since people pull down one Disto to to build on Mac, PC, or Linux, which
>> did the district choose? I forgot what Mac uses. I just know I never cared
>> for PC files needing both a new line and carriage return at the end of each
>> line. :)
>>
>> The problem will happen as folks check stuff in and out.  A previous job
>> I had stored all the files in the repository in Unix format, and converted
>> on the way out automatically by the version control tool. But, sometimes
>> buttons didn’t get clicked correctly and you’d have a file with a block of
>> updates in it in the wrong format.
>>
>> Can our version control platform take care of this for us?
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>