Closed hgvhgv closed 4 years ago
After poking around some more, I'm more stumped. I receive a similar "Unknown values" warning from solarized_dark, but there the date/timestamp shows up in search mode. Whereas using the tomorrow theme (the only other "light" theme shipped), I receive a similar warning about "Unknown values" and there is no date/timestamp in search mode.
I took the "Unknown values" warning out of this issue hed as a result. Not sure how to further debug.
With all of the debug logs, I am getting this line at the end of each new search mode query, e.g.
DEBUG:ui:Got key (['2'], [50])
DEBUG:ui:cmdline: 'search tag:flagged'
DEBUG:ui:search command string: "search tag:flagged"
DEBUG:__init__:mode:search got commandline "search tag:flagged"
DEBUG:__init__:ARGS: ['search', 'tag:flagged']
DEBUG:__init__:cmd parms {'sort': None, 'query': ['tag:flagged']}
DEBUG:utils:unquoted header: [snip]
. . .
DEBUG:utils:unquoted header: [snip]
DEBUG:walker:EMPTY PIPE
DEBUG:ui:Got key (['q'], [113])
DEBUG:ui:cmdline: 'exit'
Could that be related?
It seems that the solarized_light theme was not in order. I have not fully debugged the reason but the commit that I've just pushed to the master branch fixes this issue for me. The two lines are difectly taken from the solarized_dark theme.
Great worked for me too!
After updating from alot .8 to .9 today, the dates/timestamps are not showing up in search mode (see image). They show up in thread mode, so I believe my timestamp_format hook is still working. And when using the default alot theme, they do show up in search mode, so I believe the problem is with solarized_light, which I usually use.
In the debug log, it's clear that something is going wrong with reading the solarized_light theme, which is just the standard version that comes with alot . All 16 basic colors (in both 16 and 256) are "missing," even though they are defined in the file. This problem was already present in alot .8 (I noticed it when debugging other problems) but didn't cause the missing date/timestamp issue (for reference, my timestamp_format hook is below).
Could it have something to do with Configobject (see #1238; the "unknown values" in the config file maybe point to this?) or leftover python caches (homebrew sometimes has issues with these)? Or maybe how iTerm2 implements solarized? Any times would be appreciated. Not even sure how to start debugging further.
Software Versions
To Reproduce Steps to reproduce the behaviour:
Error Log Please include all error information from the log file.
~/.config/alot/hooks.py