Fixed G-code

[TannerReynolds]

• Changed from data to programming -> CNC Programmers create gcode files that instruct machines where to move and what to do
• Gave a color (#ff4d6b)
• Added a commonly used file type for CNC programming (.cnc)

Description

G-code files are instructions written or generated by CNC/machine programmers to instruct machines where to move and what to do (Spindle speeds, move speed, feedrate, tooling, etc.) on a line-by-line basis. As a CNC/Machine programmer, I can tell you that they are not data files, just like any other high level language, they are written instructions to be interpreted by the machine. I have also included a file type that is commonly used for CNC programming.

Checklist:

• I am associating a language with a new file extension. (Not new to GCode programming, but new to Github)

  • [?] The new extension is used in hundreds of repositories on GitHub.com Because it is currently not a programming language w/color, I cannot see the repository count. I do see thousands of gcode files with this extension, though.
    • Search results for each extension:
      • https://github.com/search?q=extension%3Acnc+NOT+nothack&type=Code
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • https://github.com/TannerReynolds/GHL
    • Sample license(s): No License for sample
  • I have included a change to the heuristics to distinguish my language from others using the same extension. (While syntax is mostly the same, different machinery use different syntax, this language is a hard one to detect using heuristics)

• I am adding a new language.

  • The extension of the new language is used in hundreds of repositories on GitHub.com.
    • Search results for each extension:
      • https://github.com/search?utf8=%E2%9C%93&type=Code&ref=searchresults&q=extension%3AFOOBAR+KEYWORDS+NOT+nothack
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • [URL to each sample source, if applicable]
    • Sample license(s):
  • I have included a syntax highlighting grammar: https://github-lightshow.herokuapp.com/
  • [] I have updated the heuristics to distinguish my language from others using the same extension.

• I am fixing a misclassified language

  • I have included a new sample for the misclassified language:
    • Sample source(s):
      • https://github.com/TannerReynolds/GHL
    • Sample license(s): No license for sample
  • I have included a change to the heuristics to distinguish my language from others using the same extension.

• I am changing the source of a syntax highlighting grammar

  • Old: https://github-lightshow.herokuapp.com/
  • New: https://github-lightshow.herokuapp.com/

• I am updating a grammar submodule

• I am adding new or changing current functionality

  • I have added or updated the tests for the new or changed functionality.

[TannerReynolds]

@pchaigno I went ahead and fixed the commits/PR comment

[pchaigno]

Thanks for the pull request!

I left a couple comments below.

As a CNC/Machine programmer, I can tell you that they are not data files, just like any other high level language, they are written instructions to be interpreted by the machine.

Are these files written by hand by humans or through a GUI/higher-level language?

[TannerReynolds]

Are these files written by hand by humans or through a GUI/higher-level language?

@pchaigno

Just like html, css, and others, it depends. Small-medium sized manufacturers, hobbyists, people who prefer it, people who need lots of control over the machines, and even some bigger manufacturers have people who write all the code themselves. Usually manufacturers that require a large volume of different code to be written daily, and that have lots of money, will opt-out for some sort of generator, that is easier to teach, but far more expensive to use. Otherwise people generally tend to prefer hand writing the code, due to added control over the machines. Bigger manufacturers that create large volume of the same product will also opt for hand written code. Bigger manufacturers thay create large volumes of custom products per day (countertop fabricators, for example) will want to not hand write code, or they will generate a base using a GUI, and hand edit the code. I for one know how to do both, and decide on whether I'm going to code it myself, or use CAM to do it, on a use-by-use basis. I apologize if anything doesnt make much sense, I'm trying my best to explain how the G-code programming world works, as thos sort of programming is very different from traditional programming

[TannerReynolds]

Addressed concerns @pchaigno

[stale]

This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

[pchaigno]

LGTM, but would probably need other opinions on the change to type: programming.

[Alhadis]

LGTM. 👍 I'm not familiar with G-code, but I've also seen people writing it out by hand, so this amendment is justified.