Onefetch languages checklist

[spenserblack]

Note

I've been pinging a lot of onefetch contributors for help with languages I'm unfamiliar with. If anyone finds this annoying, please let me know. 🙂

This is the list of languages supported by onefetch, as of when this issue was created. This tool should support most of these in order to replace tokei.

• Abap
• ABNF
• Ada
• Assembly
• AutoHotKey
• Bash This will be Shell
• C
• Ceylon
• Clojure
• CMake
• CoffeeScript
• ColdFusion
• Coq
• Cpp
• Crystal
• CSharp
• Css
• D
• Dart
• Dockerfile
• Elisp
• Elixir
• Elm
• Emojicode
• Erlang
• Fish
• Forth (Add Forth language o2sh/onefetch#35)
• FortranLegacy
• FortranModern
• FSharp
• GdScript
• Glsl (Add GLSL language support #490 o2sh/onefetch#824)
• Go
• Graphql
• Groovy
• Haskell
• Haxe (add haxe language support o2sh/onefetch#394)
• Hcl (Add HCL Support o2sh/onefetch#438)
• Hlsl (Hlsl support o2sh/onefetch#1082)
• HolyC
• Html
• Idris (Add Idris support o2sh/onefetch#54)
• Java
• JavaScript
• Json
• Jsonnet
• Jsx (NOTE: Like linguist, this will probably be combined with JavaScript)
• Julia
• Jupyter
• Kotlin
• Lisp (Common Lisp)
• LLVM (Add LLVM language support o2sh/onefetch#507)
• Lua
• Makefile
• Markdown
• Nim
• Nix
• Objective C (Add support for Objective-C o2sh/onefetch#49)
• OCaml
• Odin
• Org (Added org-mode support o2sh/onefetch#155)
• Pascal (Add Pascal support o2sh/onefetch#989)
• Perl
• Perl6 Raku (add Roku (Perl 6) ASCII logo o2sh/onefetch#303)
• Php
• PowerShell
• Processing (Nice to have: support for the Processing Language o2sh/onefetch#326)
• Prolog (Ascii for Prolog  o2sh/onefetch#94)
• Protobuf Protocol Buffers
• PureScript
• Python
• Qml (add qml support o2sh/onefetch#362)
• R
• Racket (Add Racket language logo o2sh/onefetch#124)
• Renpy
• Ruby
• Rust
• Sass
• Scala
• Scheme
• Sh (Shell)
• Solidity
• Sql
• Svelte
• Swift
• SystemVerilog (adding language systemverilog #490 o2sh/onefetch#797)
• Tcl (ASCII for Tcl and PureScript o2sh/onefetch#66)
• Tex (Add Tex support o2sh/onefetch#92 and Updated Tex's ASCII logo o2sh/onefetch#247)
• Toml
• Tsx (See note on JSX)
• TypeScript
• Vala (add support for Vala o2sh/onefetch#324)
• Verilog (adding language verilog #490 o2sh/onefetch#789)
• Vhdl (Add language support for VHDL o2sh/onefetch#632)
• VimScript
• VisualBasic (VisualBasic language support o2sh/onefetch#867)
• Vue
• WebAssembly (Add WebAssembly language support o2sh/onefetch#495)
• Wolfram (Add Wolfram language support o2sh/onefetch#609)
• Xaml (o2sh/onefetch@05fec5a)
• Xml
• XSL (adding language xsl #490 o2sh/onefetch#798)
• Yaml
• Zig
• Zsh This will be Shell

Made with:

#!/usr/bin/env ruby
require 'yaml'

filepath = ARGV[0]

langs = YAML.load_file(filepath)

langs.keys.each do |lang|
  puts "- [ ] #{lang}"
end

script.rb path/to/onefetch/languages.yaml

---

Languages added later

• Arduino (New language: Arduino o2sh/onefetch#1176)
• Modelica (Language support for Modelica o2sh/onefetch#1262)
• Agda (Add Agda to languages.yaml o2sh/onefetch#1216)
• Twig (feat: add Twig language support with ASCII art and color scheme o2sh/onefetch#1257) (reverted with o2sh/onefetch@324f3df)
• V (Added the V programming language o2sh/onefetch#1252)
• CUDA (Added CUDA to languages.yaml o2sh/onefetch#940)
• ATS (Language Support for ATS o2sh/onefetch#523)
• Oz (lang: Adding Oz programming language o2sh/onefetch#1280)
• SVG (Add svg language support o2sh/onefetch#1266)
• Astro (Add astro framework support o2sh/onefetch#1317)

[spenserblack]

Related: #22

[spenserblack]

@atluft Pinging you since you made o2sh/onefetch#789

I'm completely unfamiliar with Verilog. Would you be willing to make a PR to add support? If/when onefetch switches to this, then onefetch will be able to detect *.v as verilog 😉

[spenserblack]

@o2sh, @jake-87 pinging you guys since you added support for fortran modern and fortran legacy. Not familiar with Fortran at all. Is there a reason that onefetch separated Fortran into modern and legacy besides the fact that that's what tokei did? Is the difference between the two significant enough to be considered different languages?
Also, I'm noticing that some of the extensions tokei uses for modern are mapped to Fortran Free Form in linguist, so would that be a better name?

Edit

since you added support for fortran modern and fortran legacy

In onefetch, I mean.

[jake-87]

@spenserblack To make a long story short (and off the top of my head, mostly), they were implemented as different things mostly because they're really quite different languages - you can't take legacy fortran code and make it compile in modern fortran without quite a few changes, and vice-versa (The syntax may initially look similar, but there's many differences in how you structure it and what restrictions are placed on the programmer). If they're easy to tell apart (and they are, because they use different file extensions), then it makes more sense to consider them as seperate languages.

As for whether "Fortran Free Form" would be a better name, you could consider it as such, although I'd personally expect "Legacy FORTRAN" to then be "Fortran fixed form", which seems confusing, so maybe "Legacy" and "Modern" are better names.

[spenserblack]

@jake-87 Thanks for the info!

[spenserblack]

Hi @alessandroasm! I'm pinging you because you've previously contributed to onefetch to support LLVM. We're considering changing our language detection tool to gengo. Gengo needs a bit more language support, so, if you're interested, we'd love your help!

[spenserblack]

Hi @spsandwichman! I'm pinging you because you've previously contributed to onefetch to support Odin. We're considering changing our language detection tool to gengo. Gengo needs a bit more language support, so, if you're interested, we'd love your help!