| 2023-09-01 00:01:17 +0200 | <mml> | a similar issue arises if I change font size in other applications (gvim, e.g.)... vim tries to shrink or grow its window, either drawing text i can't see or wasting a bunch of the screen space allotted to it by xmonad. I usually fix this by launching a terminal and exiting it immediately with ^D. works fine but always feels like i should have a better answer. this is for a non-floating window. |
| 2023-09-01 00:04:46 +0200 | <geekosaur> | this sounds like stuff is not drawing properly for some reason. we don't control what an app draws in its own window, so there isn't a lot to be done about it unless mod-n somehow helps |
| 2023-09-01 00:04:56 +0200 | <geekosaur> | which is still a hack |
| 2023-09-01 00:10:07 +0200 | <mml> | i think what both of these programs have in common is that they both specify geometry in characters... quoting from X(7): "The WIDTH and HEIGHT parts of the geometry specification are usually measured in either pixels or characters, depending on the application." |
| 2023-09-01 00:10:38 +0200 | <mml> | i don't know enough about X to know the exact implications of this |
| 2023-09-01 00:23:04 +0200 | <geekosaur> | it's less about X than about the toolkit they're using |
| 2023-09-01 00:24:36 +0200 | <geekosaur> | if it's in characters then it'll usually be exposed to the window manager as an aspect ratio, but we don't do anything with it unless you use https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Layout-LayoutHints.html |
| 2023-09-01 00:25:44 +0200 | <geekosaur> | and even then we don't auto-resize windows especially if they are tiled; some programs/toolkits ignore the part of the WM spec that says that the WM has the last word on window placement and size and expect the WM to automatically obey changes to size hints |
| 2023-09-01 00:25:57 +0200 | <geekosaur> | (they're called hints for a reason) |
| 2023-09-01 04:21:19 +0200 | td_ | (~td@i53870906.versanet.de) (Ping timeout: 255 seconds) |
| 2023-09-01 04:23:05 +0200 | td_ | (~td@i5387091C.versanet.de) |
| 2023-09-01 04:35:28 +0200 | Lears | (~Leary]@user/Leary/x-0910699) |
| 2023-09-01 04:37:32 +0200 | [Leary] | (~Leary]@user/Leary/x-0910699) (Ping timeout: 248 seconds) |
| 2023-09-01 06:09:47 +0200 | exordiri | (~ex@user/exordiri) (Ping timeout: 250 seconds) |
| 2023-09-01 08:18:10 +0200 | vanvik5 | (~vanvik@78.156.11.181) |
| 2023-09-01 08:21:33 +0200 | hrberg_ | (~quassel@171.79-160-161.customer.lyse.net) |
| 2023-09-01 08:25:54 +0200 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (*.net *.split) |
| 2023-09-01 08:25:54 +0200 | vanvik | (~vanvik@78.156.11.181) (*.net *.split) |
| 2023-09-01 08:25:54 +0200 | vanvik5 | vanvik |
| 2023-09-01 09:40:58 +0200 | Nixkernal | (~Nixkernal@119.4.193.178.dynamic.wline.res.cust.swisscom.ch) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-09-01 09:42:30 +0200 | Nixkernal | (~Nixkernal@119.4.193.178.dynamic.wline.res.cust.swisscom.ch) |
| 2023-09-01 09:46:32 +0200 | cfricke | (~cfricke@user/cfricke) |
| 2023-09-01 10:02:32 +0200 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 240 seconds) |
| 2023-09-01 10:20:21 +0200 | ft | (~ft@p508db658.dip0.t-ipconnect.de) (Quit: leaving) |
| 2023-09-01 10:28:33 +0200 | cfricke | (~cfricke@user/cfricke) |
| 2023-09-01 10:39:05 +0200 | justache | reddit-bot |
| 2023-09-01 10:39:12 +0200 | reddit-bot | justache |
| 2023-09-01 11:24:08 +0200 | patrl | (~patrl@user/patrl) |
| 2023-09-01 11:30:42 +0200 | patrl | (~patrl@user/patrl) (Quit: WeeChat 3.8) |
| 2023-09-01 12:07:57 +0200 | patrl | (~patrl@user/patrl) |
| 2023-09-01 13:21:35 +0200 | patrl | (~patrl@user/patrl) (Quit: WeeChat 3.8) |
| 2023-09-01 13:46:20 +0200 | catern | (sid604849@id-604849.lymington.irccloud.com) |
| 2023-09-01 13:47:35 +0200 | <catern> | hi #xmonad, is there a package to support "switch to the window to the left/right/up/down of the currently active one"? and if there is such a package, does it further support switching between windows on different desktops in this positional way? |
| 2023-09-01 13:49:29 +0200 | <Lears> | X.A.Navigation2D |
| 2023-09-01 13:50:26 +0200 | <Lears> | (yes) |
| 2023-09-01 13:51:26 +0200 | <catern> | neato |
| 2023-09-01 16:48:16 +0200 | ft | (~ft@p508db658.dip0.t-ipconnect.de) |
| 2023-09-01 17:01:37 +0200 | de-vri-es | (~de-vri-es@2a01:7c8:aab4:33e::1) (Quit: Bathrobe!) |
| 2023-09-01 17:03:45 +0200 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 4.0.4) |
| 2023-09-01 17:27:01 +0200 | Lears | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2023-09-01 17:27:15 +0200 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2023-09-01 17:28:08 +0200 | <haskellbridge> | <yoggurt> Looking to know how Xmonad users get battery warning? probably not a xmonad specific solution but I'm looking for a good fit. I've damaged batteries before from letting it go to 0 while using xmonad |
| 2023-09-01 17:30:23 +0200 | de-vri-es | (~de-vri-es@voyager.de-vri.es) |
| 2023-09-01 17:36:40 +0200 | de-vri-es | (~de-vri-es@voyager.de-vri.es) (Quit: Bathrobe!) |
| 2023-09-01 17:36:52 +0200 | de-vri-es | (~de-vri-es@voyager.de-vri.es) |
| 2023-09-01 17:37:19 +0200 | de-vri-es | (~de-vri-es@voyager.de-vri.es) (Client Quit) |
| 2023-09-01 17:37:31 +0200 | de-vri-es | (~de-vri-es@voyager.de-vri.es) |
| 2023-09-01 18:05:58 +0200 | <deepy> | I have battery details in xmobar |
| 2023-09-01 18:06:36 +0200 | <geekosaur> | but does it issue warnings? or auto suspend on critical? |
| 2023-09-01 18:07:13 +0200 | <geekosaur> | I think there are scripts which monitor ACPI and use notification API; might check the arch wiki, it's good for stuff like that |
| 2023-09-01 18:08:35 +0200 | <geekosaur> | I saw a script that notifies via zenity, which avoids dbus |
| 2023-09-01 18:09:52 +0200 | <geekosaur> | oh, here's a bunch of them that use various notification methods https://github.com/topics/battery-monitor?l=shell |
| 2023-09-01 18:10:31 +0200 | <geekosaur> | (I'm using xmonad with MATE so mate-power-manager does all the work) |
| 2023-09-01 18:29:53 +0200 | <haskellbridge> | <yoggurt> looking into these but they have shell install steps and such which make it not so friendly to use in NixOS :/ |
| 2023-09-01 19:04:12 +0200 | <liskin> | upower takes action automatically |
| 2023-09-01 19:04:38 +0200 | <liskin> | All you need is to have it installed and have something issue at least one dbus call to it |
| 2023-09-01 19:04:49 +0200 | <liskin> | Which is completely moronic, if you ask me |
| 2023-09-01 19:06:59 +0200 | <haskellbridge> | <yoggurt> I have it installed.. wdym by take action? does it send warning notifications? |
| 2023-09-01 20:49:26 +0200 | Natch | (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) (Read error: Connection reset by peer) |
| 2023-09-01 20:54:10 +0200 | Natch | (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) |
| 2023-09-01 21:32:39 +0200 | tremon | (~tremon@83.80.159.219) |
| 2023-09-01 21:53:02 +0200 | immibis | (~quassel@2a01:4f9:4a:4caf::2) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2023-09-01 21:54:58 +0200 | immibis | (~quassel@2a01:4f9:4a:4caf::2) |
| 2023-09-01 22:33:36 +0200 | dsal | (sid13060@id-13060.lymington.irccloud.com) (Server closed connection) |
| 2023-09-01 22:33:49 +0200 | dsal | (sid13060@id-13060.lymington.irccloud.com) |
| 2023-09-01 22:58:26 +0200 | <liskin> | Sleep/shutdown. |
| 2023-09-01 22:58:38 +0200 | <liskin> | Notifications maybe, but probably not. |
| 2023-09-01 23:44:34 +0200 | tv | (~tv@user/tv) (Ping timeout: 255 seconds) |