[Cuis] Telling GitHub that our code is Smalltalk

[Angel Java Lopez]

I just found:

http://stackoverflow.com/questions/5318580/how-does-github-figure-out-a-projects-language

then

https://github.com/github/linguist

but I don't sure if it is used to classify a project. Is it used beyond
syntax highlighting?
Language detection

Linguist defines the list of all languages known to GitHub in a yaml
file<https://github.com/github/linguist/blob/master/lib/linguist/languages.yml>.
In order for a file to be highlighted, a language and lexer must be defined
there.

Most languages are detected by their file extension. This is the fastest
and most common situation.

For disambiguating between files with common extensions, we use a bayesian
classifier<https://github.com/github/linguist/blob/master/lib/linguist/classifier.rb>.
For an example, this helps us tell the difference between .h files which
could be either C, C++, or Obj-C.

and its issues:
https://github.com/github/linguist/issues



On Sun, Dec 30, 2012 at 9:53 AM, Juan Vuletich <juan at jvuletich.org> wrote:

> Hi Hannes,
>
> In addition to .pck we also have .cs files. I'd like to be able to tell
> GitHub that:
> *.pck is Smalltalk
> *.cs is Smalltalk
> The whole project is a Smalltalk project (so it shows in
> https://github.com/languages/**Smalltalk<https://github.com/languages/Smalltalk>)
>
> I found how to tell git that some files are in a specific language (see
> http://schacon.github.com/git/**gitattributes.html<http://schacon.github.com/git/gitattributes.html>), but smalltalk is not listed there. But if git already thinks that *.st
> means smalltalk, I believe the same could be done for *.pck and *.cs.
>
> Please folks, help me! I can't find a way to do it, but it should be
> possible!
>
> As a last resource, we could switch to *.pck.st and *.cs.st, but that
> would make things a bit more awkward for us, and especially for users of
> other Smalltalk environments...
>
> Thanks,
> Juan Vuletich
>
> H. Hirzel wrote:
>
>> And the packages files (*.pck) should have a Smalltalk extension *.st,
>> so e.g. *.pck.st so that the repos show up on the github Smalltalk
>> page.
>>
>>     https://github.com/languages/**Smalltalk<https://github.com/languages/Smalltalk>
>>
>> This makes it easier to see what is going on.
>>
>> For example Bernhard's Cuis fork appears there (no *.cs files) whereas
>> Juan's does not (many *.cs files,  counted as C-Sharp).
>>
>>
>>
>
>
> ______________________________**_________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org<http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jvuletich.org/pipermail/cuis_jvuletich.org/attachments/20121230/2149ad7c/attachment-0002.html>