2023/08/21

2023-08-21 00:25:35 +0200mvk(~mvk@2607:fea8:5c9a:a600::1c6d)
2023-08-21 00:29:08 +0200tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2023-08-21 01:51:15 +0200mvk(~mvk@2607:fea8:5c9a:a600::1c6d) (Ping timeout: 246 seconds)
2023-08-21 02:02:29 +0200hightower4(~hightower@43-81.dsl.iskon.hr)
2023-08-21 02:05:04 +0200hightower3(~hightower@141-136-238-229.dsl.iskon.hr) (Ping timeout: 252 seconds)
2023-08-21 02:45:24 +0200mvk(~mvk@2607:fea8:5c9a:a600::1c6d)
2023-08-21 04:11:48 +0200td_(~td@i53870934.versanet.de) (Ping timeout: 256 seconds)
2023-08-21 04:13:35 +0200td_(~td@i53870925.versanet.de)
2023-08-21 06:24:46 +0200redgloboli(~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2023-08-21 06:24:48 +0200mvk(~mvk@2607:fea8:5c9a:a600::1c6d) (Ping timeout: 246 seconds)
2023-08-21 06:25:48 +0200redgloboli(~redglobol@user/redgloboli)
2023-08-21 09:19:23 +0200cfricke(~cfricke@user/cfricke)
2023-08-21 09:37:06 +0200ft(~ft@p4fc2ad78.dip0.t-ipconnect.de) (Ping timeout: 245 seconds)
2023-08-21 09:48:56 +0200ft(~ft@p4fc2ad78.dip0.t-ipconnect.de)
2023-08-21 10:08:14 +0200 <deebo> is it possible to define how "activating" a window happens? e.g. i use `aws sso login` in a terminal, and it brings my browser to the same workspace, could i change it to bring it to the other active workspace (other monitor)
2023-08-21 11:30:19 +0200ft(~ft@p4fc2ad78.dip0.t-ipconnect.de) (Quit: leaving)
2023-08-21 11:46:21 +0200 <liskin> deebo: https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.17.1.9/XMonad-Hooks-EwmhDesktops.html#g:5 and https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.17.1.9/XMonad-Hooks-Focus.html is likely what you're looking for
2023-08-21 11:55:32 +0200td_(~td@i53870925.versanet.de) (Ping timeout: 250 seconds)
2023-08-21 12:16:40 +0200diep(~diep@172-104-137-130.ip.linodeusercontent.com)
2023-08-21 12:17:20 +0200td_(~td@i5387092A.versanet.de)
2023-08-21 12:23:51 +0200mc47(~mc47@xmonad/TheMC47)
2023-08-21 12:28:49 +0200td_(~td@i5387092A.versanet.de) (Ping timeout: 246 seconds)
2023-08-21 12:29:35 +0200 <deebo> how does the 'urgent' flag in ewmh works, what does it actually do?
2023-08-21 12:36:26 +0200 <deebo> https://xmonad.github.io/xmonad-docs/xmonad-contrib/XMonad-Hooks-UrgencyHook.html this explained it, have to read more and see what i'd prefer
2023-08-21 13:10:52 +0200td_(~td@i5387093F.versanet.de)
2023-08-21 13:22:02 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 260 seconds)
2023-08-21 13:32:30 +0200td_(~td@i5387093F.versanet.de) (Ping timeout: 246 seconds)
2023-08-21 13:39:22 +0200td_(~td@i5387092D.versanet.de)
2023-08-21 13:54:32 +0200td_(~td@i5387092D.versanet.de) (Ping timeout: 240 seconds)
2023-08-21 14:07:07 +0200td_(~td@83.135.9.23)
2023-08-21 14:36:17 +0200hightower2(~hightower@43-81.dsl.iskon.hr)
2023-08-21 14:37:04 +0200hightower4(~hightower@43-81.dsl.iskon.hr) (Ping timeout: 244 seconds)
2023-08-21 14:41:27 +0200hightower2(~hightower@43-81.dsl.iskon.hr) (Ping timeout: 246 seconds)
2023-08-21 14:44:23 +0200vifon(~vifon@user/vifon) (Quit: WeeChat 3.3)
2023-08-21 14:46:46 +0200diep(~diep@172-104-137-130.ip.linodeusercontent.com) (Remote host closed the connection)
2023-08-21 14:47:03 +0200diep(~diep@172-104-137-130.ip.linodeusercontent.com)
2023-08-21 14:54:56 +0200diep(~diep@172-104-137-130.ip.linodeusercontent.com) (Ping timeout: 250 seconds)
2023-08-21 15:01:24 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-08-21 16:08:34 +0200mc47(~mc47@xmonad/TheMC47)
2023-08-21 16:37:08 +0200hightower2(~hightower@cm-2190.cable.globalnet.hr)
2023-08-21 16:50:52 +0200hightower2(~hightower@cm-2190.cable.globalnet.hr) (Ping timeout: 240 seconds)
2023-08-21 16:51:04 +0200srk-(~sorki@user/srk)
2023-08-21 16:54:58 +0200srk(~sorki@user/srk) (Ping timeout: 252 seconds)
2023-08-21 16:54:58 +0200srk-srk
2023-08-21 17:56:05 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-08-21 17:56:59 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 18:00:08 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-08-21 18:01:03 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 18:05:01 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-08-21 18:07:36 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 246 seconds)
2023-08-21 18:16:56 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 18:19:34 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Client Quit)
2023-08-21 18:22:58 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 19:00:27 +0200yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de) (Ping timeout: 246 seconds)
2023-08-21 19:04:30 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-08-21 19:04:30 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-08-21 19:04:30 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack)
2023-08-21 19:17:04 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-08-21 19:17:31 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack) (Read error: Connection reset by peer)
2023-08-21 19:27:17 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 19:32:14 +0200yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de)
2023-08-21 20:05:27 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-08-21 20:09:46 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-08-21 20:09:46 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-08-21 20:09:46 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack)
2023-08-21 20:26:42 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-08-21 20:26:43 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack) (Read error: Connection reset by peer)
2023-08-21 20:38:44 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 20:44:22 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-08-21 20:44:22 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-08-21 20:44:22 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack)
2023-08-21 21:02:02 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2023-08-21 21:02:05 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack) (Remote host closed the connection)
2023-08-21 21:04:24 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2023-08-21 21:07:39 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-08-21 21:07:39 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-08-21 21:07:39 +0200xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack)
2023-08-21 21:11:56 +0200 <szczot3k> geekosaur: for some reason it works on a second instance of firefox (one with two tabs open), but not the one with netflix, or any other tab on that matter
2023-08-21 21:13:23 +0200 <szczot3k> it doesn't depend on the screen I'm using it on, so it's not xmobar problem itself
2023-08-21 21:13:55 +0200 <geekosaur> odd. I'd be inclined to blame your firefox in that case
2023-08-21 21:14:06 +0200 <szczot3k> one's my "main" window, with a fuckton of tabs (some pinned, some "to read later"), and a "I like to read something while watching netflix" window
2023-08-21 21:14:17 +0200 <szczot3k> the second one can be hidden and doesn't go under xmobar
2023-08-21 21:14:45 +0200 <szczot3k> It also doesn't matter if I fulscreen directly from netflix ("F", or the fullscreen icon), or F11
2023-08-21 21:19:20 +0200 <szczot3k> on that note, chrome also hides xmobar
2023-08-21 21:51:45 +0200ft(~ft@p4fc2ad78.dip0.t-ipconnect.de)
2023-08-21 21:59:24 +0200hightower2(~hightower@213.149.62.191)
2023-08-21 23:13:57 +0200ElKowar(~ElKowar@srv-fin.xware-gmbh.de) (Remote host closed the connection)
2023-08-21 23:14:17 +0200ElKowar(~ElKowar@srv-fin.xware-gmbh.de)
2023-08-21 23:32:24 +0200szczot3k(fkszczot@wikimedia/fkszczot) (Ping timeout: 246 seconds)
2023-08-21 23:36:22 +0200szczot3k(fkszczot@wikimedia/fkszczot)