Logs: liberachat/#xmonad
| 2021-11-16 13:55:25 | → | mariari joins (~mariari@user/mariari) |
| 2021-11-16 13:55:46 | <Solid> | classic :) |
| 2021-11-16 14:14:40 | → | benin joins (~benin@183.82.27.20) |
| 2021-11-16 14:28:41 | → | catman_ joins (~catman@user/catman) |
| 2021-11-16 14:29:08 | × | catman quits (~catman@user/catman) (Killed (lead.libera.chat (Nickname regained by services))) |
| 2021-11-16 14:29:08 | catman_ | is now known as catman |
| 2021-11-16 14:33:07 | → | cfricke joins (~cfricke@user/cfricke) |
| 2021-11-16 15:16:17 | → | fabfianda[m] joins (~fabfianda@2001:470:69fc:105::6db) |
| 2021-11-16 15:18:59 | × | srk quits (~sorki@user/srk) (Quit: ZNC 1.8.1 - https://znc.in) |
| 2021-11-16 15:19:18 | → | srk joins (~sorki@user/srk) |
| 2021-11-16 15:33:50 | → | qbt joins (~qbt@user/edun) |
| 2021-11-16 16:08:00 | × | benin quits (~benin@183.82.27.20) (Quit: The Lounge - https://thelounge.chat) |
| 2021-11-16 16:18:33 | → | obimod joins (~obimod@gateway/vpn/pia/obimod) |
| 2021-11-16 16:20:23 | <etrigan63[m]> | <Arcanus[m]> "this will be my next task, if..." <- All you have to do is define the monitor parameter in the polybar config.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/d43e064dbc4292a3223832b3273877357be96bd4) |
| 2021-11-16 16:21:18 | <etrigan63[m]> | Define a second bar by giving it a different name:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/cfea147898aae1519413019916f8e4a19018e83f) |
| 2021-11-16 16:22:31 | <etrigan63[m]> | Then modify the launch script to launch both bars:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/28030f30eaa2dbb994df4a553b28e0ff624c33be) |
| 2021-11-16 16:24:59 | <etrigan63[m]> | I too was struggling with workspaces and monitors and decided that monitor specific layouts was the way to go. That way whatever workspace is shown on a monitor is laid out correctly for that monitor. |
| 2021-11-16 16:44:18 | × | dschrempf quits (~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 265 seconds) |
| 2021-11-16 17:05:27 | → | dschrempf joins (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-11-16 17:17:44 | × | qbt quits (~qbt@user/edun) (Quit: Leaving.) |
| 2021-11-16 17:24:27 | → | desantra joins (~skykanin@user/skykanin) |
| 2021-11-16 17:24:34 | → | SenranKaguya joins (~weechat@c-73-15-19-170.hsd1.ca.comcast.net) |
| 2021-11-16 17:28:14 | <desantra> | Any xmonad + polybar users who have proper fullscreen layout working willing to share their config? Been struggling with this for 2w and still haven't been able to fix it. Can't get the fullscreen layout to cover the bar. This is my current config: https://github.com/skykanin/dotfiles/blob/xmonad-staging/dots/xmonad/xmonad.hs |
| 2021-11-16 17:29:41 | <desantra> | I've tried this on two different computers with the same result so I'm pretty sure it's something about the config |
| 2021-11-16 17:30:35 | → | qbt joins (~qbt@user/edun) |
| 2021-11-16 17:47:54 | → | bsjd joins (~user@2a02:a020:57:4e3:d312:cf34:976c:e971) |
| 2021-11-16 17:53:04 | × | dschrempf quits (~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 268 seconds) |
| 2021-11-16 17:55:23 | → | seschwar joins (~seschwar@user/seschwar) |
| 2021-11-16 17:57:01 | × | cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.3) |
| 2021-11-16 18:06:12 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2021-11-16 18:06:52 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2021-11-16 18:20:06 | × | thaumavorio_ quits (~thaumavor@thaumavor.io) (Ping timeout: 260 seconds) |
| 2021-11-16 18:24:53 | <etrigan63[m]> | https://github.com/etrigan63/XMonad-Dotfiles.git |
| 2021-11-16 18:26:05 | → | thaumavorio joins (~thaumavor@thaumavor.io) |
| 2021-11-16 18:40:06 | → | steve_ joins (~steve@ool-182c2b80.dyn.optonline.net) |
| 2021-11-16 19:03:37 | × | desantra quits (~skykanin@user/skykanin) (Quit: WeeChat 3.3) |
| 2021-11-16 19:12:45 | × | bsjd quits (~user@2a02:a020:57:4e3:d312:cf34:976c:e971) (Remote host closed the connection) |
| 2021-11-16 19:23:19 | → | desantra joins (~skykanin@user/skykanin) |
| 2021-11-16 19:34:56 | → | defjam joins (~eb0t@90.209.246.132) |
| 2021-11-16 20:10:00 | → | mc47 joins (~mc47@xmonad/TheMC47) |
| 2021-11-16 20:33:00 | × | qbt quits (~qbt@user/edun) (Quit: Leaving.) |
| 2021-11-16 20:54:05 | → | banc- joins (banc@gateway/vpn/airvpn/banc) |
| 2021-11-16 20:56:26 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds) |
| 2021-11-16 20:59:59 | × | SenranKaguya quits (~weechat@c-73-15-19-170.hsd1.ca.comcast.net) (Ping timeout: 265 seconds) |
| 2021-11-16 21:02:30 | × | desantra quits (~skykanin@user/skykanin) (Quit: WeeChat 3.3) |
| 2021-11-16 21:16:12 | → | SenranKaguya joins (~weechat@c-73-15-19-170.hsd1.ca.comcast.net) |
| 2021-11-16 22:14:36 | × | mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2021-11-16 22:25:28 | <Arcanus[m]> | > <@etrigan63:matrix.org> All you have to do is define the monitor parameter in the polybar config.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/0cd5498765c7ab25d521aa02f50d57d27d8a7b3b) |
| 2021-11-16 22:25:29 | <lambdabot> | <hint>:1:1: error: parse error on input ‘<@’ |
| 2021-11-16 22:33:00 | <Arcanus[m]> | <desantra> "Any xmonad + polybar users who..." <- wdym? if you press f11 does it cover the bars?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/af9ff9d5f37d160d21787651a20975f9cf72dd51) |
| 2021-11-16 22:34:03 | Arcanus[m] | posted a file: (18KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/fELDDaQapbTDPdAWQXdfscVm/xmonad.hs > |
| 2021-11-16 22:34:25 | <Arcanus[m]> | here's my current config if it will help |
| 2021-11-16 22:35:27 | <Arcanus[m]> | I realize i should probably have just shared my gitlab, but I haven't updated it yet |
| 2021-11-16 22:35:29 | × | seschwar quits (~seschwar@user/seschwar) (Quit: :wq) |
| 2021-11-16 23:00:48 | <Arcanus[m]> | etrigan63 : I'm peeking through your codes and I don't see a specification for per screen ewmh, maybe I'm just missing it, are you able to show the workspaces specific to that screen in it's corresponding polybar? I have 4 separate polybars at the moment, and all i need to do is get the left screen polybar to only show the left screen workspaces, and teh right screen polybar to show the right screen workspaces, I'm pretty sure this needs |
| 2021-11-16 23:00:48 | <Arcanus[m]> | to be specified in the main xmonad.hs and then piped (?) to polybar, and then the polybar config will need to specify that set of info somehow, (ewmh1 ewmh2?) or something like that. I don't know I'm not a programmer. awesomeWM does this out of the box, but I haven't even figured out how to get 2 separate top bars in awesomeWM yet, and don't get me started on the widgets! my awesomeWM is at like 50% config completion vs Xmonad which is at |
| 2021-11-16 23:00:48 | <Arcanus[m]> | 99% |
| 2021-11-16 23:07:06 | <davve> | im using polybar with ewmh |
| 2021-11-16 23:07:19 | <davve> | is desantra around in some form still? |
| 2021-11-16 23:08:34 | <geekosaur> | "per screen ewmh" isn't a thing, per the ewmh spec which assumes workspaces always span all screens and fails to handle window managers like xmonad |
| 2021-11-16 23:14:39 | <Arcanus[m]> | <geekosaur> ""per screen ewmh" isn't a thing,..." <- hmm...is there another module, or way to do what I'm talking about? basically monitor A sending it's information to polybar A and monitor B sending it's workspace information to polybar B to be displayed? |
| 2021-11-16 23:16:12 | <geekosaur> | not via ewmh, since it doesn't have the concept of "per screen". you'd have to feed it via DynamicLogString and either a pipe or dbus or something |
| 2021-11-16 23:17:01 | <geekosaur> | (I'm thinking semi-seriously of making a StatusBar hook for dbus, but it'd have to go into xmonad-extras because of all dbus's extra deps) |
| 2021-11-16 23:17:34 | <etrigan63[m]> | I tried this and there is going to be a way to do it in v0.18 but not right now. This is why I went the route I did. By way of a forked module in my dotfiles above, I am able to assign layouts to the monitors and the windows realign themselves automatically if you flip monitors. |
| 2021-11-16 23:18:46 | <etrigan63[m]> | There is a video in the github demonstrating ther module in action. |
| 2021-11-16 23:19:05 | <Arcanus[m]> | etrigan63[m]: I will have to look through it in more depth then |
| 2021-11-16 23:19:23 | <fizzie> | The root-window-property-based thing can work for multiple bars too, as long as the bar can be told which property to read. |
| 2021-11-16 23:20:04 | <fizzie> | https://xmonad.github.io/xmonad-docs/xmonad-contrib/XMonad-Hooks-StatusBar.html#g:3 has an xmobar example. But no idea which bars can read a property. |
| 2021-11-16 23:20:10 | <etrigan63[m]> | Polybar respects the `xrandr` name of the monitor. |
| 2021-11-16 23:23:23 | <etrigan63[m]> | My only remaining bugaboo is getting `i3lock` (via `xidlehook + betterlockscreen`) to stay above everything. When `polybar` or an app updates, they appear on top of the unlock screen when it unblanks. |
| 2021-11-16 23:24:18 | <fizzie> | (Also, showing an IndependentScreens per-screen workspace list properly involves remapping the screen numbers out of the workspace names, so I imagine that's even more impossible if communicating via the standard EWMH hints.) |
| 2021-11-16 23:25:41 | <geekosaur> | etrigan63[m], I'm becoming more and more convinced that you have some kind of local issue, and not in your config. Possibly some bug in your video driver that's causing it to do updates to windows that should be hidden? |
| 2021-11-16 23:26:23 | <geekosaur> | video driver or gpu driver |
| 2021-11-16 23:27:27 | <geekosaur> | in particular, drawing in a window does not raise it, so how is it ending up "above" the locker window? |
| 2021-11-16 23:31:26 | <Arcanus[m]> | so what I might do then is keep my workspace switcher on one bar on one screen, and put my xwindows indicator on the other screen. it isn't really what I want, but I think I can live with it at least until I have the time to try to figure it out |
| 2021-11-16 23:42:27 | <Arcanus[m]> | thank you all for your time and help btw, it is very much appreciated |
| 2021-11-17 00:02:51 | → | CorinCWStra[m] joins (~cwstramat@2001:470:69fc:105::1:3671) |
| 2021-11-17 00:10:24 | → | SpiderPig joins (~matt@047-132-233-190.res.spectrum.com) |
| 2021-11-17 00:17:30 | <CorinCWStra[m]> | Does anyone have any ideas as to how I might initialize a window to float from the command line? I know the standard manage hooks can work off of Xorg properties, but I don't want all windows of a given application to float, just ones I open up via a particular keybinding. |
| 2021-11-17 00:38:56 | <geekosaur> | you could use ExtensibleState to set a flag in the keybinding and then test the flag using liftX in the manageHook, but it will be a little unreliable because *ix is asynchronous so another window might pop up in the meantime |
| 2021-11-17 00:40:51 | <geekosaur> | or if you can reliably identify the window by _NET_WM_PID (this won't work if the app is always running in the background and spawns new windows on demand) you could use https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Actions-SpawnOn.html#v:spawnAndDo |
| 2021-11-17 00:41:08 | <geekosaur> | (don't forget to add manageSpawn to the manageHook if you do that) |
| 2021-11-17 00:41:36 | <geekosaur> | this does not require 0.17.0, that's just the docs I have up :) |
| 2021-11-17 00:41:38 | <fizzie> | There's a floatNext thing, I think. |
| 2021-11-17 00:41:45 | <fizzie> | https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Hooks-FloatNext.html |
| 2021-11-17 00:41:53 | <fizzie> | A bit racy, but probably works okay in practice. |
| 2021-11-17 00:42:16 | <fizzie> | (Also requires installing the `floatNextHook` in manageHook to work.) |
| 2021-11-17 00:49:28 | <CorinCWStra[m]> | I'll see how floatNext works. |
| 2021-11-17 00:55:32 | <CorinCWStra[m]> | Seems to work! Going to take emacs-everywhere for a spin, but didn't want to disrupt the tiling for a quick open-and-close dialog window. |
| 2021-11-17 00:58:26 | → | mvk joins (~mvk@2607:fea8:5cc3:e900::df92) |
| 2021-11-17 01:16:42 | <CorinCWStra[m]> | Well, this message was written using emacs-everywhere, so I'll call it a success! Many thanks! |
| 2021-11-17 01:37:49 | × | SenranKaguya quits (~weechat@c-73-15-19-170.hsd1.ca.comcast.net) (Ping timeout: 250 seconds) |
| 2021-11-17 02:11:23 | <yuu[m]> | i get a X when the cursor is over the desktop wallpaper for example. how to make that X turn into normal cursor arrow? |
| 2021-11-17 02:13:52 | <geekosaur> | https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Util-Cursor.html |
| 2021-11-17 02:16:15 | <geekosaur> | or use xsetroot before starting xmonad: xsetroot -cursor_name left_ptr |
| 2021-11-17 02:16:27 | <geekosaur> | (or one of the other predefined cursors from the cursor font) |
| 2021-11-17 02:17:17 | <etrigan63[m]> | <geekosaur> "video driver or gpu driver" <- You may be right. I have to double check, but I don’t think this is happening on my laptop which is Intel graphics. |
| 2021-11-17 02:23:03 | <yuu[m]> | geekosaur: thank you! do you know if i can set a custom cursor theme as well? |
| 2021-11-17 02:23:33 | <yuu[m]> | (it does not follow the cursor theme I set in Xresources) |
| 2021-11-17 02:23:44 | <geekosaur> | not easily, I think that requires a gtk-based window manager |
All times are in UTC.