Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→
Page 1 .. 780 781 782 783 784 785 786 787 788 789 790 .. 1850
184,966 events total
2022-08-10 16:50:33 × sogens quits (~sogens@gateway/vpn/pia/sogens) (Ping timeout: 268 seconds)
2022-08-10 16:58:15 <geekosaur> if you're not using XMonad.Hooks.Fade{Inactive,Windows} then xmonad knows exactly nothing about transparency. transparency is normally up to the window itself, since the window manager can't know what opacity the application rendering the window wants
2022-08-10 17:00:51 × sogens2 quits (~sogens@211.30.173.20) (Quit: WeeChat 3.5)
2022-08-10 17:18:19 Jade1 joins (~Jade1@ip-178-201-128-039.um46.pools.vodafone-ip.de)
2022-08-10 17:21:59 <Jade1> Is it normal that when switching workspaces my background flashes for a split second?
2022-08-10 17:21:59 <Jade1> In my compositor I have fading disabled but when quickly switching workspaces I can see my background for short times
2022-08-10 17:22:17 sogens joins (~sogens@211.30.173.20)
2022-08-10 17:23:33 <geekosaur> yes, it's entirely possible you can spot the background between when the old workspace's windows are unmapped and the new one's are mapped
2022-08-10 17:23:45 <geekosaur> compositing actually helps to minimize this
2022-08-10 17:24:51 <geekosaur> @ask Quelklef What's the difference between your WorkspacesIn2D and XMonad.Actions.Plane?
2022-08-10 17:24:51 <lambdabot> Consider it noted.
2022-08-10 17:26:12 <Jade1> geekosaur, so there's no way to make it "cover" it up in order to be 100% covered when just switching workspaces?
2022-08-10 17:26:21 <geekosaur> there is not
2022-08-10 17:26:27 <Jade1> because the flash is really annoying
2022-08-10 17:26:30 <Jade1> ah ok thank you
2022-08-10 17:26:37 <Jade1> I might go back to fading then
2022-08-10 17:26:41 <Jade1> it covers it up well
2022-08-10 17:26:44 <geekosaur> hypothetically we could map the new windows before unmapping the old but that's not what X.O.windows currently does
2022-08-10 17:27:20 <Jade1> ok thanks!
2022-08-10 17:28:28 <geekosaur> (and doing so might alter the stacking order and cause other obscure issues)
2022-08-10 17:28:53 <Jade1> alright
2022-08-10 17:34:55 × EnlightenedUser quits (~Enlighten@ip5f5af2d7.dynamic.kabel-deutschland.de) (Quit: Client closed)
2022-08-10 17:43:18 × Jade1 quits (~Jade1@ip-178-201-128-039.um46.pools.vodafone-ip.de) (Quit: Client closed)
2022-08-10 17:44:23 × ml| quits (~ml|@user/ml/x-5298235) (Ping timeout: 252 seconds)
2022-08-10 17:52:59 × sogens quits (~sogens@211.30.173.20) (Read error: Connection reset by peer)
2022-08-10 17:57:26 sogens joins (~sogens@211.30.173.20)
2022-08-10 17:58:32 <geekosaur> @tell EnlightenedUser for what it's worth I can duplicate it with terminology on my system. I presume that means it's looking for something that it doesn't autostart, that is presumably part of the enlightenment desktop
2022-08-10 17:58:33 <lambdabot> Consider it noted.
2022-08-10 18:01:53 ml| joins (~ml|@user/ml/x-5298235)
2022-08-10 18:06:45 <geekosaur> @tell EnlightenedUser it turns out that it's not using an opacity of 0; it's hanging before it can render anything, which also means the window can't be selected or etc. in particular I saw no shell associated with the window here
2022-08-10 18:06:46 <lambdabot> Consider it noted.
2022-08-10 18:10:18 × dschrempf quits (~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.6)
2022-08-10 18:12:34 × sogens quits (~sogens@211.30.173.20) (Quit: WeeChat 3.5)
2022-08-10 18:13:48 sogens joins (~sogens@211.30.173.20)
2022-08-10 18:26:45 × sogens quits (~sogens@211.30.173.20) (Ping timeout: 268 seconds)
2022-08-10 18:28:02 sogens joins (~sogens@gateway/vpn/pia/sogens)
2022-08-10 18:32:38 × sogens quits (~sogens@gateway/vpn/pia/sogens) (Ping timeout: 244 seconds)
2022-08-10 18:36:07 Quelklef joins (~Quelklef@64.67.70.25.res-cmts.tvh.ptd.net)
2022-08-10 18:37:25 sogens joins (~sogens@211.30.173.20)
2022-08-10 18:40:09 <Quelklef> geekosaur, good question
2022-08-10 18:40:42 <Quelklef> I've never used XMonad.Actions.Plane before
2022-08-10 18:40:53 <Quelklef> I'll try it out
2022-08-10 18:41:03 <geekosaur> keep in mind that I'm not saying "we already have that"; Plane is a huge ungainly hack that very few people trust
2022-08-10 18:41:03 <Quelklef> off the bat, it looks similar except that it doesn't have this workspace-combining feature mine does
2022-08-10 18:41:09 <Quelklef> oh, is it?
2022-08-10 18:43:11 <geekosaur> well, I think the code is small, the *hack* is big 🙂
2022-08-10 18:43:26 <geekosaur> it abuses the StackSet something fierce
2022-08-10 18:43:28 <Quelklef> what's hacky about it? :O
2022-08-10 18:43:30 <Quelklef> ahh
2022-08-10 18:43:49 <Quelklef> well, I don't touch StackSet directly
2022-08-10 18:43:58 <Quelklef> my implementation is on top of Workspaces
2022-08-10 18:44:00 <geekosaur> that already makes it sound better
2022-08-10 18:44:14 <geekosaur> well, Workspace is part of StackSet
2022-08-10 18:44:19 <Quelklef> it's slightly hacky, but in the "your output will be weird if you miss" a step way, not the "your xmonad will break if you do it wrong" way
2022-08-10 18:44:31 <Quelklef> "... if you miss a step"*
2022-08-10 18:44:33 <geekosaur> but forcibly swapping out Stacks is … fragile
2022-08-10 18:45:14 <geekosaur> (a Workspace being the combination of a Layout and a Maybe Stack)
2022-08-10 18:46:01 <Quelklef> to be clear by "on top of workspaces" i mean on top of workspace IDs
2022-08-10 18:46:44 <Quelklef> I call out to stuff like (windows . greedyView)
2022-08-10 18:48:13 <Quelklef> oh, this is interesting
2022-08-10 18:48:27 <Quelklef> so Planes takes your existing set of workspace IDs and fits it onto a 2d grid
2022-08-10 18:48:33 <geekosaur> yes
2022-08-10 18:48:50 <Quelklef> mine requires control of generating the workspace ids
2022-08-10 18:49:19 <geekosaur> so it's closer to something like IndependentScreens?
2022-08-10 18:49:46 <geekosaur> which treats actual workspace tags as <screenid>_<wsid> and gives you wrappers to manipulate each
2022-08-10 18:49:50 <Quelklef> > Utility functions for simulating independent sets of workspaces on each screen (like dwm's workspace model), using internal tags to distinguish workspaces associated with each screen.
2022-08-10 18:49:52 <lambdabot> <hint>:1:51: error: parse error on input ‘of’
2022-08-10 18:49:55 <Quelklef> yes, that sounds right
2022-08-10 18:50:12 <Quelklef> I generate workspaces tags with format "y/x:name"
2022-08-10 18:50:34 <Quelklef> and then expose an Endo PP for rendering them correctly
2022-08-10 18:54:07 <Quelklef> although come to think of it I'm not sure that's really necessary
2022-08-10 18:54:34 <Quelklef> it's a nice default implementation, but I think I could relax the API to give users completely control over workspace IDs if they want it
2022-08-10 18:54:37 alternateved joins (~user@staticline-31-183-149-36.toya.net.pl)
2022-08-10 18:59:24 × sogens quits (~sogens@211.30.173.20) (Ping timeout: 268 seconds)
2022-08-10 19:01:01 sogens joins (~sogens@gateway/vpn/pia/sogens)
2022-08-10 19:15:06 × alternateved quits (~user@staticline-31-183-149-36.toya.net.pl) (Remote host closed the connection)
2022-08-10 19:59:32 × qbt quits (~qbt@user/edun) (Quit: WeeChat 3.5)
2022-08-10 20:07:13 <zim0369[m]1> geekosaur: you've got to help me now
2022-08-10 20:07:23 <zim0369[m]1> I need to fix this.
2022-08-10 20:07:50 <zim0369[m]1> I just checked the same config file that day on my other machine running endeavorOS and xmobar was working fine
2022-08-10 20:08:03 <zim0369[m]1> I replicated the same setup on my main machine
2022-08-10 20:08:23 <zim0369[m]1> i installed xmonad-git and xmonad-contrib-git from aur and then xmobar from pacman
2022-08-10 20:08:54 <zim0369[m]1> but it still won't work on my main machine with a brand new installation
2022-08-10 20:10:17 <geekosaur> I'm not sure how I'm supposed to help you. I can't compare your two installations to see how they differ
2022-08-10 20:17:31 <zim0369[m]1> geekosaur: there must be something we cud do
2022-08-10 20:17:38 <zim0369[m]1> can Solid help?
2022-08-10 20:18:14 <geekosaur> probably not at this point. if you have all your xmonad and xmobar stuff the same then I'd next start comparing environment variables and such
2022-08-10 20:18:55 <zim0369[m]1> what should i look for?
2022-08-10 20:20:50 <geekosaur> initially I'd just compare shell startup files and such. except I seem to recall you decided to mess with /etc/environment on one system (although if it's the one you reinstalled, that won't matter any more)
2022-08-10 20:21:02 <geekosaur> iirc you run fish so you also need to check its special files
2022-08-10 20:21:54 <zim0369[m]1> ill change to bash and see
2022-08-10 20:23:53 <geekosaur> (anything in ~/.config/fish, including fish_variables)
2022-08-10 20:25:21 <geekosaur> fwiw I (like a number of other people here, and indeed on github) keep my master set of dotfiles on github and can easily compare them that way
2022-08-10 20:26:40 <geekosaur> like, if something behaves differently on two of my systems I can git diff both against my dotfiles repo
2022-08-10 20:26:57 <zim0369[m]1> https://github.com/zim0369/dots
2022-08-10 20:27:19 <zim0369[m]1> i changed my shell to bash
2022-08-10 20:27:42 <zim0369[m]1> i just installed endeavorOS a few hours ago
2022-08-10 20:27:45 <zim0369[m]1> still no xmobar
2022-08-10 20:28:09 <zim0369[m]1> wait
2022-08-10 20:28:36 <zim0369[m]1> there's no xmobarrc but xmobar starts just fine from the terminal

All times are in UTC.