I think we're going to need .nas added to another language and a heuristic as .nas appears to be quite popular and they don't all appear to be Nasal. From a quick look, quite a few appear to be Assembly.

I have included a real-world usage sample for all extensions added in this PR:

• Sample source(s): samples/Nasal/damage.nas

  • [URL to each sample source, if applicable]

Where did you get the sample from? We need the URL to that source in this section of the template.

Normally peeps want support for a language so they can have syntax highlighting on GitHub. How about adding https://github.com/RenanMsV/nasal-vscode to this PR? I'm guessing this is for the same language and seems to do a good job highlighting the sample you've included as can be seen here

I have updated the post.

But I am unsure how to update the heuristic.

But I am unsure how to update the heuristic.

Sorry about the delay in getting back to this.

From a quick look at Nasal and Assembly, I think we might be OK with leaving it to the classifier as the two appear to be quite distinct from each other.

So the next steps would be to:

1. Add .nas to the list of extensions for "Assembly"
2. Add two representative real-world samples of Assembly .nas files
3. Add another real-world representative sample of Nasal

All of this would happen in this PR.

If all goes well, all the tests should pass without any thing else, but we'll see 🤞.

I've finished off this PR. I got the colour from the Nasal logo at https://wiki.flightgear.org/Nasal_Console

The only thing I've not done is add a syntax highlighting grammar as I've just noticed that the one I referenced before is licensed under the GPL which we can't use.