Re: [i3] lexer config parser, Identifying the line in my config which is causing the error.

From: Scott Benjamin <scott.benjamin@xxxxxxxxx>
To: i3-discuss@xxxxxxxxxxxxx
Date: Thu, 11 Feb 2010 22:56:29 -0800

Thanks for the reply Michael.

I tried to run i3 with the debug level set but it kept complaining about the
options not being valid. Perhaps I'm overlooking something.

I will probably hop onto the IRC channel and see if I can get some support
there as well.

Thanks,

Scott

On Thu, Feb 11, 2010 at 12:57 AM, Michael Stapelberg <
michael+i3@xxxxxxxxxxxxx <michael%2Bi3@xxxxxxxxxxxxx>> wrote:

Hi Scott,

Excerpts from Scott Benjamin's message of Do Feb 11 06:17:57 +0100 2010:

I've been using I3 for about a month now, loving it very much.

Nice to hear :-).

My question is, is there an easy way to help identify the line that is
causing the error? I've tried scanning the output to identify the exact
line but I'm not seeing it.

Unfortunately not yet, proper error handling is still on the TODO list. The
only thing you can do for now is starting i3 with full debug level (-V -d
all)
and check the logfile for the lines which the parser correctly interpreted.
The lines in your configfile which follow these are the problem. If you
have
some experience with config file parsing / grammars, the debug output
should
give you some hints aswell ;-).

Best regards,
Michael

PS: If nothing helps, you can come to our IRC channel and/or send me your
config so we can debug the config together.

References:
- [i3] lexer config parser, Identifying the line in my config which is causing the error.
  - From: Scott Benjamin
- Re: [i3] lexer config parser, Identifying the line in my config which is causing the error.
  - From: Michael Stapelberg

Re: [i3] lexer config parser, Identifying the line in my config which is causing the error.

Other related posts: