applications/i3
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update documentation to state that the configuration file is read by the custom parser as well.

Browse Source
This commit is contained in:
Ingo Bürk 2015-04-01 17:46:53 +02:00
parent d6f1e0c568
commit f35b666631
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/hacking-howto
View File

@ -686,9 +686,9 @@ 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). for user commands and 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/*.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
(highlighting files for other editors are welcome). (highlighting files for other editors are welcome).