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