Logs: liberachat/#xmonad
| 2021-12-23 09:32:19 | <Drishal[m]> | any hints to correct the way gaps are done on xmonad/xmobar? |
| 2021-12-23 09:36:40 | <Solid> | didn't you say you fixed it? |
| 2021-12-23 09:50:58 | <Drishal[m]> | <Solid> "didn't you say you fixed it?" <- when? 🤔 |
| 2021-12-23 09:51:16 | <Drishal[m]> | seems after the latest git update things got kinda messed up |
| 2021-12-23 09:51:29 | → | Guest64 joins (~Guest64@2409:4064:212:6687:989d:250b:25ac:3e4d) |
| 2021-12-23 09:51:47 | <Solid> | > Drishal[m]: however this gets fixed if I use `setLayout $ Layout myLayout` corresponding keybind |
| 2021-12-23 09:51:48 | <lambdabot> | <hint>:1:57: error: |
| 2021-12-23 09:51:48 | <lambdabot> | parse error on input ‘$’ |
| 2021-12-23 09:51:48 | <lambdabot> | Perhaps you intended to use TemplateHaskell |
| 2021-12-23 09:51:50 | <Solid> | there |
| 2021-12-23 09:52:28 | <Drishal[m]> | Solid: nah what I mean to say is I have to press a keybind |
| 2021-12-23 09:52:35 | <Guest64> | hey i need some help |
| 2021-12-23 09:52:39 | <Drishal[m]> | so that the layout is set correctly |
| 2021-12-23 09:52:48 | <Drishal[m]> | else there is a bit too much help |
| 2021-12-23 09:52:53 | <Drishal[m]> | s/help/gaps/ |
| 2021-12-23 09:52:54 | <Guest64> | can anyone tell me how to use xmonad prompt like dmenu |
| 2021-12-23 09:53:23 | <Drishal[m]> | I wonder if something messy is going on with the latest xmonad config |
| 2021-12-23 09:54:24 | <Guest64> | seen the source code |
| 2021-12-23 10:03:01 | × | Guest64 quits (~Guest64@2409:4064:212:6687:989d:250b:25ac:3e4d) (Quit: Client closed) |
| 2021-12-23 10:04:17 | <Solid> | I'm not sure I follow; do you need to do this _every time_? |
| 2021-12-23 10:04:26 | <Solid> | Or did you simply hit M-q and you need to refresh the layouts? |
| 2021-12-23 10:11:57 | <Drishal[m]> | yes |
| 2021-12-23 10:11:57 | × | mvk quits (~mvk@2607:fea8:5cdd:f000::917a) (Ping timeout: 240 seconds) |
| 2021-12-23 10:12:06 | <Drishal[m]> | M-S-m to be exact |
| 2021-12-23 10:30:27 | <Solid> | I asked two questions, please don't answer "yes" ;) |
| 2021-12-23 10:31:20 | <Drishal[m]> | <Solid> "I'm not sure I follow; do you..." <- yes I need to do this everytime |
| 2021-12-23 10:37:18 | <Drishal[m]> | is this the correct way to reset the layouts? |
| 2021-12-23 10:37:18 | <Drishal[m]> | ```haskell |
| 2021-12-23 10:37:18 | <Drishal[m]> | , ("M-S-m", setLayout $ Layout myLayout) |
| 2021-12-23 10:37:18 | <Drishal[m]> | ``` |
| 2021-12-23 10:40:50 | <Solid> | should be fine (if you have your whole config handy you can also just do `setLayout $ layoutHook myConf`) |
| 2021-12-23 10:41:11 | <Solid> | but this should just reset some state stored in the layouts; after restarting you should not have to do this again |
| 2021-12-23 11:03:45 | <Drishal[m]> | > <@drishal:matrix.org> ```haskell... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/e512c5c78f1a89ff32b51f63301d8192d7269c28) |
| 2021-12-23 11:03:46 | <lambdabot> | <hint>:1:1: error: parse error on input ‘<@’ |
| 2021-12-23 11:04:19 | <Drishal[m]> | now theere are no random changing of window spacing when pressng M-S-m |
| 2021-12-23 11:05:44 | <Drishal[m]> | also is there any way to restart xmobar along with xmonad 0.17? |
| 2021-12-23 11:06:16 | <Drishal[m]> | currently xmobar is done this way... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/549975c175df27bbe3684d8412cb9f5332ba2433) |
| 2021-12-23 11:06:42 | <Drishal[m]> | trying to restart xmonad does not seem to restart xmobar |
| 2021-12-23 11:07:03 | <Solid> | `withEasySB` takes care of al of the restarting |
| 2021-12-23 11:08:03 | <Drishal[m]> | Solid: nope does not for me |
| 2021-12-23 11:08:46 | <Solid> | geekosaur: https://libera.ems.host/_matrix/media/r0/download/libera.chat/e512c5c78f1a89ff32b51f63301d8192d7269c28 seems to suggest that applying avoidStruts _after_ spacing is sometimes desirable (which is the opposite of what #666 says); what am I missing here? |
| 2021-12-23 11:11:41 | <Drishal[m]> | Solid: Variable not in scope: |
| 2021-12-23 11:11:53 | <Drishal[m]> | myLayout = renamed [CutWordsLeft 1] ( avoidStruts_after_spacing ( smartBorders ( spacingWithEdge 8 ( tiled ||| simplestFloat )))) ||| smartBorders Ful |
| 2021-12-23 11:12:16 | <Solid> | that message was not meant for you ;) |
| 2021-12-23 11:12:29 | <Drishal[m]> | aah ok |
| 2021-12-23 11:12:46 | <Drishal[m]> | xD |
| 2021-12-23 11:13:47 | <Solid> | Drishal[m]: afaik when you provide a haskell config as an input to xmobar, it compiles itself with that and then execv's a new instance |
| 2021-12-23 11:14:03 | <Solid> | since restarting works by keeping track of xmobar's PID we won't be able to find that |
| 2021-12-23 11:14:31 | <Drishal[m]> | so basically the way xmobar is handled is changed in 0.17 to some extent? |
| 2021-12-23 11:14:51 | <Solid> | well, property-based logging didn't restart xmobar at all in 0.16 |
| 2021-12-23 11:15:06 | <Solid> | it's just that we're now pushing this more over pipes (which are error-prone) |
| 2021-12-23 11:15:22 | <Solid> | if you want to use a Haskell-based config for xmobar I suggest you directly compile xmobar with that config |
| 2021-12-23 11:15:26 | × | lambdabot quits (~lambdabot@haskell/bot/lambdabot) (Quit: let me try something) |
| 2021-12-23 11:15:33 | <Solid> | that way there's no extra execv |
| 2021-12-23 11:15:42 | <Drishal[m]> | cause if I launched xmobar with xmproc in the previous builds it would restart without any issues |
| 2021-12-23 11:16:14 | <Drishal[m]> | now I have to start xmobar withEasySB instead 🤔 |
| 2021-12-23 11:16:34 | <Solid> | you don't _have_ to |
| 2021-12-23 11:17:40 | <Solid> | you can also use [statusBarPipe](https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Hooks-StatusBar.html#v:statusBarPipe) instead of statusBarProp |
| 2021-12-23 11:17:54 | <Solid> | which uses the old pipe-based way to talk to xmobar |
| 2021-12-23 11:17:56 | <Solid> | it's just discouraged |
| 2021-12-23 11:18:05 | <Solid> | (and so not heavily mentioned in the docs) |
| 2021-12-23 11:18:40 | → | lambdabot joins (~lambdabot@haskell/bot/lambdabot) |
| 2021-12-23 11:24:41 | × | lambdabot quits (~lambdabot@haskell/bot/lambdabot) (Quit: tum tee tum) |
| 2021-12-23 11:25:38 | → | lambdabot joins (~lambdabot@haskell/bot/lambdabot) |
| 2021-12-23 11:27:53 | × | lambdabot quits (~lambdabot@haskell/bot/lambdabot) (Client Quit) |
| 2021-12-23 11:29:03 | → | lambdabot joins (~lambdabot@haskell/bot/lambdabot) |
| 2021-12-23 11:29:56 | × | lambdabot quits (~lambdabot@haskell/bot/lambdabot) (Client Quit) |
| 2021-12-23 11:30:56 | → | lambdabot joins (~lambdabot@haskell/bot/lambdabot) |
| 2021-12-23 11:32:46 | <Drishal[m]> | <Solid> "you can also use [statusBarPipe]..." <- hmm ok 👀 |
| 2021-12-23 12:47:44 | <geekosaur> | Solid, funny, as I read that they were having problems and fixed them by moving the avoidStruts outside the spacing |
| 2021-12-23 12:48:09 | <geekosaur> | that said, the variants of spacing that don't also add screen spacing *might* work in semi-sensible ways |
| 2021-12-23 12:49:31 | <Solid> | geekosaur: indeed they did; but "outside" is "after", right? |
| 2021-12-23 12:49:56 | <geekosaur> | I worded "after" in terms of the $ $ $ chain |
| 2021-12-23 12:50:08 | <geekosaur> | not the internals that most folks won't know about |
| 2021-12-23 12:50:16 | <Solid> | oh |
| 2021-12-23 12:51:00 | <geekosaur> | suppose that could stand some clarification |
| 2021-12-23 12:52:25 | <geekosaur> | (but I think it's still true even there as the constructors get traversed in that order, so avoidStruts should get the unmodified screen rectangle / be "before" anything that reduces the rectangle) |
| 2021-12-23 12:57:25 | × | Benzi-Junior quits (~BenziJuni@88-149-66-61.du.xdsl.is) (Ping timeout: 240 seconds) |
| 2021-12-23 13:02:21 | → | p_hil joins (~p_hil@2a02:810a:8900:123b:8688:8217:388a:3994) |
| 2021-12-23 13:07:54 | × | p_hil quits (~p_hil@2a02:810a:8900:123b:8688:8217:388a:3994) (Quit: Client closed) |
| 2021-12-23 13:55:02 | → | Benzi-Junior joins (~BenziJuni@dsl-149-66-61.hive.is) |
| 2021-12-23 14:12:12 | → | ebray187 joins (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) |
| 2021-12-23 14:28:47 | → | ebray joins (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) |
| 2021-12-23 14:28:53 | × | ebray187 quits (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) (Read error: No route to host) |
| 2021-12-23 14:51:19 | × | ebray quits (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) (Read error: No route to host) |
| 2021-12-23 14:51:43 | → | ebray187 joins (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) |
| 2021-12-23 14:54:15 | × | benin quits (~benin@183.82.27.57) (Ping timeout: 268 seconds) |
| 2021-12-23 15:02:42 | → | benin joins (~benin@183.82.27.57) |
| 2021-12-23 15:06:58 | × | ebray187 quits (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) (Read error: No route to host) |
| 2021-12-23 15:07:37 | → | ebray187 joins (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) |
| 2021-12-23 15:26:20 | × | ebray187 quits (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) (Read error: Connection reset by peer) |
| 2021-12-23 15:47:55 | → | dschrempf joins (~dominik@070-207.dynamic.dsl.fonira.net) |
| 2021-12-23 15:48:54 | × | Forkk quits (~forkk@li926-228.members.linode.com) (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2021-12-23 15:55:42 | → | Forkk joins (~forkk@li926-228.members.linode.com) |
| 2021-12-23 16:03:18 | × | dschrempf quits (~dominik@070-207.dynamic.dsl.fonira.net) (Ping timeout: 268 seconds) |
| 2021-12-23 17:03:37 | → | ebray187 joins (~ebray187@2800:150:129:17c4:224:1dff:fed5:599e) |
| 2021-12-23 18:10:29 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2021-12-23 18:13:00 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2021-12-23 18:14:43 | × | humky quits (~humky@user/humky) (Quit: Leaving) |
| 2021-12-23 18:48:20 | → | cfricke joins (~cfricke@user/cfricke) |
All times are in UTC.