| 2022-06-29 00:17:26 +0200 | Natch | (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) |
| 2022-06-29 00:27:19 +0200 | sagax | (~sagax_nb@user/sagax) |
| 2022-06-29 00:45:05 +0200 | aliosablack | (~chomwitt@2a02:587:dc1c:800:5c71:ba1b:727c:3afe) (Ping timeout: 255 seconds) |
| 2022-06-29 01:12:31 +0200 | suconakh | (~suconakh@94.25.174.29) |
| 2022-06-29 01:17:31 +0200 | <suconakh> | Hi, is it possible to implement something like X.U.ActionCycle but for ManageHooks? I examined the source code of ActionCycle module and tried to just copy-paste everything and change `X` in type signature to `ManageHook`, but that didn't work: https://pastebin.com/e8RXM1EG |
| 2022-06-29 01:19:28 +0200 | <geekosaur> | you would have to use liftX for XS.gets to work |
| 2022-06-29 01:20:52 +0200 | <geekosaur> | there will probably be an XS.puts as well which also has to go via liftX |
| 2022-06-29 01:25:20 +0200 | <suconakh> | Thanks, that worked! |
| 2022-06-29 02:14:38 +0200 | werneta | (~werneta@137.78.30.207) (Ping timeout: 240 seconds) |
| 2022-06-29 02:40:08 +0200 | suconakh | (~suconakh@94.25.174.29) (Ping timeout: 252 seconds) |
| 2022-06-29 03:04:05 +0200 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2022-06-29 03:17:21 +0200 | suconakh | (~suconakh@94.25.175.204) |
| 2022-06-29 03:32:32 +0200 | suconakh | (~suconakh@94.25.175.204) (Quit: Client closed) |
| 2022-06-29 04:00:32 +0200 | gdd1 | (~gdd@2001:470:1f13:187:e8a5:fbff:fe29:42f5) (Ping timeout: 272 seconds) |
| 2022-06-29 04:02:38 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 255 seconds) |
| 2022-06-29 04:22:44 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-06-29 04:23:57 +0200 | gdd1 | (~gdd@2001:470:1f13:187:e8a5:fbff:fe29:42f5) |
| 2022-06-29 04:42:14 +0200 | td_ | (~td@94.134.91.56) (Ping timeout: 255 seconds) |
| 2022-06-29 04:44:00 +0200 | td_ | (~td@muedsl-82-207-238-037.citykom.de) |
| 2022-06-29 05:51:30 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 260 seconds) |
| 2022-06-29 07:22:19 +0200 | jeeeun0 | (~jeeeun@78.40.148.178) |
| 2022-06-29 07:22:32 +0200 | jeeeun | (~jeeeun@78.40.148.178) (Read error: Connection reset by peer) |
| 2022-06-29 07:22:32 +0200 | jeeeun0 | jeeeun |
| 2022-06-29 07:23:03 +0200 | lambdabot | (~lambdabot@haskell/bot/lambdabot) (Ping timeout: 256 seconds) |
| 2022-06-29 07:25:41 +0200 | lambdabot | (~lambdabot@haskell/bot/lambdabot) |
| 2022-06-29 07:32:47 +0200 | qbt | (~qbt@user/edun) |
| 2022-06-29 07:33:00 +0200 | qbt | (~qbt@user/edun) (Client Quit) |
| 2022-06-29 07:33:19 +0200 | qbt | (~qbt@user/edun) |
| 2022-06-29 08:18:10 +0200 | aliosablack | (~chomwitt@2a02:587:dc1c:800:6edf:8c3:2be1:2ef9) |
| 2022-06-29 08:19:58 +0200 | <Solid> | liskin: since I've decided to handle all the xmonad stuff via some freelancing gig an invoice is just simpler for me in terms of what to put on my tax declaration |
| 2022-06-29 08:21:18 +0200 | <Solid> | geekosaur liskin mc47[m]: what's your opinion on https://github.com/xmonad/xmonad-contrib/pull/727 in terms of "should we deprecate these records in favour of def"? |
| 2022-06-29 08:30:03 +0200 | alternateved | (~alternate@185.216.35.254) |
| 2022-06-29 08:30:30 +0200 | <mc47[m]> | I took a look at the code, and I agree with their argumentation in favor of deprecating urgencyConfig and keeping dzenUrgencyHook |
| 2022-06-29 08:31:41 +0200 | <mc47[m]> | If we'd deprecate dzenUrgencyHook, we should consider deprecating the other hooks like borderUrgencHook and replacing them with a Default instance |
| 2022-06-29 08:44:49 +0200 | qbt | (~qbt@user/edun) (Ping timeout: 268 seconds) |
| 2022-06-29 08:45:38 +0200 | qbt | (~qbt@user/edun) |
| 2022-06-29 08:51:58 +0200 | cfricke | (~cfricke@user/cfricke) |
| 2022-06-29 08:56:19 +0200 | thunderrd | (~thunderrd@183.182.115.144) |
| 2022-06-29 09:08:15 +0200 | thunderrd | (~thunderrd@183.182.115.144) (Ping timeout: 268 seconds) |
| 2022-06-29 09:12:37 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2022-06-29 09:46:50 +0200 | <Solid> | liskin: what do you think about the suggestion in https://github.com/NixOS/nixpkgs/commit/36d5761b3e5aca9742fec85107e3d308a9af872c#commitcomment-770… about adding XMONAD_XMESSAGE and XMONAD_GHC? |
| 2022-06-29 10:19:04 +0200 | qbt | (~qbt@user/edun) (Quit: WeeChat 3.5) |
| 2022-06-29 10:19:22 +0200 | alternateved | (~alternate@185.216.35.254) (Remote host closed the connection) |
| 2022-06-29 10:20:06 +0200 | alternateved | (~alternate@185.216.35.254) |
| 2022-06-29 10:20:44 +0200 | qbt | (~qbt@user/edun) |
| 2022-06-29 10:33:11 +0200 | aliosablack | (~chomwitt@2a02:587:dc1c:800:6edf:8c3:2be1:2ef9) (Remote host closed the connection) |
| 2022-06-29 11:01:32 +0200 | <liskin> | Solid: I'd still think you could simply ignore these expenses altogether and only use freelancing for actual "income" but maybe Germany is different |
| 2022-06-29 11:01:44 +0200 | <liskin> | Anyway, do whatever suit you best :-) |
| 2022-06-29 11:02:34 +0200 | <liskin> | Re (dzen)UrgencyHook I agree with deprecating only urgencyConfig |
| 2022-06-29 11:04:28 +0200 | <liskin> | And yeah those env vars are probably acceptable. I wanted to reply to that but just couldn't find the capacity. |
| 2022-06-29 11:05:48 +0200 | <liskin> | They have a point that using the patch for git snapshots is on us. It's explicitly mentioned in the flake, so we can probably make the Nix builds green without touching nixpkgs. I just don't know how :-) |
| 2022-06-29 11:21:00 +0200 | <alternateved> | By pointing to different patch file in flake? |
| 2022-06-29 11:23:38 +0200 | <[Leary]> | liskin: If we're out of sync with the patch, then instead of asking downstream to update, it's better we make our own and let them get it from us. That said, I think adopting those env vars is better, since it's not necessarily just a nix hack---anyone who doesn't want ghc in their path (or who wants to use a different one for xmonad) can point them at their isolated binary. |
| 2022-06-29 11:24:07 +0200 | <[Leary]> | Though I'm not sure what the easy way to get the dependencies would be without nix. |
| 2022-06-29 11:24:53 +0200 | <liskin> | alternateved: we'd drop the patch but I don't know how to change the env vars in the flake because I know nil about nix |
| 2022-06-29 11:25:42 +0200 | <liskin> | [Leary]: I mainly asked downstream for a preferred way to do this, but yeah I should have asked you first, sorry |
| 2022-06-29 11:26:19 +0200 | <liskin> | So I'd say the way forward is to upstream the patch with the suggested var names and then update the flake |
| 2022-06-29 11:26:41 +0200 | <liskin> | (I'm busy with work now but can do the former later) |
| 2022-06-29 11:32:22 +0200 | <[Leary]> | We don't need to do anything with env vars in the flake; just drop the patch and dependency on unstable. nixpkgs would just need to s/NIX_GHC/XMONAD_GHC in their xmonad wrapper, but we can leave it to them or drop a simple PR. |
| 2022-06-29 11:33:13 +0200 | <[Leary]> | It would build, but not rebuild correctly until the latter change went in. |
| 2022-06-29 11:49:42 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 246 seconds) |
| 2022-06-29 12:11:18 +0200 | alternateved | (~alternate@185.216.35.254) (Remote host closed the connection) |
| 2022-06-29 12:12:17 +0200 | benin0 | (~benin@183.82.28.242) |
| 2022-06-29 12:13:23 +0200 | alternateved | (~alternate@185.216.35.254) |
| 2022-06-29 12:30:48 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2022-06-29 14:14:11 +0200 | gdd1 | (~gdd@2001:470:1f13:187:e8a5:fbff:fe29:42f5) (Ping timeout: 255 seconds) |
| 2022-06-29 14:15:06 +0200 | gdd1 | (~gdd@2001:470:1f13:187:e8a5:fbff:fe29:42f5) |
| 2022-06-29 14:26:47 +0200 | davve_ | (davve@bsd.douchedata.com) (Remote host closed the connection) |
| 2022-06-29 15:33:24 +0200 | qbt | (~qbt@user/edun) (Ping timeout: 272 seconds) |
| 2022-06-29 16:01:44 +0200 | number-set[m] | (~number-se@2001:470:69fc:105::2:3a31) |
| 2022-06-29 16:06:01 +0200 | sagax | (~sagax_nb@user/sagax) (Read error: Connection reset by peer) |
| 2022-06-29 16:13:47 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-06-29 16:20:27 +0200 | sagax | (~sagax_nb@user/sagax) |
| 2022-06-29 16:30:04 +0200 | benin0 | (~benin@183.82.28.242) (Quit: The Lounge - https://thelounge.chat) |
| 2022-06-29 16:31:15 +0200 | _jak | (~jak@cpe-67-244-101-214.nyc.res.rr.com) |
| 2022-06-29 16:35:20 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 268 seconds) |
| 2022-06-29 16:57:12 +0200 | <geekosaur> | re PR 727, I'm still not fond of `Data.Default` although I acknowledge that it makes things easier for users — but it also makes it easier for users to shoot themselves in the foot when it's not or can't be applicable, but fails to throw a type error because it can come up with a way to produce garbage (cf. #293) |
| 2022-06-29 16:59:19 +0200 | qbt | (~qbt@user/edun) |
| 2022-06-29 17:01:04 +0200 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Quit: leaving) |
| 2022-06-29 17:08:43 +0200 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
| 2022-06-29 17:27:25 +0200 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 260 seconds) |
| 2022-06-29 17:50:21 +0200 | mantis_one | (~mantis_on@207.248.198.65) |
| 2022-06-29 17:51:45 +0200 | mantis_one | (~mantis_on@207.248.198.65) (Client Quit) |
| 2022-06-29 17:54:23 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-06-29 18:00:02 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.5) |
| 2022-06-29 18:00:08 +0200 | rarufu[m] | (~rarufumat@2001:470:69fc:105::9589) (Quit: You have been kicked for being idle) |
| 2022-06-29 18:00:14 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2022-06-29 18:02:36 +0200 | mantis_one | (~mantis_on@207.248.198.65) |
| 2022-06-29 18:05:55 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.5) |
| 2022-06-29 18:06:40 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2022-06-29 18:07:05 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Client Quit) |
| 2022-06-29 18:08:11 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2022-06-29 18:10:17 +0200 | dschrempf | (~dominik@070-207.dynamic.dsl.fonira.net) (Client Quit) |
| 2022-06-29 18:25:56 +0200 | <mantis_one> | Hi everyone, Could anybody help me? |
| 2022-06-29 18:25:56 +0200 | <mantis_one> | When I try to recompile XMonad sends an xmessage error in weird fonts. I've always had that issue on Manjaro and I have solved it installing xorg-fonts. Now is happening again and even though xfontsel is showing alphabetical letters I receive this error message when recompiling xmonad: "Warning: Cannot convert string |
| 2022-06-29 18:25:57 +0200 | <mantis_one> | "-*-fixed-medium-r-normal-*-18-*-*-*-*-*-*-*,-*-fixed-*-*-*-*-18-*-*-*-*-*-*-*,-*-*-*-*-*-*-18-*-*-*-*-*-*-*" to type FontSet" |
| 2022-06-29 18:35:42 +0200 | <geekosaur> | xmonad itself doesn't use fonts, so that must be xmessage.it is possible that manjaro has dropped support for bitmapped fonts entirely, I guess, in which case you need a replacement for xmessage |
| 2022-06-29 18:36:14 +0200 | <geekosaur> | (although if they dropped bitmap fonts they should really also drop the programs that only support bitmapped fonts) |
| 2022-06-29 18:40:12 +0200 | <geekosaur> | (I have such a replacement but it doesn't seem to work right now; I need to switch it to debugging mode and see what the change to use it throughout core and contrib did…) |
| 2022-06-29 18:44:30 +0200 | <mantis_one> | Hi, thanks for the reply geekosaur Yes it's an xmessage issue you are right, the problem for me is that it's where the xmonad error appear. When I do xmessage "Hello World" it prints fine, it just sends a warning (Warning: Missing charsets in String to FontSet conversion), but it works. I have a doubt here, it's saying it's trying to convert a |
| 2022-06-29 18:44:30 +0200 | <mantis_one> | string with 3 logical font descriptions, shouldn't it be just one? and where does that string comes from? Maybe I could change it. |
| 2022-06-29 18:45:16 +0200 | <geekosaur> | I expect it's from the app-defaults file |
| 2022-06-29 18:45:25 +0200 | <mantis_one> | OK |
| 2022-06-29 18:45:25 +0200 | <geekosaur> | we don't pass a FontSet |
| 2022-06-29 18:45:30 +0200 | <mantis_one> | got it |
| 2022-06-29 18:45:50 +0200 | <mantis_one> | I'll search the xmessage files |
| 2022-06-29 18:47:02 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-06-29 18:52:33 +0200 | <Solid> | geekosaur: we do pass a fontSet! |
| 2022-06-29 18:53:27 +0200 | <Solid> | https://github.com/xmonad/xmonad/blob/master/src/XMonad/Core.hs#L458 |
| 2022-06-29 18:54:05 +0200 | <geekosaur> | bleh |
| 2022-06-29 18:54:15 +0200 | <geekosaur> | at least I know why my wrapper stopped working |
| 2022-06-29 18:54:56 +0200 | <geekosaur> | so that means none of those fonts can be resolved, which means xorg-fonts isn't installing bitmapped fonts any more |
| 2022-06-29 18:55:12 +0200 | <geekosaur> | and xmessage can't use xft fonts |
| 2022-06-29 18:57:18 +0200 | <mantis_one> | Solid: thanks! Guys, that's exactly the message I'm receiving. The first font description I don't have it. Is that why is sending me an error? |
| 2022-06-29 19:00:49 +0200 | <geekosaur> | it should fall back to the others if the first fails, or at least that's the intent |
| 2022-06-29 19:02:11 +0200 | <geekosaur> | actually it's sending you a warning and it produces that warning if any of the specified fonts fails to load |
| 2022-06-29 19:02:23 +0200 | <geekosaur> | it will generate an error if none of them can be loaded |
| 2022-06-29 19:03:14 +0200 | <mantis_one> | so it's loading a font |
| 2022-06-29 19:03:49 +0200 | <mantis_one> | I got a warning not an error |
| 2022-06-29 19:04:43 +0200 | <geekosaur> | right, and as long as it displays something it should be okay. (sadly that's not guaranteed) |
| 2022-06-29 19:05:12 +0200 | <geekosaur> | I wonder if we can at least specify the charset at the end so people don't get smacked with unexpected BIG5 or etc. |
| 2022-06-29 19:14:37 +0200 | <mantis_one> | OK, so as I said, this similarly, has always happened on manjaro, but when I added a font on .Xresources it fixed the issue. Now xmessage is printing fine when I do it on my own, but printing the weird "manjaro default font" when I recompile xmonad. |
| 2022-06-29 19:16:05 +0200 | <mantis_one> | Wyh could this be happening? |
| 2022-06-29 19:16:12 +0200 | <mantis_one> | *Why |
| 2022-06-29 19:21:43 +0200 | <geekosaur> | I don't know. bitmap fonts are server-side so user config shouldn't matter |
| 2022-06-29 19:22:57 +0200 | <geekosaur> | well, actually, that suggests that xmessage's default font (including default size) is found but the one forced with -xrm isn't |
| 2022-06-29 19:23:12 +0200 | <geekosaur> | I think the only size guaranteed to be around is 10 |
| 2022-06-29 19:23:50 +0200 | <geekosaur> | you may need to install a package with some scalable fonts |
| 2022-06-29 19:24:06 +0200 | <geekosaur> | non-xft scalable fonts (probably adobe type1) |
| 2022-06-29 19:24:32 +0200 | <mantis_one> | let me try that |
| 2022-06-29 19:25:04 +0200 | <geekosaur> | or we should change the -xrm we send to use size 10 instead of 18 |
| 2022-06-29 19:30:54 +0200 | <mantis_one> | will https://aur.archlinux.org/packages/adobe-base-14-fonts be OK? It says adobe type1 |
| 2022-06-29 19:33:17 +0200 | <mantis_one> | it didn't work :( |
| 2022-06-29 19:38:23 +0200 | <geekosaur[m]> | You would either need to log out and back in, or manually add the font path with `xset fp+` followed by the directory containing the fonts |
| 2022-06-29 19:39:36 +0200 | <geekosaur[m]> | The X11 startup removes directories that are empty from the font path |
| 2022-06-29 19:39:50 +0200 | <mantis_one> | I'll log out |
| 2022-06-29 19:40:04 +0200 | mantis_one | (~mantis_on@207.248.198.65) (Quit: Client closed) |
| 2022-06-29 19:43:18 +0200 | mantis_one | (~mantis_on@207.248.198.65) |
| 2022-06-29 19:47:16 +0200 | <mantis_one> | Hi again. OK, I tried recompiling Xmonad and it sent this |
| 2022-06-29 19:47:17 +0200 | <mantis_one> | Warning: Cannot convert string "-*-fixed-medium-r-normal-*-18-*-*-*-*-*-*-*,-*-fixed-*-*-*-*-18-*-*-*-*-*-*-*,-*-*-*-*-*-*-18-*-*-*-*-*-*-*" to type FontSet |
| 2022-06-29 19:47:17 +0200 | <mantis_one> | Warning: Missing charsets in String to FontSet conversion |
| 2022-06-29 19:47:18 +0200 | <mantis_one> | Warning: Cannot convert string "-*-*-*-*-*-*-*-*-*-*-*-*-*-*" to type FontStruct |
| 2022-06-29 19:47:18 +0200 | <mantis_one> | Warning: Unable to load any usable ISO8859 font |
| 2022-06-29 19:47:19 +0200 | <mantis_one> | Warning: Unable to load any usable ISO8859 font |
| 2022-06-29 19:47:19 +0200 | <mantis_one> | Error: Aborting: no font found |
| 2022-06-29 19:47:20 +0200 | <mantis_one> | And xmessage run by itself sends: |
| 2022-06-29 19:47:20 +0200 | <mantis_one> | Warning: Cannot convert string "-*-fixed-medium-r-normal-*-18-*-*-*-*-*-*-*" to type FontStruct |
| 2022-06-29 19:47:21 +0200 | <mantis_one> | Warning: Unable to load any usable ISO8859 font |
| 2022-06-29 19:47:22 +0200 | <mantis_one> | Error: Aborting: no font found |
| 2022-06-29 19:50:56 +0200 | <mantis_one> | Probably this is a font and not an xmonad issue, but I don't know what to do. I would appreciate the help. Also because of this warning: Warning: Cannot convert string "-*-*-*-*-*-*-*-*-*-*-*-*-*-*" to type FontStruct, I beleibe is reading my .Xresources file. It didn't show that before. I use the logical font with only *s when I'm trying to make |
| 2022-06-29 19:50:57 +0200 | <mantis_one> | it work, then I put a more specific one. |
| 2022-06-29 19:54:16 +0200 | <geekosaur> | that sounds very wrong, like it removed the other bitmapped fonts |
| 2022-06-29 19:56:30 +0200 | mantis_one | (~mantis_on@207.248.198.65) (Quit: Client closed) |
| 2022-06-29 19:59:11 +0200 | mantis_one | (~mantis_on@207.248.198.65) |
| 2022-06-29 20:00:22 +0200 | <mantis_one> | yes, I unistalled adobe-base-14-fonts. Maybe it's time for me to try another distroX) |
| 2022-06-29 20:01:12 +0200 | <geekosaur> | I'm using ubuntu but I know some people don't like big fixed distros |
| 2022-06-29 20:01:14 +0200 | <mantis_one> | I unistalled adobe-base-14-fonts and it's giving the same error |
| 2022-06-29 20:01:48 +0200 | <geekosaur> | if it uninstalled xorg-fonts then uninstalling it won't have brought the other one back. but also check your .Xresources change |
| 2022-06-29 20:01:48 +0200 | <mantis_one> | yeah, I don't like having too "old" programs |
| 2022-06-29 20:02:05 +0200 | <geekosaur> | maybe you should try something like nixos |
| 2022-06-29 20:02:32 +0200 | <geekosaur> | (also if you change .Xresources you either need to run `xrdb ~/.Xresources` or log out and back in |
| 2022-06-29 20:07:49 +0200 | <mantis_one> | I've heard good things about nixos. I was thinking of endeavouros, since I love the aur. But I've (don't know if it's true) that manjaro presents issues thar other disttros don't. I like Manjaro for the gaming. |
| 2022-06-29 20:07:49 +0200 | <mantis_one> | Just did `xrdb ~/.Xresources` and xmessage is showing the same error, the same for xfontsel |
| 2022-06-29 20:08:21 +0200 | <mantis_one> | But I've heard(don't know if it's true) that manjaro presents issues thar other disttros don't. I like Manjaro for the gaming. |
| 2022-06-29 20:11:44 +0200 | <geekosaur> | I haven't heard that. We've had significant problems with Arch because they insist on packaging Haskell stuff to require -dynamic and it causes lots of random breakage |
| 2022-06-29 20:12:31 +0200 | <geekosaur> | including people's configs stopping working after an Arch upgrade because they didn't follow the big warning on the arch wiki page for xmonad |
| 2022-06-29 20:18:05 +0200 | <mantis_one> | that's fixed with a --recompile right? |
| 2022-06-29 20:19:42 +0200 | <geekosaur> | yes, but you have to make sure you do it before you log out or reboot, or you won't be able to get back in |
| 2022-06-29 20:19:49 +0200 | <geekosaur> | (at least not via the gui) |
| 2022-06-29 20:20:17 +0200 | <geekosaur> | sadly a lot of arch users tend to forget that part and then we get bug reports |
| 2022-06-29 20:20:34 +0200 | <geekosaur> | that we can't do anything about since it all comes down to how arch packages xmonad |
| 2022-06-29 20:22:59 +0200 | <mantis_one> | I have KDE and Xmonad so I reboot before the recompile then go to kde and recompile there and then go back to xmonad. I could use the tty to, but it became an habit for me to do it this way. Maybe I'll change it :) |
| 2022-06-29 20:23:26 +0200 | <Solid> | there has been an issue to make a pacman hook for this for years I think |
| 2022-06-29 20:23:40 +0200 | <Solid> | but no one seems to care on the Arch side of things |
| 2022-06-29 20:23:47 +0200 | <mantis_one> | lol |
| 2022-06-29 20:23:56 +0200 | <geekosaur> | if you like kde then there's a way to use xmonad as kde's window manager. sadly it currently requires a patch to kde |
| 2022-06-29 20:24:10 +0200 | <geekosaur> | which means it's easiest to do under gentoo |
| 2022-06-29 20:24:53 +0200 | geekosaur | uses xmonad as window manager for mate |
| 2022-06-29 20:25:19 +0200 | <geekosaur> | but there are at least three users who patch kde to use xmonad there |
| 2022-06-29 20:25:51 +0200 | <mantis_one> | That's sounds so good. I didn't know you could use a TWM inside a DE :o |
| 2022-06-29 20:26:40 +0200 | <geekosaur> | you can't with gnome because everything lives inside gnome-shell, but other desktops are friendlier |
| 2022-06-29 20:26:42 +0200 | _jak | (~jak@cpe-67-244-101-214.nyc.res.rr.com) (Quit: leaving) |
| 2022-06-29 20:26:44 +0200 | <geekosaur> | and someone |
| 2022-06-29 20:27:14 +0200 | <geekosaur> | 's continued to support gnome-flashback so you get a gnome 3-ish gnome 2 environment if you try to switch window managers |
| 2022-06-29 20:30:05 +0200 | <mantis_one> | I'm not thinking of using gentoo right now (lot of things to do and it seems there is a lot to learn to use gentoo), but i'ts nice to know that |
| 2022-06-29 20:37:12 +0200 | <mantis_one> | thanks a lot guys (y) |
| 2022-06-29 20:52:51 +0200 | <alternateved> | EndeavourOS is a really nice distro |
| 2022-06-29 20:53:08 +0200 | <alternateved> | Still Arch with Arch-like problems |
| 2022-06-29 20:54:06 +0200 | <alternateved> | I can recommend openSUSE Tumbleweed for rolling release, but the package availability is not that good |
| 2022-06-29 20:54:48 +0200 | <alternateved> | geekosaur: are you sure you have to patch kde to use different wm with it? |
| 2022-06-29 20:57:14 +0200 | <geekosaur[m]> | The problem isn't using a different WM as such; it's a conflict between Plasma and how xmonad manages its windows |
| 2022-06-29 20:57:38 +0200 | <alternateved> | Ah, I see |
| 2022-06-29 21:03:16 +0200 | <geekosaur> | https://github.com/xmonad/xmonad/issues/174 if you're interested |
| 2022-06-29 21:03:35 +0200 | <geekosaur> | kde assumes a non-tiling wm will manage them and the result is kinda bad |
| 2022-06-29 21:04:45 +0200 | <alternateved> | Yeah, someone who uses plasma with xmonad mentioned that krunner is acting up |
| 2022-06-29 21:05:28 +0200 | <alternateved> | And in the end that person is using another launcher, more suited for the challenge |
| 2022-06-29 21:06:51 +0200 | <alternateved> | I'll pass this info, maybe that will be of value to that person, thanks! |
| 2022-06-29 21:27:54 +0200 | alternateved | (~alternate@185.216.35.254) (Ping timeout: 246 seconds) |
| 2022-06-29 21:46:12 +0200 | mantis_one | (~mantis_on@207.248.198.65) (Quit: Client closed) |
| 2022-06-29 21:54:34 +0200 | alternateved | (~alternate@45.134.212.176) |
| 2022-06-29 22:26:50 +0200 | qbt | (~qbt@user/edun) (Ping timeout: 268 seconds) |
| 2022-06-29 22:47:16 +0200 | mantis_one | (~mantis_on@207.248.198.65) |
| 2022-06-29 22:51:06 +0200 | <mantis_one> | Hi, I just asked for help here to fix that I got a weird font on Manjaro when xmessage sent XMonad erros. I wanted to tell I've installed endeavouros and I get alphabetic normal error messages, this is good. |
| 2022-06-29 22:56:16 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-06-29 23:12:39 +0200 | mantis_one | (~mantis_on@207.248.198.65) (Quit: Client closed) |
| 2022-06-29 23:50:53 +0200 | <MrElendig> | replace xmessage with one of the more modern alternatives |
| 2022-06-29 23:51:05 +0200 | <MrElendig> | xmessage is just broken |