Under "Code listing 3.6" there are two examples of running aterm that results in aterm exiting with "bad option": Mod1 a :ExecCommand aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg\ white -fade 90 -bl -tn xterm -fn\ -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15 -g 116x57 Mod1 s :ExecCommand aterm -name aterm -sl 3000 -tr +sb -sr -sk -bg black -fg\ white -fade 90 -bl -tn xterm -fn\ -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15 -g 116x57 -e su - on the two lines where you have "-fg\" and "-fn\" there are no spaces afterwards or before the next word/string so it ends up coming out like: "-fgwhite" and "-fn-misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15" If the lines are pasted as is in to ~/.fluxbox/keys fluxbox will only parse the first line and ignore all the options after that it seems. Reproducible: Always Steps to Reproduce: 1. Open link, scroll down to "Code Listing 3.6" 2. Copy the code listed and paste it in to ~/.fluxbox/keys 3. Reload the fluxbox config (right-click on the desktop, might be an option for it, if not add "[reconfig] (Reload Config)" to ~/.fluxbox/keys. 4. Use alt-s or alt-a to test the new keys 5. Note that not all the options are passed to aterm. Actual Results: Only the first line of the key setting is read, the rest of the options are ignored. Expected Results: Should have read all the options if everything was listed on one line instead of 3 lines using \ at the end of each line. This could very well be the most retarted bug to submit, but it might save some email and IRC support if the lines were corrected... Good guide all around though, thanks for writing it.
You're entirely correct. Thanks for reporting!
