# Niche languages plugins

**URL:** <https://discuss.kakoune.com/t/niche-languages-plugins/639>\
**Category:** Plugins\
**Tags:** language\
**Created:** [June 29, 2019, 8:06pm UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639 "2019-06-29T20:06:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![TeddyDD](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/teddydd/32/21_2.png) [@TeddyDD](https://discuss.kakoune.com/u/TeddyDD)\
**Post date:** [June 29, 2019, 8:06pm UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/1 "2019-06-29T20:06:18Z")

</div>

I have soft spot on niche languages. Since creating basic language support plugin is easy in Kakoune I went ahead and wrote these plugins. I don’t think they deserve separate threads.

## Mint

[Mint](https://www.mint-lang.com/) is strict language for writing SPAs. It’s runtime uses React under the hood.

> **[GitHub - TeddyDD/kakoune-mint: Mint language support for Kakoune](https://github.com/teddydd/kakoune-mint)**
>
> Mint language support for Kakoune

## Context Free Art

[CFDG](https://www.contextfreeart.org/) is language for generating graphics with context free grammars. It’s great tool for generative art 💚

> **[GitHub - TeddyDD/kakoune-cfdg: Context Free Art support for Kakoune editor](https://github.com/teddydd/kakoune-cfdg)**
>
> Context Free Art support for Kakoune editor

## Pixilang

[Pixilang](http://www.warmplace.ru/soft/pixilang/) is

> pixel-oriented programming language for small graphics/sound applications and experiments

according to the website. I didn’t used it much yet. I wrote the plugin so I can learn in comfortable environment 😉

> **[GitHub - TeddyDD/kakoune-pixilang: Pixilang support for Kakoune text editor](https://github.com/teddydd/kakoune-pixilang)**
>
> Pixilang support for Kakoune text editor

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [June 30, 2019, 6:22am UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/2 "2019-06-30T06:22:15Z")

</div>

Language plugins are small and simple. Maybe just include them to Kakoune?

---

<div class="post-metadata">

**Author:** ![himi](https://discuss.kakoune.com/letter_avatar_proxy/v4/letter/h/848f3c/32.png) [@himi](https://discuss.kakoune.com/u/himi)\
**Post date:** [July 2, 2019, 10:04am UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/3 "2019-07-02T10:04:13Z")

</div>

While developing them and getting them to the point you might be willing to send a pull request it makes sense to have a public space to put them . . . I’m in the same position trying to write a puppet plugin.

Also, small and simple is very relative to your skill levels!

---

<div class="post-metadata">

**Author:** ![TeddyDD](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/teddydd/32/21_2.png) [@TeddyDD](https://discuss.kakoune.com/u/TeddyDD)\
**Post date:** [July 2, 2019, 9:49pm UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/4 "2019-07-02T21:49:26Z")

</div>

I might open pr with Mint when it reaches 1.0, other than that I’m prefer to maintain these off-tree.

---

<div class="post-metadata">

**Author:** ![bugabinga](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/bugabinga/32/144_2.png) [@bugabinga](https://discuss.kakoune.com/u/bugabinga)\
**Post date:** [July 3, 2019, 7:43am UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/5 "2019-07-03T07:43:27Z")

</div>

A dedicated “incubation” repo could be nice for such plugins.  
It costs however in terms of manpower and organization.

---

<div class="post-metadata">

**Author:** ![robertmeta](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/robertmeta/32/833_2.png) [@robertmeta](https://discuss.kakoune.com/u/robertmeta)\
**Post date:** [July 6, 2019, 5:15pm UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/6 "2019-07-06T17:15:37Z")

</div>

Alternatively, we could have a kakoune-polyglot (akin to [https://github.com/sheerun/vim-polyglot](https://github.com/sheerun/vim-polyglot)). Vim-polyglot is generally more up to date / correct compared to the baked in scripts.

I think we need to sort of decide as a community do we want to bake in stuff, or depend on 3rd parties to do it.

---

<div class="post-metadata">

**Author:** ![andreyorst](https://discuss.kakoune.com/user_avatar/discuss.kakoune.com/andreyorst/32/29_2.png) [@andreyorst](https://discuss.kakoune.com/u/andreyorst)\
**Post date:** [July 6, 2019, 7:37pm UTC](https://discuss.kakoune.com/t/niche-languages-plugins/639/7 "2019-07-06T19:37:46Z")

</div>

I’m not sure about this part when it comes to Kakoune:

> Vim-polyglot is generally more up to date / correct compared to the baked in scripts.

The problem I see here is overriding highlighters that is unfortunately not really as easy to do. Well, perhaps if such repo provides, say, C++ language highlighting, it could possibly drop highlighters that Kakoune declares and then provide it’s own, but it’s kinda ineffective way to do this. Vim has some ways to decide [if syntax should be applied](https://github.com/sheerun/vim-polyglot/blob/3ddca5da461ebfaa82104f82e3cbf19d1c326ade/syntax/c.vim#L10) which isn’t as easy to do in Kakoune.
