Newest at the top
| 2025-03-26 22:51:42 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 272 seconds) |
| 2025-03-26 22:46:38 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 22:39:18 +0100 | ru0mad | (~ru0mad@moon.ruomad.net) ru0mad |
| 2025-03-26 22:37:51 +0100 | ru0mad | (~ru0mad@2a01:e0a:98f:8270:f2d5:bfff:fe7f:1c6e) (Ping timeout: 276 seconds) |
| 2025-03-26 22:30:46 +0100 | fp1 | (~Thunderbi@87-92-229-21.rev.dnainternet.fi) fp |
| 2025-03-26 22:27:01 +0100 | ru0mad | (~ru0mad@2a01:e0a:98f:8270:f2d5:bfff:fe7f:1c6e) ru0mad |
| 2025-03-26 22:18:56 +0100 | justsomeguy | (~justsomeg@user/justsomeguy) (Quit: WeeChat 3.6) |
| 2025-03-26 22:04:27 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
| 2025-03-26 22:00:21 +0100 | robobub | (uid248673@id-248673.uxbridge.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-03-26 22:00:14 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 22:00:10 +0100 | sprotte24_ | (~sprotte24@p200300d16f097d007520d57df2b917ec.dip0.t-ipconnect.de) (Remote host closed the connection) |
| 2025-03-26 22:00:09 +0100 | sprotte24_ | (~sprotte24@p200300d16f097d007520d57df2b917ec.dip0.t-ipconnect.de) |
| 2025-03-26 21:57:00 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 244 seconds) |
| 2025-03-26 21:54:35 +0100 | <merijn> | Especially for what you said "compiler error messages" you probably wanna use prettyprinter and then use prettyprinter-ansi-terminal to render it to ansi terminal output |
| 2025-03-26 21:53:03 +0100 | <merijn> | [exa]: Then there are multiple renderers to turn those into output (html, ascii, ansi terminal, etc.) |
| 2025-03-26 21:52:43 +0100 | <merijn> | [exa]: You have prettyprinter that can compose message (including fancy formatting, indenting, line wrapping, etc.) with semantic annotations |
| 2025-03-26 21:52:08 +0100 | <merijn> | [exa]: Basically, prettyprinter decouples the decision |
| 2025-03-26 21:51:33 +0100 | infohazards | (~user@user/fmira) (Remote host closed the connection) |
| 2025-03-26 21:51:32 +0100 | infohazards | (~user@user/fmira) fmira |
| 2025-03-26 21:51:09 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) |
| 2025-03-26 21:49:42 +0100 | infohazards | (~user@user/fmira) (Remote host closed the connection) |
| 2025-03-26 21:49:40 +0100 | <[exa]> | nvm thanks both for pointing me! |
| 2025-03-26 21:49:35 +0100 | <[exa]> | hard choices today |
| 2025-03-26 21:49:30 +0100 | <[exa]> | or maybe I just wrap the ansi-terminal with a single function |
| 2025-03-26 21:49:07 +0100 | infohazards | (~user@user/fmira) fmira |
| 2025-03-26 21:44:54 +0100 | <[exa]> | ok looks like prettyprinter, thanks! |
| 2025-03-26 21:44:46 +0100 | <[exa]> | yeah I kinda wanted to have something that avoids emitting them if the termcap check fails etc |
| 2025-03-26 21:44:35 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) (Ping timeout: 268 seconds) |
| 2025-03-26 21:43:41 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-03-26 21:43:39 +0100 | <merijn> | [exa]: That lets you do formatting like indenting, etc. too |
| 2025-03-26 21:43:36 +0100 | son0p | (~ff@2800:e6:4000:d723:c181:4205:f2b1:437a) son0p |
| 2025-03-26 21:43:35 +0100 | <tomsmeding> | (also, basic ansi color escapes are easy to do manually) |
| 2025-03-26 21:43:21 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer) |
| 2025-03-26 21:43:21 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
| 2025-03-26 21:43:16 +0100 | <merijn> | [exa]: prettyprinter |
| 2025-03-26 21:43:06 +0100 | <tomsmeding> | ansi-terminal? |
| 2025-03-26 21:42:56 +0100 | <[exa]> | (purpose: making compiler error messages more easily readable by highlighting the bad part and location) |
| 2025-03-26 21:42:28 +0100 | ash3en | (~Thunderbi@ip1f10cbd6.dynamic.kabel-deutschland.de) (Client Quit) |
| 2025-03-26 21:41:59 +0100 | <[exa]> | hi all! is there some good terminal library for printing out colored stuff without too much hassle? preferably capable of turning the colors off when not needed? |
| 2025-03-26 21:40:34 +0100 | infohazards | (~user@user/fmira) (Remote host closed the connection) |
| 2025-03-26 21:40:26 +0100 | infohazards | (~user@user/fmira) fmira |
| 2025-03-26 21:40:04 +0100 | ash3en | (~Thunderbi@ip1f10cbd6.dynamic.kabel-deutschland.de) ash3en |
| 2025-03-26 21:39:51 +0100 | ash3en | (~Thunderbi@31.16.203.214) (Read error: Connection reset by peer) |
| 2025-03-26 21:39:10 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) |
| 2025-03-26 21:33:35 +0100 | infohazards | (~user@user/fmira) (Remote host closed the connection) |
| 2025-03-26 21:31:24 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) (Ping timeout: 246 seconds) |
| 2025-03-26 21:28:03 +0100 | jespada | (~jespada@2800:a4:2263:8100:f927:2b9e:1735:aa6a) (Quit: My Mac has gone to sleep. ZZZzzz…) |
| 2025-03-26 21:26:46 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 252 seconds) |
| 2025-03-26 21:25:29 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Quit: peterbecich) |
| 2025-03-26 21:23:59 +0100 | jco | (~jco@78-70-217-44-no600.tbcn.telia.com) (Quit: leaving) |