slotThe 0a6048c66d X.U.EZConfig: Force readKeySequence to consume the whole input
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
2022-01-05 15:06:17 +01:00
..
2021-06-06 18:59:05 +02:00
2021-12-13 16:11:57 +01:00
2020-12-11 18:03:22 +01:00
2022-01-03 08:59:41 +01:00
2020-12-11 18:03:22 +01:00
2021-06-06 18:59:05 +02:00
2021-06-06 18:59:05 +02:00
2021-05-21 17:37:09 +02:00