i3 startup sequence and role of config file
I have been struggling to get a window to start in the scratchpad (I have an earlier question on this, but can't link to it). I finally - partially - fixed that by switching to lilyterm from urxvt. But I have continued to have odd delays and failures in startup when I've tried to start other programs (for instance, Claws Mail and Iceweasel; sometimes they start from exec commands in config, sometimes they don't). This leads me to wonder if i3 is not yet 'ready' at the time of the config file to load certain windows. In that context I had two questions:
What is the i3 startup sequence and where does the config file fit in this?
Is there is anything one can put in the config file to make sure that certain commands are only executed after i3 is "ready"? Would shifting those commands to a separate script and executing them with i3-msg help?
What are you using in your config file to do this? Did you check [the debugging output](http://i3wm.org/docs/debugging.html)
Sorry, I just saw this. I haven't checked out the debugging output. I found that shifting all the exec commands (and the scratchpad stuff) to a separate script, and putting in only one exec_always call to that script at the end of the config, worked. I still don't know why, however.