olafklinke

+1 for this request. It makes little sense to export `runParserT'` without a no-boilerplate way for the user to construct a `State` input.

Also experiencing this, r4.1 on AMD Ryzen with Radeon graphics. journalctl in dom0 says xss-lock dumped core. System seems to go into screen saver mode at random points in time....

As suggested in [#2982](https://github.com/QubesOS/updates-status/issues/2982) I tried downgrading the firmware: ``` user@dom0$ sudo qubes-dom0-update linux-firmware-20211216 ``` Will keep you updated how that goes. Here are the info about my system prior...

No glitches/crashes since the downgrade for me either.

As this seems to be caused by the linux-firmware package, I'd rather wait for a permanent fix from upstream. (linux-firmware is a Fedora package, right?) It would be cool if...

Just another data point: I have three machines with nearly identical AMD Ryzen hardware: 1. Qubes 4.1 with XFCE 2. Qubes 4.0 with XFCE 3. Debian11 kernel 5.10.0-13-amd64 with XFCE...

Wouldn't it help if `decimal` first parses into a non-lossy type such as `Integer` and then used `fromInteger`? For the same reason the `float` parser uses `Scientific` under the hood.

Sorry to revive this already quite old issue, but what is the preferred way of _parsing_ spreadsheets? Obviously, the traditional stream-based parsers are a bit limited, since `xlsx` already provides...

FWIW, I happened to implement something along these lines, because the [xls](https://hackage.haskell.org/package/xls) package has this and I wanted a unified Megaparsec parser for both xlsx and xls. Here is the...

> @olafklinke could we worth creating a PR if you have time for it IMHO this would actually better be part of a separate package, see [here](https://github.com/qrilka/xlsx/issues/15#issuecomment-2117537356).