Closed Mikilio closed 5 months ago
Yeah, I don't check XDG_DATA_DIRS
, but I do check XDG_DATA_HOME
. This is the reason the first one doesn't work but the second does. (The HM writes to extraCSS
to .config/gBar/style.css
) The second one asserts, because you executed the wrong command. You want gBar bar 1
for the bar. gBar 1
is not a valid command.
Though thinking about it I probably want to add a check for XDG_DATA_DIRS
Actually, I might make a PR for that if it helps :) Thanks a lot for gBar!
If you want to make a PR, that would be awesome!
Builds but doesn't run because it expects defaults
What doesn't work? Please be as precise as possible. e.g.: "gBar crashes on hovering the RAM sensor module. No other modules are affected."
Steps to Reproduce
Use the hm-module as described in README.md and start bar from terminal
Expected behavior
Bar should start
Screenshots/Error logs
Without extra config
With
extraCSS=""
Solution I browsed the Code and saw that absolute paths like /usr/share etc. are being used. These paths don't exist so the executable can not find any installed files by gBar. Abiding by XDG specifications and using environment variables like XDG_DATA_DIRS.
Information about your system and gBar