Newest at the top
| 2025-11-26 14:29:20 +0100 | falafel | (~falafel@gateway/vpn/pia/falafel) (Ping timeout: 244 seconds) |
| 2025-11-26 14:27:01 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 264 seconds) |
| 2025-11-26 14:25:03 +0100 | <[exa]> | gah, okay. if I hit this one more time I send a PR. |
| 2025-11-26 14:24:41 +0100 | <[exa]> | oic it's actually hardcoded there |
| 2025-11-26 14:23:29 +0100 | <dminuoso> | You would have to to extend the ParseError data type with a new constructor `InfoDoc Doc` |
| 2025-11-26 14:23:02 +0100 | <[exa]> | :< |
| 2025-11-26 14:23:01 +0100 | <dminuoso> | [exa]: Anyway, all that infoOption does is just stuff an `InfoMsg` into the right place. You can see in the source code of src/Options/Applicative/Extra.hs - which is the only place this is ever discriminated upon - that there is no alternative. |
| 2025-11-26 14:22:56 +0100 | <[exa]> | like I see it's not a great deal probably, I assumed it would get defaulted on runtime but it doesn't seem so |
| 2025-11-26 14:22:33 +0100 | <[exa]> | in particular there's prefColumns in ParserPrefs, would love to inherit that somehow |
| 2025-11-26 14:20:14 +0100 | <[exa]> | so I hoped there would be something handy for rendering the stuff right |
| 2025-11-26 14:20:01 +0100 | <dminuoso> | A-ha. And you want access to the renderer used in `execParser` eventually? |
| 2025-11-26 14:19:59 +0100 | <[exa]> | for consistency etc |
| 2025-11-26 14:19:54 +0100 | <[exa]> | I'd like to render with the same as optparse-applicative renders with |
| 2025-11-26 14:19:37 +0100 | <[exa]> | the prettyString needs arguments (ribbon width, terminal width) that I have to supply as constants now |
| 2025-11-26 14:19:18 +0100 | <[exa]> | ok so essentially I now have: infoOption (prettyString ..complex thing..) $ long "blabla" ... |
| 2025-11-26 14:18:25 +0100 | <dminuoso> | [exa]: Again, you are being awfully silent on what primimtive is triggering the renderer you are talking about. |
| 2025-11-26 14:18:13 +0100 | <[exa]> | and I can render my doc manually (there's prettyString) but it ain't gonna get these opts |
| 2025-11-26 14:17:55 +0100 | <dminuoso> | It takes a string. |
| 2025-11-26 14:17:55 +0100 | <[exa]> | the Doc renderers usually have some options (render width) so I'd love to inherit the global ones |
| 2025-11-26 14:17:52 +0100 | <dminuoso> | infoOption :: String -> Mod OptionFields (a -> a) -> Parser (a -> a) |
| 2025-11-26 14:17:31 +0100 | <dminuoso> | Okay.. so whats stopping you? |
| 2025-11-26 14:17:08 +0100 | <[exa]> | yeah I want to format that string from a Doc because I have something with nesting etc there |
| 2025-11-26 14:16:36 +0100 | <dminuoso> | infoOption itself doesnt do anything, its just a parser failure containing a `String` internally. |
| 2025-11-26 14:16:13 +0100 | <dminuoso> | It seems like you're being really asking about some other primitive of optparse-applicative that you feed an infoOption to. |
| 2025-11-26 14:15:52 +0100 | <dminuoso> | Yeah but what does "infoOption" have to do with a pretty printer? |
| 2025-11-26 14:15:18 +0100 | <[exa]> | so I thought I could give it info with some structure that would get rendered properly or so |
| 2025-11-26 14:14:41 +0100 | <[exa]> | dminuoso: optparse has internal prettyprinter https://hackage-content.haskell.org/package/optparse-applicative-0.19.0.0/docs/Options-Applicative… |
| 2025-11-26 14:14:00 +0100 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2025-11-26 14:13:18 +0100 | <dminuoso> | [exa]: What do you mean by "formats a Doc", ? |
| 2025-11-26 14:09:24 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-26 14:04:57 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |
| 2025-11-26 13:59:13 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-26 13:56:49 +0100 | anselmschueler | (~Thunderbi@user/schuelermine) schuelermine |
| 2025-11-26 13:53:55 +0100 | arandombit | (~arandombi@user/arandombit) (Ping timeout: 246 seconds) |
| 2025-11-26 13:53:24 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-11-26 13:53:13 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 246 seconds) |
| 2025-11-26 13:50:18 +0100 | poscat | (~poscat@user/poscat) poscat |
| 2025-11-26 13:49:45 +0100 | poscat | (~poscat@user/poscat) (Remote host closed the connection) |
| 2025-11-26 13:47:51 +0100 | rls129 | (~rls129@150.107.206.33) () |
| 2025-11-26 13:47:37 +0100 | rls129 | (~rls129@150.107.206.33) |
| 2025-11-26 13:46:05 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-26 13:42:50 +0100 | michalz | (~michalz@185.246.207.197) (Ping timeout: 244 seconds) |
| 2025-11-26 13:41:37 +0100 | michalz_ | (~michalz@185.246.207.221) |
| 2025-11-26 13:39:44 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-11-26 13:32:23 +0100 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2025-11-26 13:29:25 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 264 seconds) |
| 2025-11-26 13:27:01 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 264 seconds) |
| 2025-11-26 13:23:52 +0100 | comerijn | (~merijn@77.242.116.146) merijn |
| 2025-11-26 13:21:42 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-26 13:11:07 +0100 | GdeVolpiano | (~GdeVolpia@user/GdeVolpiano) GdeVolpiano |