[vim/vim] Add .roto filetype for Roto (PR #19195)

6 views
Skip to first unread message

Bendik Samseth

unread,
Jan 16, 2026, 6:06:38 PMJan 16
to vim/vim, Subscribed

This is only meant to provide minimal filetype recognition as the first step to get some level of editor support for the language. It can be extended once the language has a (more) stable syntax.

See https://github.com/NLnetLabs/roto.

Note: I have no affiliation with NLnetLabs, I simply would like to improve the editor support in order to make it easier to use.

Note 2: I have tried to figure out all the places where I should make changes. If I've missed something I'm happy to update the PR.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/19195

Commit Summary

  • 3e1e544 Add .roto filetype for Roto

File Changes

(5 files)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19195@github.com>

Christian Brabandt

unread,
Jan 17, 2026, 5:12:45 AMJan 17
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19195)

is this actually used much?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19195/c3762987749@github.com>

Bendik Samseth

unread,
Jan 17, 2026, 5:41:55 PMJan 17
to vim/vim, Subscribed
bsamseth left a comment (vim/vim#19195)

I don't have any particular insight into that, but no, I can't imagine it has a lot of real world users yet. It was somewhat recently presented at a Rust conference, as well as a Rust-focused podcast. This is how I learned about it, and at least to me it ticks a lot of boxes. More importantly though, I'd be surprised if it went away, seeing as the organization behind it is developing it actively and has it as a part of their core product.

I'm totally fine if this is to early days to be included. I just saw heaps of filetypes I had never heard of and figured the bar was low.

Thanks for your time either way!


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19195/c3764422149@github.com>

Christian Brabandt

unread,
Jan 18, 2026, 4:22:51 PMJan 18
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19195)

I think this is a bit too early. If this gains momentum we can include it later. Feel free to re-submit in a year or so. Thanks for understanding.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19195/c3765760720@github.com>

Christian Brabandt

unread,
Jan 18, 2026, 4:22:55 PMJan 18
to vim/vim, Subscribed

Closed #19195.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19195/issue_event/22124715635@github.com>

Reply all
Reply to author
Forward
0 new messages