Logs: liberachat/#xmonad
| 2022-07-11 19:24:48 | × | chomwitt quits (~chomwitt@2a02:587:dc0d:4a00:e44b:517c:8b93:d71d) (Ping timeout: 276 seconds) |
| 2022-07-11 19:27:33 | → | chomwitt joins (~chomwitt@2a02:587:dc0d:4a00:68e4:4ca8:a63:19fd) |
| 2022-07-11 19:27:56 | → | lambdadelta-[m] joins (~lambdadel@2001:470:69fc:105::2:44c7) |
| 2022-07-11 19:49:59 | × | chomwitt quits (~chomwitt@2a02:587:dc0d:4a00:68e4:4ca8:a63:19fd) (Remote host closed the connection) |
| 2022-07-11 19:50:23 | → | chomwitt joins (~chomwitt@2a02:587:dc0d:4a00:4e3c:ad56:fffa:225d) |
| 2022-07-11 20:22:39 | × | chomwitt quits (~chomwitt@2a02:587:dc0d:4a00:4e3c:ad56:fffa:225d) (Ping timeout: 276 seconds) |
| 2022-07-11 20:53:37 | → | chomwitt joins (~chomwitt@2a02:587:dc0d:4a00:b231:296e:3336:4e6e) |
| 2022-07-11 21:09:27 | × | chomwitt quits (~chomwitt@2a02:587:dc0d:4a00:b231:296e:3336:4e6e) (Ping timeout: 276 seconds) |
| 2022-07-11 21:09:37 | → | wusticality joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-11 21:15:58 | <wusticality> | Hey folks, I've been trying to find a reliable way to swap the Windows and Alt keys in XMonad (in gnome, I use tweaks select the "Left Win as Meta key" option). I've tried using xmodmap (see here: https://gist.github.com/wusticality/c0fc6b8c92bbadf52ad6e833be63c396) to get around this, and that works, temporarily, but within a minute or two, |
| 2022-07-11 21:15:58 | <wusticality> | certain applications wipe my xmodmap settings, breaking my keybindings all over again. I tried to resolve this by running it in a loop forever on startup (aka, something like this: [ -f "$HOME/.Xmodmap" ] && sleep 4 && while true; do xmodmap "$HOME/.Xmodmap"; sleep 1; done &), but that causes other problems. Is there some way to swap the Windows |
| 2022-07-11 21:15:59 | <wusticality> | and Alt keys when using XMonad that's reliable? Thanks very much in advance, this has me totally blocked. |
| 2022-07-11 21:21:30 | <geekosaur> | what are these "certain applications"? |
| 2022-07-11 21:22:49 | <geekosaur> | also technically xmodmap is obsolete and Xkb should be used. |
| 2022-07-11 21:24:01 | <geekosaur> | "Alt is swapped with Super/Win" is one of the provided Xkb options, but configuring Xkb manually is somewhat annoying |
| 2022-07-11 21:24:36 | <wusticality> | oh, xmodmap is deprecated? |
| 2022-07-11 21:25:16 | <wusticality> | honestly, I just need something that works |
| 2022-07-11 21:25:23 | <wusticality> | will Xkb work if you run wayland? |
| 2022-07-11 21:25:50 | <geekosaur> | yes, wayland devs got so confused by keyboard configuration that they just imported Xkb as is |
| 2022-07-11 21:26:41 | <wusticality> | hah |
| 2022-07-11 21:26:58 | <wusticality> | I'll look into it right away - I assume you can have some text-based config that's loaded on startup |
| 2022-07-11 21:27:34 | <geekosaur> | probably you want the setxkbmap command, rather than trying to build a new config for xkbcomp |
| 2022-07-11 21:30:12 | <wusticality> | ok, will take a look :) |
| 2022-07-11 21:31:41 | <liskin> | wusticality: take a look at man xkeyboard-config |
| 2022-07-11 21:31:49 | <geekosaur> | setxkbmap -option altwin:swap_alt_win, looks like |
| 2022-07-11 21:32:29 | <geekosaur> | which shouldleave the rest of the keyboard alone instead of selecting a different layout |
| 2022-07-11 21:32:29 | <liskin> | Yeah, and you can put that in /etc/default/keyboard or wherever your distro puts it |
| 2022-07-11 21:34:10 | <wusticality> | I wonder if that option swaps both alt / win keys |
| 2022-07-11 21:34:15 | <wusticality> | I need them swapped on both sides |
| 2022-07-11 21:38:27 | <geekosaur> | I just checked with mate's keyboard settings and it looks like it's swapped on both sides |
| 2022-07-11 21:38:44 | <geekosaur> | (can't be 100% certain as my right alt is actually a compose key) |
| 2022-07-11 21:39:14 | <wusticality> | is it possible to rebind individual keys with that program ala xmodmap? |
| 2022-07-11 21:39:29 | <wusticality> | gotta say though, xmodmap constantly forgets my settings, it's rough |
| 2022-07-11 21:39:34 | <geekosaur> | for individual keys you would need to resort to xkbcomp |
| 2022-07-11 21:39:56 | <geekosaur> | setxkbmap can only use certain prepackaged configurations |
| 2022-07-11 21:40:45 | <geekosaur> | that said, using xkbcomp you can remap every key on the keyboard including some xmodmap can't touch (like which key, if any, can immediately shut down the server) |
| 2022-07-11 21:41:07 | <wusticality> | is this something you execute in your .profile or something? aka, is this setting persistent for a session? |
| 2022-07-11 21:41:13 | <geekosaur> | (default is control-alt-backspace, if you're wondering, but it's disabled by default) |
| 2022-07-11 21:41:58 | <geekosaur> | you would need to rerun it at the start of every session, but .profile is not typically run by X11 sessions; you'd run it with spawnOnce in your xmonad startupHook |
| 2022-07-11 21:42:17 | <wusticality> | oh ok |
| 2022-07-11 21:42:31 | <wusticality> | this is an absolute lifesaver if it works out |
| 2022-07-11 21:45:26 | <wusticality> | hoping it doesn't lose it's state the way xmodmap does |
| 2022-07-11 21:46:01 | <geekosaur> | you never did way which app was causing you trouble |
| 2022-07-11 21:46:30 | <geekosaur> | if it's (say) a kde app that launches the kde setting manager in the background then you may have to use the kde keyboard configuration dialog to change it |
| 2022-07-11 21:47:01 | × | Ocelot quits (~ocelot@50-78-208-189-static.hfc.comcastbusiness.net) (Remote host closed the connection) |
| 2022-07-11 21:47:38 | <wusticality> | Honestly, I'm not sure |
| 2022-07-11 21:48:03 | <wusticality> | I'm using Signal, Slack, Discord, JetBrains apps, Emacs, Alacritty, Chrome, etc. |
| 2022-07-11 21:48:14 | <wusticality> | without fail though, every few minutes, my xmodmap settings disappear |
| 2022-07-11 21:52:54 | kaskal- | is now known as kaskal |
| 2022-07-11 22:21:44 | <liskin> | xkbcomp isn't really necessary, you can define your own xkb options and then use them in setxkbmap |
| 2022-07-11 22:22:16 | <liskin> | although you'll be writing the same language xkbcomp accepts so probably not that much of a difference really :-) |
| 2022-07-11 22:31:59 | <wusticality> | as long as it's data-driven ya know |
| 2022-07-11 23:09:15 | <wusticality> | this is working, thanks so much folks <3 |
| 2022-07-11 23:09:21 | × | wusticality quits (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) (Quit: Client closed) |
| 2022-07-11 23:51:59 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::909a) |
| 2022-07-12 00:16:19 | × | Solitary quits (~Solitary@user/solitary) (Ping timeout: 256 seconds) |
| 2022-07-12 00:27:20 | → | Solitary joins (~Solitary@user/solitary) |
| 2022-07-12 00:41:33 | × | jaklt[m] quits (~jaklttchn@2001:470:69fc:105::a42) (Quit: Client limit exceeded: 20000) |
| 2022-07-12 00:41:33 | × | Solitary quits (~Solitary@user/solitary) (Ping timeout: 260 seconds) |
| 2022-07-12 00:44:03 | × | liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: Client limit exceeded: 20000) |
| 2022-07-12 00:56:21 | → | Solitary joins (~Solitary@user/solitary) |
| 2022-07-12 00:57:52 | → | wusticality joins (~wusticali@c-67-161-204-49.hsd1.co.comcast.net) |
| 2022-07-12 01:00:30 | × | Solitary quits (~Solitary@user/solitary) (Ping timeout: 240 seconds) |
| 2022-07-12 01:03:18 | <wusticality> | Hey folks, I was taking that `spawnOnce "setxkbmap -option altwin:swap_alt_win"` approach to fixing my issues with swapping the windows / alt keys and it worked well (I used to use xmodmap). However, I seem to be running into the same issue where eventually, the keybindings are reversed. Any ideas would could be going wrong here? Here's the |
| 2022-07-12 01:03:19 | <wusticality> | relevant part of my config: https://gist.github.com/wusticality/480a62377b988ca5066f576413c95371 |
| 2022-07-12 01:03:30 | <wusticality> | specifically, line 86 |
| 2022-07-12 01:03:36 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 2022-07-12 01:03:48 | → | jaklt[m] joins (~jaklttchn@2001:470:69fc:105::a42) |
| 2022-07-12 01:04:46 | × | Yehoshua quits (~yehoshua@2001:470:69fc:105::1:593f) (Quit: Client limit exceeded: 20000) |
| 2022-07-12 01:13:18 | <geekosaur> | as I said earlier, look for a program starting some kind of settings daemon (`ps -fu$USER | grep setting` should work) and then use the corresponding (probably gnome or kde) keyboard configurator to make the same change |
| 2022-07-12 01:13:19 | → | Yehoshua joins (~yehoshua@2001:470:69fc:105::1:593f) |
| 2022-07-12 01:14:12 | <geekosaur> | unfortunately there may not otherwise be a lot to be done about it, especially since the program is apparently ignoring the Xkb settings on the root window that setxkbmap will have registered |
| 2022-07-12 01:17:32 | <wusticality> | I got around it by changing every single program to use windows as alt, but unfortunatly it won't work properly for jetbrains stuff :( |
| 2022-07-12 01:18:45 | → | pjaml[m] joins (~pjamlmatr@2001:470:69fc:105::2:41c4) |
| 2022-07-12 01:22:52 | <geekosaur> | ugly hack might be to change the spawnOnce to spawn and hit mod-q (I guess alt-q for you) when it happens, but ick |
| 2022-07-12 01:27:57 | <wusticality> | Wish there was a way to override this in xmonad itself |
| 2022-07-12 01:28:22 | → | Solitary joins (~Solitary@user/solitary) |
| 2022-07-12 01:28:33 | <geekosaur> | sadly keybindings are not part of xmonad's purview |
| 2022-07-12 01:28:52 | <wusticality> | does setxkbmap spawn a process, or just change some setting? |
| 2022-07-12 01:28:53 | <geekosaur> | you might be interested in kmonad, although you'll probably have to fight the same problem anyway |
| 2022-07-12 01:29:02 | <wusticality> | aka, do I need to kill it first before calling spawn |
| 2022-07-12 01:29:03 | <geekosaur> | it just tweaks a server setting |
| 2022-07-12 01:29:13 | → | tjmciver joins (~tjmciver@cpe-172-101-32-70.maine.res.rr.com) |
| 2022-07-12 01:29:55 | <tjmciver> | Hi. Anyone running xmonad using nix/nixos? I'm having some trouble with it trying to upgrade nixos to 22.05. At least I think it's an xmonad issue. |
| 2022-07-12 01:31:07 | <geekosaur> | (kmonad manages keyboards the same way xmonad manages windows) |
| 2022-07-12 01:33:10 | <wusticality> | unrelated to xmonad? |
| 2022-07-12 01:33:38 | <geekosaur> | unrelated aside from using a similar configuration style |
| 2022-07-12 01:34:43 | <geekosaur> | there's a #kmonad channel although it's small compared to this one |
| 2022-07-12 01:36:10 | × | Solitary quits (~Solitary@user/solitary) (Ping timeout: 240 seconds) |
| 2022-07-12 01:41:52 | → | Solitary joins (~Solitary@user/solitary) |
| 2022-07-12 01:52:52 | Hash | is now known as stoned |
| 2022-07-12 01:53:27 | → | steve__ joins (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-07-12 02:03:59 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds) |
| 2022-07-12 02:22:49 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2022-07-12 02:28:54 | × | td_ quits (~td@muedsl-82-207-238-180.citykom.de) (Ping timeout: 276 seconds) |
| 2022-07-12 02:30:15 | → | td_ joins (~td@94.134.91.223) |
| 2022-07-12 02:43:57 | × | ectospasm quits (~ectospasm@user/ectospasm) (Quit: WeeChat 3.5) |
| 2022-07-12 02:44:55 | → | ectospasm joins (~ectospasm@user/ectospasm) |
| 2022-07-12 02:54:21 | → | qther joins (~qther@165.225.230.105) |
| 2022-07-12 03:02:13 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds) |
All times are in UTC.