All 'acknowledged' Dyalog APL fileextensions should be recognized by GitHub about link HOT 15 CLOSED

@stampes Would it be acceptable to add a .gitattributes file to each repository?

If so, add such a file to the root of relevant repositories, containing:

*.apl? linguist-language=APL

I've added this file to this repository, and GitHub now seems to colour .aplf files appropriately. See e.g. this one.

from link.

I looked into this, and it may turn out to be a problem. They write that (my emphasis):

We try only to add new extensions once they have some usage on GitHub. In most cases we prefer that extensions be in use in hundreds of repositories before supporting them (...)

Maybe this is an argument for abandoning the nameclass-specific extensions?

from link.

We will look at that! Thanks

from link.

You really ought to go to the Lingust guys and add aplf as an extension for apl files, may I suggest looking at this guide: https://github.com/github/linguist/blob/master/CONTRIBUTING.md

from link.

We have a lot of repositories with APL code in an Enterprise GitHub installation and prefer not to include .gitattibutes in all these.

from link.

We are reaching out to "the Linguist guys" to understand whether they will waive the stated requirement of "hundreds of repositories" as they clearly did for apl and dyalog, and accept a set of new extensions - at least aplf to begin with (but we also need apla aplo apln aplc and apli, if we are to support the full set according to the current design).

We are also investigating whether a Git Enterprise installation can have a custom default .gitattributes file, as a temporary work-around.

from link.

@mkromberg Why not ask for *.apl? so we don't have to bother them again with any future extensions. We can even justify it by saying that *.apl? is like the existing *.apl but with a specification of the content.

from link.

@mkromberg I don't think you can set this "system wide". At least I found this issue: github-linguist/linguist#4283

from link.

Why not ask for *.apl?

Can you use patterns?

from link.

@e9gille See #52 (comment)

from link.

@e9gille See #52 (comment)

Sure, it just isn't obvious to me that patterns are allowed/supported in the https://github.com/github/linguist/blob/master/lib/linguist/languages.yml file.

from link.

@e9gille Turns out:

No, it doesn't.

We (I'm a co-maintainer of github-linguist) don't receive that many requests to add new extensions that we have felt a need to add this for now.

pchaigno

from link.

I think we have done as much as we can at this point; Dyalog will send a broadcast out to the user community to raise awareness and accelerate use of the new extensions and ultimately adoption by GitHub.

from link.

Closing the discussion. Not a Link issue.

from link.

Might not be a Link issue - but I do see this as a Dyalog issue...

from link.