mirror of
https://github.com/xmonad/xmonad-contrib.git
synced 2025-05-19 03:20:21 -07:00
When users specify non-existent keys, it seems most intuitive to just abort the parse and not try to take the "longest" input that still works. For example, given the "key" `M-10` we should signal a parse error (by returning `Nothing`) instead of parsing `M-1` and ignoring the rest of the input. The old EZConfig parser accounted for this but when the module was rewritten to use X.U.Parser in [1], this was forgotten about. Fixes: https://github.com/xmonad/xmonad/issues/361 [1]: 8abeb81fd0693bd4ee914b522c0a2a2cfcfaf0dd