[Cuis] About cr/lf issues in MSWindows

[H. Hirzel]

Ok to summarize


You suggest to have
    git config   --global   core.autocrlf   false

(= the default)

and have an individual
  .gitattributes

file per repository?

With at least

*.st text
*.md text
*.png binary
*.jpg binary
*.mcz binary

Note aside: I think it is useful for porting to store the original
Monticello *.mcz files (from Squeaksource etc) along with the port.
This safes time for doing code reviews.

--Hannes

On 1/22/13, Angel Java Lopez <ajlopez2000 at gmail.com> wrote:
> The problem with global settings, is when you start to work on different
> projects, your global settings could interfere with the expected work on
> that projects.
>
> So, I would go for local settings per project. And maybe, explicit
> specifying the text files:
>
> *.st text
> *.md text
> ...
> *.png binary
> ...
>
> Hahaha!... I'm ot a GitHub expert, but a daily user, yes
>
> Angel "ACommitToGitHubADayKeepsTheDoctorAway" Lopez
>
> On Tue, Jan 22, 2013 at 7:24 AM, H. Hirzel <hannes.hirzel at gmail.com> wrote:
>
>> Thank you Angel, as our github expert in residence for these links
>> about line end problems with github.
>>
>> The reference
>> http://timclem.wordpress.com/2012/03/01/mind-the-end-of-your-line/ gives
>>
>> "Git’s primary solution to all this is to specify that LF is the best
>> way to store line endings for text files in a Git repository’s object
>> database. "
>>
>> and
>>
>> "
>> core.autocrlf = false
>>
>> – This is the default, but most people are encouraged to change this
>> immediately. The result of using false is that Git doesn’t ever mess
>> with line endings on your file
>> "
>>
>>
>>
>> I use Windows 7 with a git bash shell.
>>
>> I had not done yet a change so I do now
>>
>>     git config --global core.autocrlf true
>>
>> on my MINGW32 git bash shell , right?
>>
>> Is this enough for Cuis/Squeak/Pharo use? Or do I need to go for a
>> .gitattributes file?
>>
>> Kind regards
>> Hannes
>>
>> On 1/22/13, Angel Java Lopez <ajlopez2000 at gmail.com> wrote:
>> > Ah! This is a discussion about text files in repo, no text file
>> processing
>> > in Smalltalk.
>> >
>> > Then:
>> >
>> http://stackoverflow.com/questions/170961/whats-the-best-crlf-handling-strategy-with-git
>> > https://help.github.com/articles/dealing-with-line-endings
>> > and specially
>> > http://timclem.wordpress.com/2012/03/01/mind-the-end-of-your-line/
>> >
>> > Angel "GitHub" Lopez ;-)
>> >
>> > On Tue, Jan 22, 2013 at 5:36 AM, H. Hirzel <hannes.hirzel at gmail.com>
>> wrote:
>> >
>> >> Hello Juan
>> >>
>> >> On 1/22/13, Juan Vuletich <juan at jvuletich.org> wrote:
>> >> > Germán Arduino wrote:
>> >> ..
>> >> >>
>> >> >> Just noticed also that in Windows I have also the bad formatting
>> >> >> with
>> >> >> the cr/lf as if they were not converted.
>> >> >>
>> >> >>
>> >> >
>> >> > I use Cuis on Mac and Windows all the time. I never had any issue
>> >> > with
>> >> > cr/lf. Maybe you're editing files in notepad.exe?
>> >>
>> >> Yes, I do that sometimes, e.g. to edit README.md files. I realize that
>> >> after some editing operations  lines are double spaced.
>> >>
>> >>
>> >> Or transferring them
>> >> > with a "smart" tool that thinks it must do conversions?
>> >>
>> >> An alternative tool I use is Notepad++
>> >> http://www.notepad-plus-plus.org/
>> >>
>> >>
>> >> In any case,
>> >> > prepare a list of steps to reproduce the problems you see, and I'll
>> >> > take
>> >> > a look (as usual).
>> >>
>> >>
>> >> Yes
>> >>
>> >> > Cheers,
>> >> > Juan Vuletich
>> >>
>> >>
>> >> Regards
>> >> Hannes Hirzel
>> >>
>> >> _______________________________________________
>> >> Cuis mailing list
>> >> Cuis at jvuletich.org
>> >> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>> >>
>> >
>>
>> _______________________________________________
>> Cuis mailing list
>> Cuis at jvuletich.org
>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>
>