hacking-howto: point out that the parser is not used for the configfile (yet) (Thanks fernandotcl)

This commit is contained in:
Michael Stapelberg 2012-01-16 23:41:24 +00:00
parent fa4a909f34
commit 518d210a9b
1 changed files with 2 additions and 1 deletions

View File

@ -683,7 +683,8 @@ all commands.
In earlier versions of i3, interpreting these commands was done using lex and In earlier versions of i3, interpreting these commands was done using lex and
yacc, but experience has shown that lex and yacc are not well suited for our yacc, but experience has shown that lex and yacc are not well suited for our
command language. Therefore, starting from version 4.2, we use a custom parser. command language. Therefore, starting from version 4.2, we use a custom parser
for user commands (not yet for the configuration file).
The input specification for this parser can be found in the file The input specification for this parser can be found in the file
+parser-specs/commands.spec+. Should you happen to use Vim as an editor, use +parser-specs/commands.spec+. Should you happen to use Vim as an editor, use
:source parser-specs/highlighting.vim to get syntax highlighting for this file :source parser-specs/highlighting.vim to get syntax highlighting for this file