Logs: liberachat/#xmonad
| 2023-03-31 11:13:45 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L318-L336 is what I send |
| 2023-03-31 11:14:20 | <geekosaur> | although I send it to xmonad-log-applet instead of xmobar because I use xmonad as MATE's window manager and run mate-panel instead of xmobar |
| 2023-03-31 11:14:48 | <Ou42> | you keep asking my 2ndary Q's before I can formulate them |
| 2023-03-31 11:14:50 | <Ou42> | amazing. |
| 2023-03-31 11:15:17 | <Ou42> | i dumped MATE as the panel hiccuped and the "click in the open space" part was a killer as there wasn't any |
| 2023-03-31 11:15:51 | <Solid> | Ou42: suggestions to improve the tutorial are always welcome (places that are hard to understand for a newcomer etc.) |
| 2023-03-31 11:15:55 | <Ou42> | moved to Cinamon. I've tinkered w/ xfce in the past and more beofre MATE, KDE |
| 2023-03-31 11:16:27 | <Ou42> | Solid: will keep that in mind. I would love to give back somehow. |
| 2023-03-31 11:16:52 | <Ou42> | I've been slowly learning Haskell for a while now. Not making any speed records learning it. |
| 2023-03-31 11:17:06 | <Solid> | Obviously I tried, but it's hard to know exactly what someone new to XMonad will find difficult, what they know and don't know etc. |
| 2023-03-31 11:18:02 | <Ou42> | it's honestly very good. I think the main issue y'all have is what's "broken" or easily broken by noobs when they try to implement sometihng that is "old" w/ the new stuff. |
| 2023-03-31 11:19:52 | <Ou42> | it honestly could have been my wonky haskell setup, but trying to get ewmhFullscreen to work before ( Jan per datestamps ) was a mess. I probably had wrong versions and I"m not that adept at stack and was trying to get it to serve a particular ghc ver w/o knowing what I was doing. |
| 2023-03-31 11:20:06 | <Ou42> | this attempt has been much more ... productive. |
| 2023-03-31 11:20:21 | <Ou42> | and it's because of that tut off of xmonad.org and the help here |
| 2023-03-31 11:20:34 | <Ou42> | single source of truth |
| 2023-03-31 11:20:41 | <Ou42> | unix philosophy |
| 2023-03-31 11:22:21 | <Ou42> | ah! memories. I rem why i deviated |
| 2023-03-31 11:22:42 | <Ou42> | what exactly is .xinitrc? and/or is it something that would be accessed by every WM? |
| 2023-03-31 11:23:42 | <Ou42> | "For the remainder of this document, .... If you have set up your ~/.xinitrc as directed in the xmonad guided tour, you should be good to go! If not, just smack an exec xmonad at the bottom of that file." |
| 2023-03-31 11:23:53 | <Solid> | It's the config for `xinit(1)` |
| 2023-03-31 11:24:06 | <Ou42> | I'd prefer to keep thinks as selfcontained and not affect the other WM/DE's |
| 2023-03-31 11:24:06 | <Solid> | it's what starts X11 when you don't have a display manager |
| 2023-03-31 11:24:21 | <Solid> | If you do then how to start XMonad depends on what you use |
| 2023-03-31 11:25:25 | <Ou42> | I"m not the smartest noob, changing any documentation based on my "preferences" might be a tad overkill. I'd prefer to keep xmonad "inside xmonad" to a point. I will contradict myself, by say using .Xresources. |
| 2023-03-31 11:26:16 | <Solid> | I mean, at some point you have to tell X11 which window manager to use |
| 2023-03-31 11:26:47 | <Solid> | whether that'd be via xinitrc or with a dm |
| 2023-03-31 11:27:02 | <Ou42> | but I ad a switcher already setup and whatever I had before was there, so I didn't start from scratch this time... I had xmonad installed... I jsut thought it was broken. I wiped out the xmonad.hs file and started w/ the tut. |
| 2023-03-31 11:27:18 | <Solid> | (if you plan on using multiple DEs/WMs then a display manager is definietly the better choice) |
| 2023-03-31 11:27:21 | <Ou42> | oh oh oh DM = switcher |
| 2023-03-31 11:27:31 | <Ou42> | yes, got that |
| 2023-03-31 11:27:41 | <Solid> | ah, yes :) |
| 2023-03-31 11:27:47 | <Ou42> | i can choose xmonad from a drop down on a GUI screen |
| 2023-03-31 11:29:51 | <Ou42> | OK, so here it is: |
| 2023-03-31 11:29:52 | <geekosaur> | right, so that doesn't use .xinitrc, it uses /usr/share/xsessions/xmonad.desktop and there's an Exec= line in there that tells it what to do |
| 2023-03-31 11:29:53 | <Ou42> | "Your ~/.xinitrc may wind up looking like this:" |
| 2023-03-31 11:30:08 | <Ou42> | right |
| 2023-03-31 11:30:14 | <Ou42> | I"m slow at skimming |
| 2023-03-31 11:30:16 | <Ou42> | sorry |
| 2023-03-31 11:31:07 | <Ou42> | so it's not req to use .xinitrc to start xmonad, but then you suggest editing it to include feh, nm-applet, trayer, and a few other things |
| 2023-03-31 11:31:34 | <Ou42> | so I didn't, I did the "myStarUpHooks = do" block thing |
| 2023-03-31 11:31:39 | <geekosaur> | right, because .xinitrc is the closest thing to a standard there is, but it assumes startx is used |
| 2023-03-31 11:32:07 | <geekosaur> | .xsession is another possibility (and is used on debian if .xinitrc doesn't exist even for startx/xinit) |
| 2023-03-31 11:33:38 | <Ou42> | not trying to be difficult ( it comes naturally ), but what if I didn't want to use any of those files? is it possible to *completely* setup xmobar / trayer w/o one of those files? |
| 2023-03-31 11:33:43 | <geekosaur> | also the xmonad.desktop on debian and derivatives runs xmonad-session which runs ~/.xmonad/xmonad-session-rc before starting xmonad iirc |
| 2023-03-31 11:33:50 | <geekosaur> | but that is very debian-dependent |
| 2023-03-31 11:34:23 | <geekosaur> | you can run stuff in the startupHook |
| 2023-03-31 11:34:44 | <Ou42> | i think my gist is the same... checking. |
| 2023-03-31 11:35:07 | <geekosaur> | but for xmobar, since we need to be able to send it information about workspaces, you use `withEasySB` to start it |
| 2023-03-31 11:35:39 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L181-L198 |
| 2023-03-31 11:38:50 | <Ou42> | OK ... |
| 2023-03-31 11:39:09 | <Ou42> | huh |
| 2023-03-31 11:39:26 | <Ou42> | brb |
| 2023-03-31 11:45:04 | <Ou42> | if either of you 2 are up for this... I'll upload another gist... short ver: xmobar is up and it does give some feedback ( still using xmobarProp iteration from tut ) |
| 2023-03-31 11:45:16 | <Ou42> | trayer is up but on the wrong screen |
| 2023-03-31 11:45:23 | <Ou42> | can look into fixing that later |
| 2023-03-31 11:45:34 | <Ou42> | but it does make seeing what is working / not working harder |
| 2023-03-31 11:45:50 | <Ou42> | feh is working via spawnOnce |
| 2023-03-31 11:46:07 | <Ou42> | trayer & nm-applet |
| 2023-03-31 11:46:35 | <Ou42> | are too, but spawnOnce "xfce4-power-manager &" isnt' showing up |
| 2023-03-31 11:47:17 | <Ou42> | oh and hexchat has an icon showing up on trayer too |
| 2023-03-31 11:47:31 | × | redgloboli quits (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
| 2023-03-31 11:48:28 | → | redgloboli joins (~redglobol@user/redgloboli) |
| 2023-03-31 11:49:26 | <geekosaur> | you may need to run that one in a terminal and see what errors if any it spits out |
| 2023-03-31 11:50:10 | <geekosaur> | although you may also need to check if it's actually running; conceivably it's configured to not show an icon when fully charged on power (I know I can set up mate-power-manager that way) |
| 2023-03-31 11:50:38 | <Ou42> | interesting |
| 2023-03-31 11:52:29 | <Ou42> | "$ Xfce Power Manager: Another power manager is already running" |
| 2023-03-31 11:52:59 | <geekosaur> | pgrep xfce4-power-manager |
| 2023-03-31 11:54:40 | <Ou42> | shows nothing |
| 2023-03-31 11:57:54 | <geekosaur> | ps -ef | grep power |
| 2023-03-31 11:58:31 | <geekosaur> | (which on my system shows the indicator icon is in fact a separate process… /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service) |
| 2023-03-31 12:01:08 | <Ou42> | which means ... there needs to be something else to attach it to trayer? |
| 2023-03-31 12:01:39 | <geekosaur> | looks like it, yes |
| 2023-03-31 12:05:44 | <Ou42> | I'm gonna try a tweak for trayer... might get disconnected... |
| 2023-03-31 12:09:11 | <Ou42> | I guess I don't get dc'd... OK, so uhhh spawnOnce... if a M-q is issued, will all spanOnce items get skipped? |
| 2023-03-31 12:12:07 | <geekosaur> | yes |
| 2023-03-31 12:12:22 | <geekosaur> | that's the point of spawnOnce |
| 2023-03-31 12:15:23 | <Ou42> | so I have to logout to test my trayer changes? |
| 2023-03-31 12:16:26 | <geekosaur> | or kill and restart it from a terminal |
| 2023-03-31 12:17:35 | <Ou42> | i killed it. I"m a killer. mom will be so disapointed |
| 2023-03-31 12:23:59 | <Ou42> | so silly |
| 2023-03-31 12:24:04 | <Ou42> | testing |
| 2023-03-31 12:25:10 | <Ou42> | yup. user error again. |
| 2023-03-31 12:25:19 | <Ou42> | that's at least 4 blunders on my end. |
| 2023-03-31 12:25:47 | <Ou42> | didn't copy the line right... dropped "--width 10", but how?! |
| 2023-03-31 12:26:42 | <geekosaur> | not sure what you're asking |
| 2023-03-31 12:27:02 | <geekosaur> | also not sure how you fit more than a couple of indicators into --width 10 🙂 |
| 2023-03-31 12:28:09 | <Ou42> | I have 3 and looks like room for 2 more! |
| 2023-03-31 12:28:13 | <Ou42> | :oD |
| 2023-03-31 12:28:34 | <Ou42> | I dunno about all this. really bad noob errors on my end. |
| 2023-03-31 12:29:15 | <Ou42> | what does a tray look like w/o any indicators? w/ no width assignment? |
| 2023-03-31 12:29:51 | <Ou42> | i should write a book. "noob's guide to inefficient computing". |
| 2023-03-31 12:31:51 | <Ou42> | interstingly picom is working better now too... I was getting transparency, but the rectangle was larger than it needed to be. now it's fine. |
| 2023-03-31 12:32:27 | <Ou42> | OK, I'll go back over the tut and see what changing things for xmobar does/doesn't do ... |
| 2023-03-31 12:32:54 | <Ou42> | or much more likely what boneheaded typo's and mistakes and things I'll accidentally leave out that will cause me hours of adventures |
| 2023-03-31 12:33:57 | <Ou42> | BTW, the "--width 10" is directly from the tut. Not my doing. My subconcious, apparently, wanted the width to fill the screen. |
| 2023-03-31 12:35:19 | <geekosaur> | I think the tutorial is shooting for having xmobar and trayer share the same part of the screen, so xmobar should be a little short and trayer's supposed to fill in the rest? but that's Solid's bailiwick since I don't run either |
| 2023-03-31 12:36:31 | <Ou42> | Yes, he sets xmobar at 90 and trayer at 10 |
| 2023-03-31 12:37:25 | <Ou42> | I still have a ton of Q's, but you've given me a ton to sift thru. tyvm |
| 2023-03-31 12:38:29 | <Ou42> | Solid: your tut is fine. maybe add a warning, "leaving out '--width 10' will cause trayer to expand to the full screen width and occlude xmobar. |
| 2023-03-31 12:38:49 | <Ou42> | y'know? for those "special" noobs. |
All times are in UTC.