Closed Gremious closed 1 year ago
This was a ""bug"" in pywalfox-native. Changing to slightly more useful logging errors a la:
except IOError as io_err:
error_message = 'Could not read colors from: %s' % PYWAL_COLORS_PATH
logging.error(error_message)
logging.error('val error: %s' % io_err)
return (False, None, error_message)
except ValueError as val_err:
error_message = 'Could not read colors from: %s' % PYWAL_COLORS_PATH
logging.error(error_message)
logging.error('val error: %s' % val_err)
return (False, None, error_message)
in fetcher.py (highly recommend) I get:
ERROR:val error: Invalid \escape: line 2 column 21 (char 22)
pywalfox-native died because wal apparently has a bug where it output the wallpaper path, line 2 in my colors.json, with \
slashes, as Windows paths are. That is however, invalid json, since \
is an escape string.
"wallpaper": "C:\\Users\\Gremious\\wallpaper.jpg"
in the json works perfectly.
Supposedly wal fixed this https://github.com/dylanaraps/pywal/pull/617 and current impl should return forward slashes so I am extra confused?
I will go look at pywal settings or maybe run a script with it to correct that I guess.
I am running pywalfox on Windows 11, and it connects ok (Debugger panel says Connected version 2.7). I try to fetch pywal colors, I get:
Said files exists:
C:\Users\Username\.pywalfox\pywalfox.json
is also real.Only error in console i see is
pywalfox log
just says failed to read colors.I am honestly not sure what could be causing this. Is this a known issue, or is there maybe a more verbose way to log?