Newest at the top
| 2024-09-23 01:15:30 +0200 | Squared | (~Square@user/square) |
| 2024-09-23 01:15:13 +0200 | Squared | (~Square@user/square) (Quit: Leaving) |
| 2024-09-23 01:11:24 +0200 | pavonia | (~user@user/siracusa) |
| 2024-09-23 01:09:54 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds) |
| 2024-09-23 01:08:38 +0200 | JuanDaugherty | (~juan@user/JuanDaugherty) (Quit: JuanDaugherty) |
| 2024-09-23 01:05:08 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-23 01:03:36 +0200 | <geekosaur> | hope that doesn't repeat on reboot |
| 2024-09-23 01:03:28 +0200 | <geekosaur> | first time I logged in a number of programs were behaving oddly, but exiting and restarting them fixed that. ??? |
| 2024-09-23 01:02:12 +0200 | athan | (~athan@syn-098-153-145-140.biz.spectrum.com) |
| 2024-09-23 01:00:25 +0200 | <haskellbridge> | <sm> đź‘€ |
| 2024-09-23 00:57:04 +0200 | __monty__ | (~toonn@user/toonn) (Quit: leaving) |
| 2024-09-23 00:54:46 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds) |
| 2024-09-23 00:52:57 +0200 | target_i | (~target_i@user/target-i/x-6023099) (Quit: leaving) |
| 2024-09-23 00:50:35 +0200 | geekosaur | just upgraded to 24.04. it's a mixed bag, but generally positive because a lot of annoying bugs going back at least to 20.04 have finally been fixed |
| 2024-09-23 00:49:55 +0200 | <geekosaur> | I just saw it again last night (they broke clang++, dammit) |
| 2024-09-23 00:49:31 +0200 | <haskellbridge> | <sm> I love launchpad, haven't seen it for ages |
| 2024-09-23 00:49:20 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-23 00:48:14 +0200 | sdrfan123 | (~sdrfan123@2607:fb90:df8d:eacb:467:e53f:ae7e:31ca) |
| 2024-09-23 00:38:34 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2024-09-23 00:33:33 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-23 00:31:38 +0200 | machinedgod | (~machinedg@d50-99-47-73.abhsia.telus.net) (Ping timeout: 245 seconds) |
| 2024-09-23 00:31:13 +0200 | gwern | (~gwern@user/gwern) () |
| 2024-09-23 00:30:21 +0200 | <gwern> | https://bugs.launchpad.net/ubuntu/+source/ghc/+bug/2081666 |
| 2024-09-23 00:22:48 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-09-23 00:21:33 +0200 | gwern | figures that once it is actually enabled rather than buried in the deepest mustiest part of the ghc repo, then people will start filing bugs on its infelicities |
| 2024-09-23 00:21:02 +0200 | <sm> | that sounds good, and/or a ghc bug asking for the script to be updated for latest ghc |
| 2024-09-23 00:18:13 +0200 | <gwern> | anyway so I guess I should file a ubuntu bug for the ghc package asking for the existing ghc.bash to be installed appropriately? |
| 2024-09-23 00:17:46 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-23 00:15:33 +0200 | joeyadams | (~joeyadams@syn-184-054-105-097.res.spectrum.com) (Quit: Leaving) |
| 2024-09-22 23:53:37 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2024-09-22 23:50:41 +0200 | uli-fem | (~uli-fem@user/uli-fem) (Ping timeout: 248 seconds) |
| 2024-09-22 23:48:20 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-22 23:38:24 +0200 | athan | (~athan@syn-098-153-145-140.biz.spectrum.com) (Quit: Konversation terminated!) |
| 2024-09-22 23:37:29 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds) |
| 2024-09-22 23:32:33 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-22 23:24:46 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2024-09-22 23:21:44 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 255 seconds) |
| 2024-09-22 23:16:47 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-22 23:08:00 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-09-22 23:03:07 +0200 | merijn | (~merijn@204-220-045-062.dynamic.caiway.nl) |
| 2024-09-22 23:01:24 +0200 | <haskellbridge> | <sm> it also gets more complicated if you want your tool to run external exes as subcommands, as recent cabal does |
| 2024-09-22 23:00:18 +0200 | <haskellbridge> | <sm> I think that kind of position sensitivity in clis is uncommon because it requires custom logic (or more flexibility than exists in the vast majority of parsing libs) |
| 2024-09-22 22:57:08 +0200 | <tomsmeding> | `cabal run foo xyz` does run `foo xyz` |
| 2024-09-22 22:57:01 +0200 | <tomsmeding> | it's not what cabal does, for better or for worse |
| 2024-09-22 22:56:29 +0200 | <gwern> | (ie. 'cabal run --option foo' obviously means that '--option' is for 'cabal run' and not for 'foo', and so 'cabal run --option1 foo --option2' is not ambiguous and doesn't need any guarding) |
| 2024-09-22 22:55:57 +0200 | <haskellbridge> | <sm> gwern: that's a possible convention, but would be surprising to some people. Robust command line processing is quite hard |
| 2024-09-22 22:55:42 +0200 | <gwern> | a wrapper like that doesn't usually *need* the ' -- ' guard |
| 2024-09-22 22:55:40 +0200 | <tomsmeding> | it also takes them after the executable name -- not sure why |
| 2024-09-22 22:55:17 +0200 | <gwern> | just sounds odd. I would expect cabal run to only take its options if they came before 'foo', or before 'run' even |
| 2024-09-22 22:54:52 +0200 | <tomsmeding> | I mean, even if that did work, that wouldn't make fish's completion any more functional :p |