add XF86WLAN special key

[geekosaur]

Description

Add XF86WLAN to EZConfig.
Closes #27.

Checklist

• I've read CONTRIBUTING.md

• I've considered how to best test these changes (property, unit,
  manually, ...) and concluded: manually

• I updated the CHANGES.md file (next push)

[geekosaur]

@slotThe, OrgMode test failure only on 8.6.5, looks like a QuickCheck version problem possibly?

[slotThe]

@slotThe, OrgMode test failure only on 8.6.5, looks like a QuickCheck version problem possibly?

Yes, it seems to pick 2.7.x, while arbitraryPrintableChar is only available from 2.10.x onwards. I'm curious, though, why this has never happened before?

[geekosaur]

Betting some dependency changed its bounds, possibly by removing its own 8.6 support.

[slotThe]

Debian stable already seems to be on 9.0… Should we just drop support for 8.6? (not because arbitraryPrintableChar is so difficult to define ourselves, but just as a matter of principle)

@liskin any opinions?

[liskin]

Debian stable already seems to be on 9.0… Should we just drop support for 8.6? (not because arbitraryPrintableChar is so difficult to define ourselves, but just as a matter of principle)

@liskin any opinions?

Yeah that's reasonable. Ubuntu 22.04, which seems to still be used quite a lot, has ghc 8.8.4, so we may want to keep that one.

Or not, I dunno. We're currently supporting (and testing against in CI!) 9 different major GHC versions, which seems quite excessive. It'd be 10 once the PRs adding 9.12 are merged (only looked at those briefly, some work needs to be done, and I'm kind of in the middle of doing that work for X11 and X11-xft). Just removing 8.6 gets us down to 9. Probably all right, we're far from running out of GitHub Actions budget :-)

[slotThe]

I think I did this right. Should be good to go now

[geekosaur]

LGTM

[liskin]

This was here to make sure we test compatibility with the latest hackage release of xmonad and X11 on both oldest and newest supported GHC. So only one of these should be dropped, and the stack.yaml one should be moved to a newer resolver.

[slotThe]

Ah, so that was what that was :)

[geekosaur]

I'm on it.

[liskin]

I should've added a comment really. It's a small miracle I still remember what the point was. Perhaps I don't and what I said isn't even true 😂

[geekosaur]

Looks correct to me from inspecting both the stack.yaml files. (I'm reminded of the stuff I added to cabal's CI to do much the same thing, but it's a little more involved since of course they don't build with stack.)