#xmobar — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xmobar, aggregated by home.social.
-
It's always nice when I unexpectedly understand something after a long time - today I understood the #xmobar config <3
-
Personally I use #xmonad though. I wouldn't recommend using it unless you want to learn #haskell. I have used #awesomeWM and #qtile as well, but I am not as well versed in them.
Haskell was quite fun to learn as its a purely functional language with no object oriented ability.
The reason why I use xmonad is primarily because there are so many libraries for it. I #polybar rather than #xmobar.
-
I'm about 90% done with my #xmobar rice. Living in #xmonad has been an eye-opening experience, and when I finally got to seriously working on its panel, I truly realize the power of #Linux and the freedom it provides in customization.
Adding in the icons was definitely my favorite part of the process! All that's left to do is to add the workspaces on the left, which shouldn't be difficult. I'll probably post a picture soon!
-
This is a great looking xmonad setup:
https://old.reddit.com/r/unixporn/comments/pf23vd/xmonad_onedark_colorscheme/
Dotfiles in the comments, also nice neofetch!
#linux #customization #xmonad #xmobar #neofetch -
Looks like my slow login (xmonad) is due to how I call xmobar. Right now it's about 40 seconds.
I disabled my startup things inside xmonad config, I also played with my .xinitrc.
Fun stuff.
The only problem is that, any other way xmobar simple doesn't load, I can only see the space at the top where it should be. Trayer loads fine and works (ofc since it doesn't depend on xmobar).
Note that if I start it from terminal, it's totally fine, except I can't see workspaces.
#linux #xmonad #xmobar #startup -
Yesterday I stayed up so late because I am obsessed with making xmonad work the way I want to. And finally I could put nice icons on my xmobar, and put some stuff in order, so it looks good and I can instantly see the information I want. CPU, memory usage, I have disk space, volume, keyboard layout and even I can see how many updates I have on my system.
I still need to do some cosmetic stuff, make it more distinct.
On picture: xmobar, with full transparency.
#linux #xmonad #xmobar #customization -
CW: xmonad success (long)
What I've learned today is that it's always good to look for many sources if you have problems or just want to learn things.
First I watched DT's awesome xmonad video, and I just couldn't make xmobar appear. I searched for the last few days, and I wanted to solve the problem based on his config.
Instead I should have looked for another solution entirely, and infact I've found this:
https://superuser.com/questions/470067/what-is-wrong-in-this-xmonad-configuration
Now my xmobar works perfectly! Onto ricing and other stuff. (tomorrow)
I have to say I feel that xmonad is faster in some regard than dwm, or maybe my config is not that complex.
I also re-installed xmonad xmonad-contrib and xmobar from the Artix community repo. I don't know if that helped at the end (probably not).
I am really happy right now. I worked 3 days on this, and at one point I just logged out and went back to dwm. However I felt that I was close to making it work, and I did.
Xmonad and haskell is not really for me as in "I am not a programer and I am way over my head with this", but I will make this work for me. My setup might not be as flashy like some others, but at least I can learn something.
What an adventure!
#linux #xmonad #xmobar #customization #learning #artix -
OK, scratch that one. Looks like since Arch is using systemd, it doesn't really plays well in Artix, when you get something from their repo.
With the above solution xmobar works fine, but there is no sound and some other problems.
However if I add to my .xinitrc, like this:
exec dbus-launch xmonad
Then xmobar works (except for some reason it doesn't read it from the config file, so I need to start it from terminal), and there is sound, etc.
One step closer...
#xmonad #linux #wm #xmobar -
I finally found a solution. For some reason the ~/.config/xmobar/xmobarrc file didn't work, renamed to xmobar.config. Then run in terminal, it give me this error:
xmobar: SocketError {socketErrorMessage = "Network.Socket.connect: <socket: 16>: does not exist (No such file or directory)", socketErrorFatal = True, socketErrorAddress = Just (Address "unix:path=/run/user/1000/bus")}
Which lead me to reddit, and a possible solution, by adding two lines to /etc/environment file
DBUS_SYSTEM_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket
And it now shows, and updates information like CPU and MEM usage.
However if I want to tweak the xmobar config file now, it doesn't update. Which is of course less annoying than not showing at all.
I drink a tea for that...
#xmonad #linux #wm #xmobar -
Got inspired after watching @derek DT's video on leftwm. I have now played a few minutes with polybar and xmobar. I Like it! Will probably continue try get it look better and fix some keybindings etc... #sundayfun #leftwm #polybar #xmobar
-
Back to using #XMonad as my primary WM. I'm really attached to my #xmobar setup. Minimalist, but tells me what I need. Recreating that in another WM turned out to be so tedious as to end the experiment.
Awkward image size but, FWIW, from left to right:
* username
* workspaces (key:label)
* layout
* window/app
...
* dropbox status
* wifi status
* battery level ("^" charging, "_" discharging)
* volume level
* backlight level
* date and time
