Newest at the top
| 2024-05-03 20:40:06 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:37:59 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:34:30 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:31:30 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:30:18 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:27:52 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:25:10 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:23:10 +0200 | euleritian | (~euleritia@87.79.39.180) |
| 2024-05-03 20:23:03 +0200 | euleritian | (~euleritia@87.79.39.180) (Read error: Connection reset by peer) |
| 2024-05-03 20:23:03 +0200 | chexum | (~quassel@gateway/tor-sasl/chexum) |
| 2024-05-03 20:22:03 +0200 | chexum | (~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection) |
| 2024-05-03 20:21:41 +0200 | euleritian | (~euleritia@87.79.39.180) |
| 2024-05-03 20:21:34 +0200 | euleritian | (~euleritia@87.79.39.180) (Read error: Connection reset by peer) |
| 2024-05-03 20:21:34 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:21:21 +0200 | tomsmeding | just :%!jq .<cr> in vim but that's 1% effort 80% reward |
| 2024-05-03 20:20:42 +0200 | <tomsmeding> | monochrom: why not? |
| 2024-05-03 20:20:30 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:20:05 +0200 | euleritian | (~euleritia@87.79.39.180) |
| 2024-05-03 20:19:48 +0200 | euleritian | (~euleritia@87.79.39.180) (Read error: Connection reset by peer) |
| 2024-05-03 20:17:34 +0200 | euleritian | (~euleritia@87.79.39.180) |
| 2024-05-03 20:16:32 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:15:22 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:13:49 +0200 | <EvanR> | the more inconsequential the change to the syntax the more egotism. New programming language < new syntax < new syntax for comments < new whitespace formatting |
| 2024-05-03 20:13:05 +0200 | <monochrom> | (I need a json formatter for all sorts of json-using things, not just cabal's plan file.) |
| 2024-05-03 20:11:50 +0200 | <monochrom> | Actually that's just egotism. I should just use an existing one. |
| 2024-05-03 20:11:44 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:11:23 +0200 | <monochrom> | I need to write my own json formatter. :) |
| 2024-05-03 20:09:46 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:09:01 +0200 | nurupo | (~nurupo.ga@user/nurupo) |
| 2024-05-03 20:08:44 +0200 | nurupo | (~nurupo.ga@user/nurupo) (Quit: nurupo.ga) |
| 2024-05-03 20:07:25 +0200 | raehik | (~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) (Ping timeout: 268 seconds) |
| 2024-05-03 20:06:36 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:06:16 +0200 | michalz | (~michalz@185.246.207.197) |
| 2024-05-03 20:06:09 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) |
| 2024-05-03 20:05:33 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) (Read error: Connection reset by peer) |
| 2024-05-03 20:05:06 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 20:02:47 +0200 | <raehik> | super! cabal-plan tred has extremely concise understandable output |
| 2024-05-03 20:01:23 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) |
| 2024-05-03 20:00:40 +0200 | <glguy> | "cabal-plan tred" can be pretty handy |
| 2024-05-03 20:00:15 +0200 | target_i | (~target_i@user/target-i/x-6023099) |
| 2024-05-03 19:59:58 +0200 | stiell | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
| 2024-05-03 19:59:53 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
| 2024-05-03 19:59:27 +0200 | <tomsmeding> | (warning: that graph is large) |
| 2024-05-03 19:59:12 +0200 | <tomsmeding> | ('cabal-plan dot' gives you a graphviz dot graph of your dep graph) |
| 2024-05-03 19:58:48 +0200 | <tomsmeding> | the cabal-plan tool has utilities for reading that file, but it's also hand-readable if you run it through a json formatter |
| 2024-05-03 19:58:39 +0200 | <raehik> | ooh I've never looked in there. cheers tomsmeding |
| 2024-05-03 19:58:19 +0200 | <tomsmeding> | raehik: you can also check the contents of dist-newstyle/cache/plan.json |
| 2024-05-03 19:58:05 +0200 | <raehik> | Oh wait, self-answer. cabal freeze appears to do it! |
| 2024-05-03 19:57:21 +0200 | <raehik> | How can I check the transitive dependencies of a Hackage (or local Cabal) package? I'm building an aeson that I don't expect and don't know if it's my Nix setup or an actual dep. |
| 2024-05-03 19:56:28 +0200 | justsomeguy | (~justsomeg@user/justsomeguy) (Read error: Connection reset by peer) |