Newest at the top
| 2024-04-30 11:35:40 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 260 seconds) |
| 2024-04-30 11:35:11 +0200 | zmt01 | (~zmt00@user/zmt00) (Ping timeout: 272 seconds) |
| 2024-04-30 11:34:53 +0200 | tolt | (~kevin@li219-154.members.linode.com) (Client Quit) |
| 2024-04-30 11:33:45 +0200 | swamp_ | (~zmt00@user/zmt00) |
| 2024-04-30 11:32:42 +0200 | zmt00 | (~zmt00@user/zmt00) |
| 2024-04-30 11:32:40 +0200 | <tomsmeding> | (GC is really taking up a significant percentage of the runtime here, like >60%, so it really matters) |
| 2024-04-30 11:31:37 +0200 | <tomsmeding> | I'd like to use a compact region, but that doesn't apply here because of (1.) and (2.), right? |
| 2024-04-30 11:31:25 +0200 | tolt | (~kevin@li219-154.members.linode.com) |
| 2024-04-30 11:31:11 +0200 | <tomsmeding> | the thing is, 1. I'm allocating that structure in parallel, and 2. it has lots of internal sharing |
| 2024-04-30 11:30:51 +0200 | <tomsmeding> | and because the structure is large, the GC actually takes a long time to traverse it, and repeatedly does so while it's being constructed -- lots of wasted cpu cycles |
| 2024-04-30 11:30:21 +0200 | <tomsmeding> | structure while the second function is still live |
| 2024-04-30 11:30:20 +0200 | tolt_ | (~kevin@li219-154.members.linode.com) (Quit: WeeChat 4.2.2) |
| 2024-04-30 11:30:19 +0200 | <tomsmeding> | I have a (haskell) function that allocates a whole bunch of data on the heap, and another function that consumes it all again. I know that all data in that particular data structure will be live until the second function consumes it, and the data ought to be kept live as long as the second function is live (it has a pointer to it in its closure); it's pointless for the GC to traverse the data |
| 2024-04-30 11:27:44 +0200 | tolt | (~kevin@li219-154.members.linode.com) (Ping timeout: 260 seconds) |
| 2024-04-30 11:27:08 +0200 | TheCoffeMaker | (~TheCoffeM@user/thecoffemaker) |
| 2024-04-30 11:27:00 +0200 | cashew | (~cashewsta@65.17.175.150) |
| 2024-04-30 11:25:48 +0200 | <tomsmeding> | (found by spelunking in /key list) |
| 2024-04-30 11:25:38 +0200 | <tomsmeding> | dminuoso: F10 to scroll forward, F9 to scroll back |
| 2024-04-30 11:24:46 +0200 | tolt_ | (~kevin@li219-154.members.linode.com) |
| 2024-04-30 11:24:29 +0200 | qqq | (~qqq@92.43.167.61) |
| 2024-04-30 11:23:41 +0200 | ski | bound `C-home' and `C-end' to scroll to top and bottom of scrollback buffer |
| 2024-04-30 11:23:25 +0200 | <dminuoso> | But yeah, I just use /topic |
| 2024-04-30 11:23:17 +0200 | <tomsmeding> | ski: right, /topic indeed also repeats it |
| 2024-04-30 11:23:03 +0200 | <tomsmeding> | and have it take up more than 1 line of my screen? no thanks :) |
| 2024-04-30 11:22:56 +0200 | <dminuoso> | It just does.. things and confuses me |
| 2024-04-30 11:22:56 +0200 | <ski> | yea, just saying you can, at least in Irssi, repeat the whole topic, with `/topic', and i'd imagine also in weechat |
| 2024-04-30 11:22:47 +0200 | <ncf> | /set weechat.bar.title.size_max 3 |
| 2024-04-30 11:22:46 +0200 | <dminuoso> | Oh I have mouse mode turned off, because I cant deal with it. |
| 2024-04-30 11:22:38 +0200 | <tomsmeding> | there's also a bizarrely obscure keybind for it iirc |
| 2024-04-30 11:22:25 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 245 seconds) |
| 2024-04-30 11:22:23 +0200 | <tomsmeding> | dminuoso: by using the mouse scroll wheel when the mouse is on that line in the terminal (!) |
| 2024-04-30 11:22:08 +0200 | <tomsmeding> | (and also the whole thing on join, but I don't often first-time-join a channel ;) ) |
| 2024-04-30 11:22:03 +0200 | <dminuoso> | tomsmeding: And how do you scroll to the end in weechat? |
| 2024-04-30 11:21:51 +0200 | <tomsmeding> | I see the first screenwidth of the topic above the channel buffer |
| 2024-04-30 11:21:41 +0200 | <tomsmeding> | oh |
| 2024-04-30 11:21:33 +0200 | <ski> | <tomsmeding> I've learned to read it -- it took me an embarrassingly long time to figure out how to scroll to the end in weechat |
| 2024-04-30 11:21:06 +0200 | tolt | (~kevin@li219-154.members.linode.com) |
| 2024-04-30 11:20:29 +0200 | <tomsmeding> | what made you think that? |
| 2024-04-30 11:20:21 +0200 | <tomsmeding> | it does |
| 2024-04-30 11:18:57 +0200 | califax | (~califax@user/califx) |
| 2024-04-30 11:18:55 +0200 | <ski> | tomsmeding : it doesn't display topic for you, in weechat ? |
| 2024-04-30 11:10:28 +0200 | TheCoffeMaker | (~TheCoffeM@user/thecoffemaker) (Ping timeout: 260 seconds) |
| 2024-04-30 11:07:58 +0200 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2024-04-30 11:07:01 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
| 2024-04-30 11:04:24 +0200 | <tomsmeding> | ... oops |
| 2024-04-30 11:04:19 +0200 | <tomsmeding> | :q |
| 2024-04-30 10:53:35 +0200 | <tomsmeding> | ski: hm? |
| 2024-04-30 10:48:54 +0200 | <ski> | tomsmeding : `/topic' ? |
| 2024-04-30 10:47:56 +0200 | noumenon | (~noumenon@113.51-175-156.customer.lyse.net) (Remote host closed the connection) |
| 2024-04-30 10:47:28 +0200 | noumenon | (~noumenon@113.51-175-156.customer.lyse.net) |