thread: alternative language modules; language support requests

[NotAShelf]

Tracking issue for alterative language modules. This is both a place to track progress on language modules that are to be added, or to request new ones.

• Assembly - languages/assembly: init #447
• Bash languages/bash: add LSP #142
• Haskell - Haskell: init #426
• Kotlin - languages/kotlin: init #390
• lua feat: lua language support and neodev.nvim #139
• Nim languages/nim: init #205
• Terraform languages: add terraform language support #182
• R R: adding LSP #378
• ruby Add ruby language support to neovim-flake (WIP) #89 (closed, ruby is pain)

[horriblename]

I can add lua support, I have it setup already anyway

[NotAShelf]

would be nice, I'll take a look at bash and kotlin then

[Soliprem]

It'd be nice to add Julia and R. They're very commonly used in data science (in fact, I'm pretty sure R is still more used than Python)

[NotAShelf]

I'd be happy to take a look at Julia support sometime, but R is unfortunately far outside my area of expertise - would be better if someone with experience in using R took it on.

[Soliprem]

maybe there's another flake that already implements it so we can take a look at how they integrate the toolset? I tried looking into it but didn't find any myself.

[Soliprem]

In terms of useful tooling, this is a great data science config imo:
https://github.com/jmbuhr/quarto-nvim-kickstarter
Quarto is very commonly used, and the way they implement otter might even be cool for other uses (e.g., writing code snippets in normal markdown).

I notice it uses luarocks.nvim to installl image.nvim, but I assume it can be handled by the system luarocks compiler, seeing as that was the original method and seems to still be supported. Or we can simply not implement image.nvim, as it does depend on kitty and that's a pretty big assumption to make about a user's setup.

[NotAShelf]

image.nvim is already implemented under utilty/images.

[Soliprem]

oh, missed it. RN I'm working on the R lsp and formatter (I found both packages in nixpkgs, so I assume it shouldn't take too long. I can begin testing on my local instance pretty soon)