[Cuis] Telling GitHub that our code is Smalltalk
Germán Arduino
garduino at gmail.com
Sun Dec 30 17:49:46 CST 2012
Seems that 2013 will be a great year to Cuis, with Morphic 3 and
(hopefully) a lot of usable packages!
Go Cuis Go! :)
2012/12/30 H. Hirzel <hannes.hirzel at gmail.com>
> Nice, I see it on
>
> https://github.com/languages/Smalltalk/updated
>
> --Hannes
>
> On 12/30/12, Germán Arduino <garduino at gmail.com> wrote:
> > Yes, I convertes some of mines and now I can saw it as Smalltalk :)
> >
> >
> > 2012/12/30 Juan Vuletich <juan at jvuletich.org>
> >
> >> Ok. Done. Uploaded a new prebuilt image and a couple of changesets. Now,
> >> when you save a package or change set, extension will be '.pck.st' and
> '.
> >> cs.st'. But you can load files without the '.st' suffix as usual. Now
> >> Cuis shows up at
> >> https://github.com/languages/**Smalltalk/updated<
> https://github.com/languages/Smalltalk/updated>.
> >>
> >> There's no urgency in updating your repos, but if you do, I believe
> >> they'll get correctly identified as Smalltalk stuff by GitHub.
> >>
> >> Cheers,
> >> Juan Vuletich
> >>
> >> Germán Arduino wrote:
> >>
> >>> ok, but how will we do the switch?
> >>>
> >>> I mean, we need to rename all the packages in our local repos? and then
> >>> commit then to GitHub.... and then delete the old names in GitHub?
> >>>
> >>> We will wait you release fixes in Cuis to consider the new names?
> >>>
> >>>
> >>>
> >>> 2012/12/30 Juan Vuletich <juan at jvuletich.org
> >>> <mailto:juan at jvuletich.org>>
> >>>
> >>>
> >>> Hi Angel,
> >>>
> >>> Yes. From all that, it seems that the way to do it would be to use
> >>> *.cs.st <http://cs.st> and *.pck.st <http://pck.st> file
> >>>
> >>> extensions for ChangeSets and Packages. *.st is the only file
> >>> extension recognized as Smalltalk. It is a reasonable solution. I
> >>> thought that a manual override should be possible...
> >>>
> >>> If we don't find another solution, maybe I'll switch to *.cs.st
> >>> <http://cs.st> and *.pck.st <http://pck.st> as the defaults in the
> >>>
> >>> code, and rename files in the Cuis repository. Then, it would be
> >>> good if folks start renaming .pck files in their own repository. I
> >>> guess supporting the older (current!) extensions will not be a
> >>> problem.
> >>>
> >>> Cheers,
> >>> Juan Vuletich
> >>>
> >>> Angel Java Lopez wrote:
> >>>
> >>> I just found:
> >>>
> >>> http://stackoverflow.com/**questions/5318580/how-does-**
> >>> github-figure-out-a-projects-**language<
> http://stackoverflow.com/questions/5318580/how-does-github-figure-out-a-projects-language
> >
> >>>
> >>> then
> >>>
> >>>
> >>> https://github.com/github/**linguist<
> 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<
> 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<
> 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<
> https://github.com/github/linguist/issues>
> >>>
> >>>
> >>>
> >>> On Sun, Dec 30, 2012 at 9:53 AM, Juan Vuletich
> >>> <juan at jvuletich.org <mailto:juan at jvuletich.org>
> >>> <mailto:juan at jvuletich.org <mailto: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
> >>> <http://pck.st> <http://pck.st>
> >>> and *.cs.st <http://cs.st> <http://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 <http://pck.st> <http://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 <mailto:Cuis at jvuletich.org>
> >>> <mailto:Cuis at jvuletich.org <mailto:Cuis at jvuletich.org>>
> >>>
> >>>
> >>> http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org<
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org>
> >>>
> >>>
> >>>
> ------------------------------**------------------------------**
> >>> ------------
> >>>
> >>>
> >>>
> >>> ______________________________**_________________
> >>> Cuis mailing list
> >>> Cuis at jvuletich.org <mailto:Cuis at jvuletich.org>
> >>>
> >>>
> >>> http://jvuletich.org/mailman/**listinfo/cuis_jvuletich.org<
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org>
> >>>
> >>>
> >>>
> >>> ______________________________**_________________
> >>> Cuis mailing list
> >>> Cuis at jvuletich.org <mailto:Cuis at jvuletich.org>
> >>>
> >>> http://jvuletich.org/mailman/**listinfo/cuis_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<
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org>
> >>>
> >>>
> >>
> >>
> >> ______________________________**_________________
> >> Cuis mailing list
> >> Cuis at jvuletich.org
> >> http://jvuletich.org/mailman/**listinfo/cuis_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
>
--
============================================
Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
Arduino Software http://www.arduinosoftware.com
PasswordsPro http://www.passwordspro.com
greensecure.blogspot.com germanarduino.blogspot.com
============================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jvuletich.org/pipermail/cuis_jvuletich.org/attachments/20121230/c4bef48c/attachment-0002.html>
More information about the Cuis
mailing list