Seems that 2013 will be a great year to Cuis, with Morphic 3 and (hopefully) a lot of usable packages!<div><br></div><div>Go Cuis Go! :)<br><br><div class="gmail_quote">2012/12/30 H. Hirzel <span dir="ltr"><<a href="mailto:hannes.hirzel@gmail.com" target="_blank">hannes.hirzel@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nice, I see it on<br>
<br>
<a href="https://github.com/languages/Smalltalk/updated" target="_blank">https://github.com/languages/Smalltalk/updated</a><br>
<br>
--Hannes<br>
<div class="im"><br>
On 12/30/12, Germán Arduino <<a href="mailto:garduino@gmail.com">garduino@gmail.com</a>> wrote:<br>
> Yes, I convertes some of mines and now I can saw it as Smalltalk :)<br>
><br>
><br>
> 2012/12/30 Juan Vuletich <<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a>><br>
><br>
>> Ok. Done. Uploaded a new prebuilt image and a couple of changesets. Now,<br>
>> when you save a package or change set, extension will be '.<a href="http://pck.st" target="_blank">pck.st</a>' and '.<br>
>> <a href="http://cs.st" target="_blank">cs.st</a>'. But you can load files without the '.st' suffix as usual. Now<br>
>> Cuis shows up at<br>
</div>>> <a href="https://github.com/languages/**Smalltalk/updated" target="_blank">https://github.com/languages/**Smalltalk/updated</a><<a href="https://github.com/languages/Smalltalk/updated" target="_blank">https://github.com/languages/Smalltalk/updated</a>>.<br>
<div><div class="h5">>><br>
>> There's no urgency in updating your repos, but if you do, I believe<br>
>> they'll get correctly identified as Smalltalk stuff by GitHub.<br>
>><br>
>> Cheers,<br>
>> Juan Vuletich<br>
>><br>
>> Germán Arduino wrote:<br>
>><br>
>>> ok, but how will we do the switch?<br>
>>><br>
>>> I mean, we need to rename all the packages in our local repos? and then<br>
>>> commit then to GitHub.... and then delete the old names in GitHub?<br>
>>><br>
>>> We will wait you release fixes in Cuis to consider the new names?<br>
>>><br>
>>><br>
>>><br>
>>> 2012/12/30 Juan Vuletich <<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a><br>
>>> <mailto:<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a>>><br>
>>><br>
>>><br>
>>> Hi Angel,<br>
>>><br>
>>> Yes. From all that, it seems that the way to do it would be to use<br>
>>> *.<a href="http://cs.st" target="_blank">cs.st</a> <<a href="http://cs.st" target="_blank">http://cs.st</a>> and *.<a href="http://pck.st" target="_blank">pck.st</a> <<a href="http://pck.st" target="_blank">http://pck.st</a>> file<br>
>>><br>
>>> extensions for ChangeSets and Packages. *.st is the only file<br>
>>> extension recognized as Smalltalk. It is a reasonable solution. I<br>
>>> thought that a manual override should be possible...<br>
>>><br>
>>> If we don't find another solution, maybe I'll switch to *.<a href="http://cs.st" target="_blank">cs.st</a><br>
>>> <<a href="http://cs.st" target="_blank">http://cs.st</a>> and *.<a href="http://pck.st" target="_blank">pck.st</a> <<a href="http://pck.st" target="_blank">http://pck.st</a>> as the defaults in the<br>
>>><br>
>>> code, and rename files in the Cuis repository. Then, it would be<br>
>>> good if folks start renaming .pck files in their own repository. I<br>
>>> guess supporting the older (current!) extensions will not be a<br>
>>> problem.<br>
>>><br>
>>> Cheers,<br>
>>> Juan Vuletich<br>
>>><br>
>>> Angel Java Lopez wrote:<br>
>>><br>
>>> I just found:<br>
>>><br>
</div></div>>>> <a href="http://stackoverflow.com/**questions/5318580/how-does-**" target="_blank">http://stackoverflow.com/**questions/5318580/how-does-**</a><br>
>>> github-figure-out-a-projects-**language<<a href="http://stackoverflow.com/questions/5318580/how-does-github-figure-out-a-projects-language" target="_blank">http://stackoverflow.com/questions/5318580/how-does-github-figure-out-a-projects-language</a>><br>
>>><br>
>>> then<br>
>>><br>
>>><br>
>>> <a href="https://github.com/github/**linguist" target="_blank">https://github.com/github/**linguist</a><<a href="https://github.com/github/linguist" target="_blank">https://github.com/github/linguist</a>><br>
<div class="im">>>><br>
>>> but I don't sure if it is used to classify a project. Is it<br>
>>> used beyond syntax highlighting?<br>
>>><br>
>>><br>
>>> Language detection<br>
>>><br>
>>> Linguist defines the list of all languages known to GitHub in<br>
>>> a yaml file<br>
</div>>>> <<a href="https://github.com/github/**linguist/blob/master/lib/**" target="_blank">https://github.com/github/**linguist/blob/master/lib/**</a><br>
>>> linguist/languages.yml<<a href="https://github.com/github/linguist/blob/master/lib/linguist/languages.yml" target="_blank">https://github.com/github/linguist/blob/master/lib/linguist/languages.yml</a>><br>
<div class="im">>>> >.<br>
>>> In order for a file to be highlighted, a language and lexer<br>
>>> must be defined there.<br>
>>><br>
>>><br>
>>> Most languages are detected by their file extension. This is<br>
>>> the fastest and most common situation.<br>
>>><br>
>>> For disambiguating between files with common extensions, we<br>
>>> use a bayesian classifier<br>
</div>>>> <<a href="https://github.com/github/**linguist/blob/master/lib/**" target="_blank">https://github.com/github/**linguist/blob/master/lib/**</a><br>
>>> linguist/classifier.rb<<a href="https://github.com/github/linguist/blob/master/lib/linguist/classifier.rb" target="_blank">https://github.com/github/linguist/blob/master/lib/linguist/classifier.rb</a>><br>
<div class="im">>>> >.<br>
>>> For an example, this helps us tell the difference between |.h|<br>
>>> files which could be either C, C++, or Obj-C.<br>
>>><br>
>>><br>
>>><br>
>>> and its issues:<br>
>>><br>
</div>>>> <a href="https://github.com/github/**linguist/issues" target="_blank">https://github.com/github/**linguist/issues</a><<a href="https://github.com/github/linguist/issues" target="_blank">https://github.com/github/linguist/issues</a>><br>
<div class="im">>>><br>
>>><br>
>>><br>
>>> On Sun, Dec 30, 2012 at 9:53 AM, Juan Vuletich<br>
>>> <<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a> <mailto:<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a>><br>
>>> <mailto:<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a> <mailto:<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a>>>> wrote:<br>
>>><br>
>>> Hi Hannes,<br>
>>><br>
>>> In addition to .pck we also have .cs files. I'd like to be<br>
>>> able to<br>
>>> tell GitHub that:<br>
>>> *.pck is Smalltalk<br>
>>> *.cs is Smalltalk<br>
>>> The whole project is a Smalltalk project (so it shows in<br>
>>><br>
</div>>>> <a href="https://github.com/languages/**Smalltalk" target="_blank">https://github.com/languages/**Smalltalk</a><<a href="https://github.com/languages/Smalltalk" target="_blank">https://github.com/languages/Smalltalk</a>>)<br>
<div class="im">>>><br>
>>> I found how to tell git that some files are in a specific<br>
>>> language<br>
>>> (see<br>
</div>>>> <a href="http://schacon.github.com/git/**gitattributes.html" target="_blank">http://schacon.github.com/git/**gitattributes.html</a><<a href="http://schacon.github.com/git/gitattributes.html" target="_blank">http://schacon.github.com/git/gitattributes.html</a>>),<br>
<div class="im">>>> but<br>
>>> smalltalk is not listed there. But if git already thinks<br>
>>> that *.st<br>
>>> means smalltalk, I believe the same could be done for<br>
>>> *.pck and *.cs.<br>
>>><br>
>>> Please folks, help me! I can't find a way to do it, but it<br>
>>> should<br>
>>> be possible!<br>
>>><br>
>>> As a last resource, we could switch to *.<a href="http://pck.st" target="_blank">pck.st</a><br>
>>> <<a href="http://pck.st" target="_blank">http://pck.st</a>> <<a href="http://pck.st" target="_blank">http://pck.st</a>><br>
>>> and *.<a href="http://cs.st" target="_blank">cs.st</a> <<a href="http://cs.st" target="_blank">http://cs.st</a>> <<a href="http://cs.st" target="_blank">http://cs.st</a>>, but that would<br>
>>><br>
>>> make things a bit more<br>
>>><br>
>>> awkward for us, and especially for users of other Smalltalk<br>
>>> environments...<br>
>>><br>
>>> Thanks,<br>
>>> Juan Vuletich<br>
>>><br>
>>> H. Hirzel wrote:<br>
>>><br>
>>> And the packages files (*.pck) should have a Smalltalk<br>
>>> extension *.st,<br>
>>> so e.g. *.<a href="http://pck.st" target="_blank">pck.st</a> <<a href="http://pck.st" target="_blank">http://pck.st</a>> <<a href="http://pck.st" target="_blank">http://pck.st</a>> so<br>
>>><br>
>>> that the repos show up on<br>
>>><br>
>>> the github Smalltalk<br>
>>> page.<br>
>>><br>
>>><br>
</div>>>> <a href="https://github.com/languages/**Smalltalk" target="_blank">https://github.com/languages/**Smalltalk</a><<a href="https://github.com/languages/Smalltalk" target="_blank">https://github.com/languages/Smalltalk</a>><br>
<div class="im">>>><br>
>>> This makes it easier to see what is going on.<br>
>>><br>
>>> For example Bernhard's Cuis fork appears there (no<br>
>>> *.cs files)<br>
>>> whereas<br>
>>> Juan's does not (many *.cs files, counted as C-Sharp).<br>
>>><br>
>>><br>
>>><br>
</div>>>> ______________________________**_________________<br>
<div class="im">>>> Cuis mailing list<br>
>>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a> <mailto:<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a>><br>
>>> <mailto:<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a> <mailto:<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a>>><br>
>>><br>
>>><br>
</div>>>> <a href="http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org</a><<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>
>>><br>
>>><br>
>>><br>
>>> ______________________________**_________________<br>
<div class="im">>>> Cuis mailing list<br>
>>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a> <mailto:<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a>><br>
>>><br>
>>><br>
</div>>>> <a href="http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org</a><<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>
<div class="im">>>> Cuis mailing list<br>
>>> <a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a> <mailto:<a href="mailto:Cuis@jvuletich.org">Cuis@jvuletich.org</a>><br>
>>><br>
</div>>>> <a href="http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org</a><<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>
>>><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><<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>
>> ______________________________**_________________<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><<a href="http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org" target="_blank">http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org</a>><br>
<div class="HOEnZb"><div class="h5">>><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><br clear="all"><div><br></div>-- <br>============================================<br>Germán S. Arduino <gsa @ <a href="http://arsol.net" target="_blank">arsol.net</a>> Twitter: garduino<br>
Arduino Software <a href="http://www.arduinosoftware.com" target="_blank">http://www.arduinosoftware.com</a><br>PasswordsPro <a href="http://www.passwordspro.com" target="_blank">http://www.passwordspro.com</a><br><a href="http://greensecure.blogspot.com" target="_blank">greensecure.blogspot.com</a> <a href="http://germanarduino.blogspot.com" target="_blank">germanarduino.blogspot.com</a><br>
============================================
</div>