On Thu, Apr 07, 2011 at 07:51:53PM +0200, Louis Hoefler wrote:
> I never had problems with LF line endings in my batch files/source files/
> whatever
> I am on windows 7 with vs2010.
>
> The only thing whitch troubles me is the linux shell interpreter who can not
> live with CR-LF line endings and
On Thu, Apr 7, 2011 at 4:56 PM, Wilson, Ronald wrote:
> How is abandoning backwards compatibility in any way linked to winning?
> Frankly,
> I’m surprised at how often MS seems to get beat up on this list; many of us
> are
> Windows users and developers. Personally it gets under my skin; maybe
> Basically, Unix won. I think Windows is the last system maintaining
> backwards compatibility to systems that predate the rise of Unix.
> Pretty much everything else either was designed with the Unix model in
> mind, or converted to it somewhere along the way.
How is abandoning backwards compati
On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó wrote:
> Another thing that would be a bonus for cross-platform development
> would be to change the encoding of the text files. In modern Linux it
> is utf-8. And in modern Windows, it is a code page that depends on the
> country but it is different fro
Getting pedantic here...
On Thu, 7 Apr 2011 12:55:14 -0400
Richard Hipp wrote:
> On Thu, Apr 7, 2011 at 12:42 PM, Ramon Ribó wrote:
> > MacOSX is using UNIX line ending since more than 10 years-ago.
> > In modern computers, there are two options:
> > Unix/MacOSX: LF
> Also, Solaris, AIX, HPUX, N
abort and fix.
>>>
>>> This is a good option for me. Some files are OK with CRLFs
and others are not. I like being able to choose.
>>>
>>> -Clark
>>>
>>>
>>>
>>> - Original Message -
>>> From:Martin Gagno
>>
>> >> --
>> >> Martin
>> >>
>> >> Le 2011-04-07 à 10:43, Clark Christensen a écrit :
>> >>
>> >>> I'm using fossil version [1d93222627] 2011-03-01 19:04:32 UTC
>> >>>
>> >>> With this
Good to know!
This came about from supporting data files supplied by various users
and I still receive the occasional [CR] only data file?
On Thu, Apr 7, 2011 at 12:33 PM, Konstantin Khomoutov
wrote:
> On Thu, 7 Apr 2011 12:04:44 -0400
> sky5w...@gmail.com wrote:
>
>> I would be immensely confus
for me. Some files are OK with CRLFs and others
> are not. I like being able to choose.
> >>>
> >>> -Clark
> >>>
> >>>
> >>>
> >>> - Original Message -
> >>> From:Martin Gagnon
> >>> To:Fo
Fossil warns about CRLF line ends on commit, and allows
>>> me to commit anyway, or abort and fix.
>>>
>>> This is a good option for me. Some files are OK with CRLFs and others are
>>> not. I like being able to choose.
>>>
>>> -Clark
>>
On Thu, 7 Apr 2011 12:04:44 -0400
sky5w...@gmail.com wrote:
> I would be immensely confused if my SCM was modifying the contents of
> my source code and/or support documents.
> Given that MacOS has yet another EOL = [CR], it is better for your own
> code to manage distribution effects.
I think it'
gt; -Clark
>>
>>
>>
>> - Original Message -
>> From:Martin Gagnon
>> To:Fossil Users Mailing List
>> Cc:
>> Sent:Thursday, April 7, 2011 4:11 AM
>> Subject:[fossil-users] CRLF conversion on windows
>>
>> Hi, Is there any p
; From:Martin Gagnon
> To:Fossil Users Mailing List
> Cc:
> Sent:Thursday, April 7, 2011 4:11 AM
> Subject:[fossil-users] CRLF conversion on windows
>
> Hi, Is there any plan for CRLF conversion under windows?
>
> This would be very usefull for cross platform projects. E
Clark
- Original Message -
From:Martin Gagnon
To:Fossil Users Mailing List
Cc:
Sent:Thursday, April 7, 2011 4:11 AM
Subject:[fossil-users] CRLF conversion on windows
Hi, Is there any plan for CRLF conversion under windows?
This would be very usefull for cross platform projects. Espec
Hi, Is there any plan for CRLF conversion under windows?
This would be very usefull for cross platform projects. Especially
when using Visual Studio on the Windows side, which silently add CRLF
line ending on a LF only file which give you a mixed line ending file
(got bunch of ^M when editing file
15 matches
Mail list logo
