Newest at the top
| 2025-10-23 11:06:00 +0200 | Googulator6 | (~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) |
| 2025-10-23 11:05:42 +0200 | Googulator6 | (~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-10-23 10:59:11 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-10-23 10:51:12 +0200 | humasect | numberella |
| 2025-10-23 10:49:27 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 244 seconds) |
| 2025-10-23 10:44:00 +0200 | craunts795335385 | (~craunts@136.158.7.194) (Quit: The Lounge - https://thelounge.chat) |
| 2025-10-23 10:38:48 +0200 | <tomsmeding> | the current phrase reads rather awkward in english, I think :p |
| 2025-10-23 10:38:43 +0200 | <haskellbridge> | <maerwald> artistic freedom? |
| 2025-10-23 10:38:32 +0200 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) |
| 2025-10-23 10:38:18 +0200 | <tomsmeding> | maerwald: about that: why is it called "advance options" instead of "advanced options"? |
| 2025-10-23 10:37:51 +0200 | <haskellbridge> | <maerwald> if you press Enter, we could show the less common options (like unset) |
| 2025-10-23 10:37:35 +0200 | <tomsmeding> | possibly this is just an assembly template that ghc fills in and it ends up generating redundant instructions here |
| 2025-10-23 10:37:23 +0200 | <haskellbridge> | <maerwald> yeah, mapping all of the cli to the tui is hard... although with the new advanced install menu, that's partially done |
| 2025-10-23 10:37:06 +0200 | <tomsmeding> | moving a bunch of zeros around without accomplishing anything? |
| 2025-10-23 10:36:48 +0200 | <tomsmeding> | zero the xmm0 register, then proceed to copy the high half of it to the low half |
| 2025-10-23 10:36:34 +0200 | <tomsmeding> | how is it useful on x86_64 to do `pxor %xmm0,%xmm0 ; movhlps %xmm0,%xmm0`? |
| 2025-10-23 10:36:14 +0200 | <tomsmeding> | the assembly generated by ghc on doc's example looks weird anyway |
| 2025-10-23 10:32:47 +0200 | merijn | (~merijn@77.242.116.146) (Ping timeout: 256 seconds) |
| 2025-10-23 10:30:04 +0200 | comerijn | (~merijn@77.242.116.146) merijn |
| 2025-10-23 10:25:47 +0200 | Googulator30 | (~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-10-23 10:25:36 +0200 | Googulator6 | (~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) |
| 2025-10-23 10:25:08 +0200 | <tomsmeding> | [exa]: be careful, don't hit your head |
| 2025-10-23 10:24:41 +0200 | <tomsmeding> | I think wanting to unset is relatively uncommon |
| 2025-10-23 10:24:39 +0200 | [exa] | slams a nice flat stone over himself and enjoys the hideout |
| 2025-10-23 10:24:17 +0200 | <tomsmeding> | I don't see how that's strong vs weak |
| 2025-10-23 10:24:14 +0200 | <[exa]> | can it be afternoon finally? |
| 2025-10-23 10:24:10 +0200 | <[exa]> | am I overdoing it? |
| 2025-10-23 10:24:07 +0200 | <[exa]> | I meant like, "as opposed to weak unset by setting something else" |
| 2025-10-23 10:23:44 +0200 | <tomsmeding> | I'd remove "force" from that sentence |
| 2025-10-23 10:23:30 +0200 | <[exa]> | the main problem was that the lack of "unset" in UI is kinda surprising, maybe the easiest solution is to hint after `set` completes that "you can force unset via commandline" or so |
| 2025-10-23 10:23:06 +0200 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 244 seconds) |
| 2025-10-23 10:22:56 +0200 | <haskellbridge> | <maerwald> https://youtu.be/bB4fmQiUYPw |
| 2025-10-23 10:22:27 +0200 | <[exa]> | maerwald: anyway I guess all this is just me whining ^, don't take it very seriously |
| 2025-10-23 10:22:14 +0200 | <haskellbridge> | <maerwald> I actually recorded a video for windows installation, lol |
| 2025-10-23 10:22:11 +0200 | <tomsmeding> | [exa]: lol |
| 2025-10-23 10:22:05 +0200 | <tomsmeding> | I mean, this is your call and I don't care enough to really complain about it if you do make hotkeys case-insensitive, but if I maintained ghcup I would limit this change to q at least |
| 2025-10-23 10:21:49 +0200 | <[exa]> | "in this video I'll show 5 easy ways to quit ghcup tui if you're stuck installing haskell" |
| 2025-10-23 10:21:12 +0200 | <haskellbridge> | <maerwald> lmao |
| 2025-10-23 10:21:02 +0200 | <tomsmeding> | (prevent people going "I can't exit vim" on ghcup) |
| 2025-10-23 10:20:46 +0200 | <tomsmeding> | perhaps indeed for q it's nice to allow Q too, if only to make it as easy as possible to quit the app |
| 2025-10-23 10:20:34 +0200 | [exa] | dodges |
| 2025-10-23 10:20:32 +0200 | <[exa]> | ctrl-s? |
| 2025-10-23 10:20:19 +0200 | <tomsmeding> | if accidental capslock is the first time they tried a capital letter hotkey, then I fail to see why one would capitalisation to not matter across the board immediately |
| 2025-10-23 10:19:54 +0200 | <haskellbridge> | <maerwald> for quit, it's indeed annoying |
| 2025-10-23 10:19:39 +0200 | <tomsmeding> | yes I read that |
| 2025-10-23 10:19:34 +0200 | <haskellbridge> | <maerwald> capslock on |
| 2025-10-23 10:19:14 +0200 | <tomsmeding> | why would they want that? |
| 2025-10-23 10:18:41 +0200 | <haskellbridge> | <maerwald> https://github.com/haskell/ghcup-hs/issues/1294 |
| 2025-10-23 10:18:35 +0200 | <haskellbridge> | <maerwald> well |
| 2025-10-23 10:17:55 +0200 | <[exa]> | maerwald: maybe pressing s again? or better leave that as "retry setting" and go shift-s ? |