potatoesmaster/i3-vim-syntax

Vim syntax for i3 window manager config

⚠️ This syntax file is not maintained anymore. Feel free to take over or try some alternative (eg: i3config.vim).

---

This is a Vim syntax file for i3 config file.

Using it

You can install it using a Vim plugin manager (Vundle, Pathogen, …) or just by putting i3.vim in your ~/.vim/syntax directory.

I recommend you to add # vim:filetype=i3 at the end of your i3 config file, unless you really want to type :set filetype=i3 every time you edit this file.

i3-vim-syntax's Issues

Missing config keywords

Hello. Some keywords are missing. Examples:
hide_edge_borders
workspace_auto_back_and_forth

Complete list: http://code.stapelberg.de/git/i3/tree/parser-specs/config.spec

Project name doesn't match standard convention

It'd be nice to have it be vim-i3-syntax or vim-i3 to match up with the standard convention.

--pango_markup could be set with a different hl

For instance in mode --pango_markup "rofi (Qutebrowser" {,
'--pango_markup "rofi (Qutebrowser"' is highlighted with the same color (and I suppose hlGroup)

Line-continuation not handled properly

When splitting a line like so
the continuation is not syntax highlighted.

Weirdness

h and v are highlighted out of context

h and v are properly highlighted when used as abbreviations for "horizontal" and "vertical" respectively, but are incorrectly highlighted when used to reference the "h" and "v" keys.

Missing inline comments

At least for me, inline comments are not working.

Archive the repo

https://help.github.com/articles/archiving-a-github-repository/

Syntax file rewrite

The syntax file needs a rewrite, for several reasons:

• The current highlighting does not take account of the context (Are we in the middle of a command? In a binding declaration?). I use syn region for exec commands and string and nextgroup= at several places, but it does not work that well as of now and need to be rethought.
• client.* keywords are not highlighted, because client itself is a keyword and take precedence.
• Command scopes are ignored.

i3 generate its syntax from custom files, parsed by a perl script (spec files, script). These files could be used to generate a syntax file.