2022/07/13

2022-07-13 00:12:21 +0200pok_(~pok@41.157.227.24) (Ping timeout: 272 seconds)
2022-07-13 00:14:41 +0200 <wusticality> hey liskin
2022-07-13 00:15:16 +0200 <wusticality> are you saying I shouldn't run spawnOnce "setxkbmap -option altwin:swap_alt_win" in xmonad.hs?
2022-07-13 00:16:43 +0200 <geekosaur> on my system you put the -option part in /etc/default/keyboard in the XKBOPTIONS field
2022-07-13 00:17:30 +0200 <wusticality> my apologies haha
2022-07-13 00:17:45 +0200 <wusticality> are you saying editing /etc/default/keyboard would prevent settings from being wiped?
2022-07-13 00:18:02 +0200 <geekosaur> it would mean your settings get reapplied whenever whatever it is happens
2022-07-13 00:18:19 +0200 <geekosaur> and "udevadm monitor" will probably show you the whatever-it-is
2022-07-13 00:18:25 +0200 <geekosaur> as I understand it
2022-07-13 00:18:35 +0200 <wusticality> looks like that file contains
2022-07-13 00:18:37 +0200 <wusticality> XKBLAYOUT=us
2022-07-13 00:18:37 +0200 <wusticality> BACKSPACE=guess
2022-07-13 00:19:27 +0200 <geekosaur> https://paste.tomsmeding.com/oQ3f8qPN
2022-07-13 00:20:16 +0200 <geekosaur> so it sounds like you add XKBOPTIONS="altwin:swap_alt_win"
2022-07-13 00:21:23 +0200 <wusticality> should I remove the line from my xmonad config then?
2022-07-13 00:22:08 +0200 <geekosaur> yes, it shouldn't be necessary after you do that
2022-07-13 00:22:20 +0200 <geekosaur> (and restart the X server, which may require a reboot)
2022-07-13 00:22:55 +0200 <wusticality> I have to say, you have all been incredibly helpful
2022-07-13 00:23:03 +0200 <wusticality> let me try that quick
2022-07-13 00:25:55 +0200alternateved(~alternate@staticline-31-183-144-54.toya.net.pl) (Remote host closed the connection)
2022-07-13 00:28:45 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-13 00:31:17 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-13 00:31:19 +0200 <wusticality> This appears to work!
2022-07-13 00:31:25 +0200 <wusticality> (so far)
2022-07-13 00:38:43 +0200 <wusticality> which is *ahem* outstanding
2022-07-13 00:40:29 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-13 00:41:40 +0200 <wusticality> here's yet another noob question - is there some way to get xmonad to remember what applications were open and on what workspaces? and perhaps the state of my layouts on each workspace? that'd be rad. I heard about lxsession but I'm not sure if that's a red herring
2022-07-13 00:42:29 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Read error: Connection reset by peer)
2022-07-13 00:42:36 +0200tjmciver(~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Ping timeout: 244 seconds)
2022-07-13 00:42:40 +0200 <geekosaur> lxsession may be the best that you can do, but it won't remember layout state
2022-07-13 00:42:48 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-13 00:43:40 +0200 <geekosaur> xsm can do some session stuff but it predates workspaces and won't save those
2022-07-13 00:46:13 +0200nomorehasu(~user@2804:30c:137f:2400:267:bffd:8a8f:f9)
2022-07-13 00:54:48 +0200nomorehasu(~user@2804:30c:137f:2400:267:bffd:8a8f:f9) (Remote host closed the connection)
2022-07-13 01:00:22 +0200 <wusticality> $ udevadm monitor
2022-07-13 01:00:23 +0200 <wusticality> monitor will print the received events for:
2022-07-13 01:00:23 +0200 <wusticality> UDEV - the event which udev sends out after rule processing
2022-07-13 01:00:24 +0200 <wusticality> KERNEL - the kernel uevent
2022-07-13 01:00:24 +0200 <wusticality> KERNEL[149.111425] add /module/tls (module)
2022-07-13 01:00:25 +0200 <wusticality> UDEV [149.112484] add /module/tls (module)
2022-07-13 01:00:29 +0200 <wusticality> Looks like some event happened
2022-07-13 01:13:36 +0200 <geekosaur> won't be the keyboard though
2022-07-13 01:13:59 +0200 <geekosaur> udev triggers on any device load/unload/state change
2022-07-13 01:14:11 +0200 <wusticality> ah
2022-07-13 01:14:18 +0200 <wusticality> how would I know it's keyboard related?
2022-07-13 01:17:12 +0200 <geekosaur> subsystem contains "input", apparently
2022-07-13 01:18:29 +0200 <wusticality> ah ok
2022-07-13 01:19:02 +0200 <geekosaur> apparently you can use `udevadm monitor --subsystem-match=input` to limit it to that
2022-07-13 01:19:18 +0200 <geekosaur> rather than try to spot it amid other stuff
2022-07-13 02:13:15 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a)
2022-07-13 03:37:03 +0200abhinav(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2022-07-13 04:04:09 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 272 seconds)
2022-07-13 04:22:51 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-07-13 04:26:50 +0200td_(~td@94.134.91.223) (Ping timeout: 244 seconds)
2022-07-13 04:28:59 +0200td_(~td@muedsl-82-207-238-241.citykom.de)
2022-07-13 04:34:33 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds)
2022-07-13 04:42:38 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Ping timeout: 255 seconds)
2022-07-13 04:56:07 +0200sagax(~sagax_nb@user/sagax)
2022-07-13 05:05:05 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 244 seconds)
2022-07-13 05:38:59 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Remote host closed the connection)
2022-07-13 05:39:19 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-13 05:40:50 +0200tjmciver__(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-13 05:40:50 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Read error: Connection reset by peer)
2022-07-13 05:42:18 +0200tjmciver_(~tjmciver@cpe-172-101-32-70.maine.res.rr.com)
2022-07-13 05:42:18 +0200tjmciver__(~tjmciver@cpe-172-101-32-70.maine.res.rr.com) (Read error: Connection reset by peer)
2022-07-13 06:27:28 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at)
2022-07-13 07:18:10 +0200rieper(~riepernet@webmirror.geo.uni-leipzig.de) (Ping timeout: 240 seconds)
2022-07-13 07:22:31 +0200sagax(~sagax_nb@user/sagax) (Quit: Konversation terminated!)
2022-07-13 07:24:15 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-13 07:29:44 +0200pok_(~pok@41.157.227.24)
2022-07-13 07:37:29 +0200rieper(~riepernet@webmirror.geo.uni-leipzig.de)
2022-07-13 07:38:51 +0200pok_(~pok@41.157.227.24) (Ping timeout: 272 seconds)
2022-07-13 08:02:48 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at) (Ping timeout: 244 seconds)
2022-07-13 08:20:08 +0200alternateved(~alternate@5.253.206.53)
2022-07-13 08:30:30 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net)
2022-07-13 08:40:31 +0200benin0(~benin@183.82.29.162)
2022-07-13 09:05:54 +0200alternateved(~alternate@5.253.206.53) (Remote host closed the connection)
2022-07-13 09:08:18 +0200alternateved(~alternate@5.253.206.53)
2022-07-13 09:24:21 +0200abhinav(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 268 seconds)
2022-07-13 09:49:57 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Ping timeout: 272 seconds)
2022-07-13 09:52:29 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:99fe:ae00:5424:6d23)
2022-07-13 09:55:19 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-07-13 10:06:12 +0200alternateved(~alternate@5.253.206.53) (Remote host closed the connection)
2022-07-13 10:06:31 +0200alternateved(~alternate@5.253.206.53)
2022-07-13 10:14:39 +0200benin0(~benin@183.82.29.162) (Ping timeout: 272 seconds)
2022-07-13 10:17:24 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:99fe:ae00:5424:6d23) (Ping timeout: 276 seconds)
2022-07-13 10:22:44 +0200thaumavorio(~thaumavor@thaumavor.io) (Quit: ZNC 1.8.2 - https://znc.in)
2022-07-13 10:24:01 +0200thaumavorio(~thaumavor@thaumavor.io)
2022-07-13 10:34:12 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 244 seconds)
2022-07-13 11:10:21 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de)
2022-07-13 11:36:32 +0200mc47(~mc47@xmonad/TheMC47)
2022-07-13 12:33:42 +0200cfricke(~cfricke@user/cfricke)
2022-07-13 14:31:34 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at)
2022-07-13 15:03:20 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a)
2022-07-13 15:19:18 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:2f00:f9a4:8560:d503)
2022-07-13 15:50:45 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.5)
2022-07-13 16:45:30 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a) (Ping timeout: 240 seconds)
2022-07-13 16:56:21 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:2f00:f9a4:8560:d503) (Remote host closed the connection)
2022-07-13 16:56:42 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:deae:e1cf:72:7368)
2022-07-13 17:11:27 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-07-13 17:40:30 +0200stonedHash
2022-07-13 17:56:07 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at) (Quit: WeeChat 3.5)
2022-07-13 17:57:36 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Ping timeout: 276 seconds)
2022-07-13 17:59:43 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-07-13 18:24:15 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:deae:e1cf:72:7368) (Ping timeout: 276 seconds)
2022-07-13 18:27:10 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Ping timeout: 240 seconds)
2022-07-13 18:32:36 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-07-13 18:54:50 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:dd89:2ce:aa76:b885)
2022-07-13 19:01:38 +0200allbery_b(~geekosaur@xmonad/geekosaur)
2022-07-13 19:01:38 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2022-07-13 19:01:41 +0200allbery_bgeekosaur
2022-07-13 19:17:09 +0200jeeeun(~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat)
2022-07-13 19:19:05 +0200jeeeun(~jeeeun@78.40.148.178)
2022-07-13 19:49:00 +0200jeeeun(~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat)
2022-07-13 19:53:30 +0200jeeeun(~jeeeun@78.40.148.178)
2022-07-13 19:54:05 +0200 <cidra[m]> Hey guys can you see xmonad docs via lsp? It seems that i can't
2022-07-13 19:54:40 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-13 19:55:03 +0200 <cidra[m]> If i do stack haddock --open xmonad i can see the docs, but on vscode i see no docs through autocompletion
2022-07-13 19:55:05 +0200 <geekosaur> I have heard this before but I don't use lsp so don't have any personal experience
2022-07-13 20:06:05 +0200gormulent(~gormulent@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-13 20:09:10 +0200gormulent(~gormulent@c-67-161-204-49.hsd1.co.comcast.net) (Client Quit)
2022-07-13 20:13:05 +0200 <zawaken> lsp with hls in neovim works for haskell, but not for xmonad specific haskell in my experience
2022-07-13 20:14:48 +0200wusticality1(~user@c-67-161-204-49.hsd1.co.comcast.net)
2022-07-13 20:15:26 +0200 <cidra[m]> :( that sucks
2022-07-13 20:16:48 +0200 <wusticality> in general, lsp-mode is pretty awesome
2022-07-13 20:16:52 +0200 <wusticality> I use it for rust / golang
2022-07-13 20:20:15 +0200 <zawaken> seems I might have set up my hie.yaml file wrong, but I am not sure about that at all.
2022-07-13 20:23:40 +0200 <zawaken> setting my hie.yaml up with the second one here, seems to make it come up with lsp entries for xmonad.
2022-07-13 20:23:45 +0200 <zawaken> http://ix.io/44hc
2022-07-13 20:27:56 +0200 <liskin> there's no way to write a hie.yaml that would work with ~/.xmonad/xmonad.hs without also having a something.cabal and possibly also cabal.project/stack.yaml somewhere
2022-07-13 20:28:24 +0200 <liskin> (well maybe there is but it involves some very advanced ghc/envvar hackery that nobody ever really bothered to figure out)
2022-07-13 20:28:33 +0200 <liskin> this is unfortunately a limitation of hls/hie
2022-07-13 20:30:04 +0200 <zawaken> yeah I have a stack.yaml in the same directory as well (.config/xmonad)
2022-07-13 20:31:46 +0200 <liskin> good, you're like 40% there 👍 :-)
2022-07-13 20:31:50 +0200 <liskin> maybe 30.
2022-07-13 20:32:48 +0200 <liskin> oh actually with that hie.yaml it might just do something…
2022-07-13 20:33:20 +0200 <liskin> it's not entirely kosher, but… :-)
2022-07-13 20:34:05 +0200 <zawaken> Yeah it seems to output something, tested with clickJustFocuses, and it showed up as "clickJustFocuses [LSP]" in cmp-nvim-lsp
2022-07-13 20:34:26 +0200 <zawaken> What would be the kosher way of setting up that hie.yaml?
2022-07-13 20:40:14 +0200 <wusticality> anyone know if there's a cooler way to show an overlay for things like the current time, etc. - maybe via a scratchpad?
2022-07-13 20:40:17 +0200 <wusticality> I saw tty-time
2022-07-13 20:40:24 +0200 <wusticality> I find xmobar uses too much space
2022-07-13 20:40:38 +0200 <wusticality> kinda like a way to do widgets that you can show / hide in the center of the screen
2022-07-13 20:41:14 +0200 <zawaken> eww might be something worth looking at https://github.com/elkowar/eww
2022-07-13 20:41:26 +0200 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/pyanfar/xmonad.hs#L107-L110
2022-07-13 20:41:58 +0200 <geekosaur> although I needed to define a custom app-defaults file to set the colors correctly iirc; would need to dig that out of a backup
2022-07-13 20:42:00 +0200 <wusticality> fascinating, I'll take a look
2022-07-13 20:43:06 +0200 <zawaken> I think geekosaur's implementation in a scratchpad might be better than eww though
2022-07-13 20:43:14 +0200 <geekosaur> stuck a digital clock at the top right of my monitor, which put it in a place that was usually empty
2022-07-13 20:49:40 +0200 <geekosaur> hm, nope, looks like I just used the usual dclock app-defaults
2022-07-13 20:51:20 +0200 <geekosaur> eww certainly looks fancier (and more mac-like)
2022-07-13 20:53:07 +0200 <zawaken> there are many great examples of its capabilities on r/unixporn
2022-07-13 20:54:07 +0200 <zawaken> I currently use eww as my bar instead of polybar/xmobar
2022-07-13 20:56:00 +0200 <geekosaur> dear vs code, whatever in the world made you conclude I'm on arm64?
2022-07-13 20:56:41 +0200 <geekosaur> flip side I guess I'm protected against at least some exploits 😈
2022-07-13 21:24:15 +0200 <geekosaur> so it took a ridiculous amount of time for vs code to process my xmonad.hs, but it seems to be working without an hie.yaml. then again, I have a full cabal setup
2022-07-13 21:24:45 +0200 <geekosaur> (https://github.com/geekosaur/xmonad.hs/blob/skkukuk)
2022-07-13 21:25:51 +0200 <zawaken> that link seems to be broken.
2022-07-13 21:26:13 +0200 <geekosaur> hm, I chopped that off a working link, but probably github doesn't work that way
2022-07-13 21:26:24 +0200 <geekosaur> https://github.com/geekosaur/xmonad.hs/tree/skkukuk
2022-07-13 21:26:27 +0200 <zawaken> yea tree instead of blob
2022-07-13 21:28:08 +0200 <zawaken> https://github.com/Zawaken/dotfiles/tree/master/.config/xmonad here's my xmonad directory. the "install_xmonad_with_stack.sh" is redundant there though
2022-07-13 21:30:18 +0200 <zawaken> xmonad.hs isn't very pretty though
2022-07-13 21:33:34 +0200 <zawaken> do you use any vscode plugins to get linting/lsp then or does it just work without the hie.yaml?
2022-07-13 21:34:15 +0200 <geekosaur> I installed the recommended Haskell plugin
2022-07-13 21:34:47 +0200 <zawaken> Ah
2022-07-13 21:34:56 +0200 <geekosaur> I presume that since I have a full cabal setup the default cradle works fine
2022-07-13 21:37:08 +0200 <geekosaur> not getting hinting I think, but I didn't install hlint
2022-07-13 21:37:25 +0200 <zawaken> that makes sense, I just have a very barebones stack setup in mine, used to compile xmonad with
2022-07-13 21:39:12 +0200 <zawaken> I am VERY new to haskell, though I've used xmonad for a year or so, only now starting to try learning haskell
2022-07-13 22:01:20 +0200 <wusticality> here's a question - what's the best way to increase keypress repeat speed when using xmonad? also, is there some way to start xmonad with the numlock on? I always have to turn it on manually which is a bit frustrating
2022-07-13 22:03:55 +0200 <geekosaur> xset r rate … (see the xset manpage)
2022-07-13 22:04:02 +0200 <zawaken> seems like the numlock part is earily done with numlockx
2022-07-13 22:04:21 +0200 <geekosaur> numlock on/off is that, or configurable in xorg.conf
2022-07-13 22:04:41 +0200 <zawaken> just install numlockx and chuck "numlockx &" in startx
2022-07-13 22:04:49 +0200 <zawaken> xinitrc**
2022-07-13 22:05:03 +0200 <geekosaur> they're using a different setup
2022-07-13 22:05:36 +0200 <geekosaur> ~/.xmonad/xmonad-session-rc
2022-07-13 22:05:47 +0200 <geekosaur> make sure you have it backgrounded
2022-07-13 22:06:04 +0200 <zawaken> Could probably add it as a spawnOnce in xmonad as well
2022-07-13 22:07:39 +0200 <zawaken> yeah I just assume everyone who uses window managers use xorg-xinit to start x, sorry about that
2022-07-13 22:08:18 +0200 <zawaken> assumption based on how I do it.
2022-07-13 22:15:15 +0200wusticality(~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed)
2022-07-13 22:43:49 +0200noex_(~null@2600:8804:14e0:104:8804:14e0:104:0) (Quit: :q!)
2022-07-13 23:00:13 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-07-13 23:06:26 +0200noex(~null@user/noex)
2022-07-13 23:11:44 +0200quarkQuark[m](~quarkquar@2001:470:69fc:105::2:46e2)
2022-07-13 23:18:43 +0200[Leary](~Leary]@122-58-224-198-vdsl.sparkbb.co.nz) (Ping timeout: 272 seconds)
2022-07-13 23:37:29 +0200mvk(~mvk@2607:fea8:5ce3:8500::909a)