Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 New issue report by semdornus: What steps will reproduce the problem? 1. Change the normalBorderColor or focusedBorderColor in your configuration - i.e. normalBorderColor = "000" (note missing "#"). 2. Restart xmonad with the standard modm-q binding. What is the expected output? What do you see instead? Expected: xmonad keeps running with the old configuration and displays an error message about the problem. Actual: xmonad crashes with "user error (error in allocNamedColor)" What version of the product are you using? On what operating system? darcs | gentoo Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings