On 12/20/13, 12:15 PM, Ke Carlton wrote:
> Noticed that Github has been incorrectly detecting project type for some of
> my projects. Solution turns out to be quite straight forward – you just
> need to ensure your third party libraries are placed in a folder that will
> be ignored.


Yeah, my problem is that I use .inc for my library files, and most of
what I have on github are library files. Since .inc is so common, Github
ignores them and doesn't know what to do with my repos. (It also doesn't
highlight them.)

It would be nice for Github to allow us to choose the default language
for our repos. One thing that is in our control - we can standardize on
file extensions. (And we need to add those other extensions to this
list:
https://github.com/github/linguist/blob/master/lib/linguist/languages.yml)

Personally, I like to have one file extension for my template files
(Lasso mixed in with HTML) from my library files (all lasso code). Since
my library files only have Lasso code, they never have <?...?> or [].
(I've also set my text editor to be aware of the different file
extensions and highlight accordingly.)

I suggest we keep .lasso for the template files and come up with
something else for the library files. Possible suggestions:
.lal
.lasl
.las
.llib
.lso
.lsol

What do other people think? Do we even need this distinction?

Thanks,
Brad


Tags: #standards #github
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>