The change in commit 6989713 broke the internet() test function by
trying to access the DNS port of "www.google.de", causing it to always
return False, which in turn broke all modules calling it. We instead use
the actual domain name of Google's DNS server at IP "8.8.8.8".
-there was a trailing comma in the clock module that would interact badly with i3pystatus & i3bar; i3pystatus seeing the comma would generate the json ** full_text : ["13 september"] ** and then i3bar would only display the last module (one may have to check for i3bar robustness). resulted in having only the clock module displayed
-the 2nd problem was with the alsa module when setting the volume to a number <0 or > 100 then the pyalsa bindings would generate the following error in .xsession-errors
target_module.on_click(command["button"])↲
File "/home/teto/i3pystatus/i3pystatus/core/modules.py", line 31, in
on_click↲
self.on_upscroll()↲
File "/home/teto/i3pystatus/i3pystatus/alsa.py", line 95, in
on_upscroll↲
self.alsamixer.setvolume( vol + self.increment)↲
alsaaudio.ALSAAudioError: Volume must be between 0 and 100↲
time depending on different timezones. You can set the timezone as
described on the data linked on http://www.iana.org/time-zones.
For instance:
status.register('clock',
format=[("%a %X",'Europe/Dublin'),("%X",'Europe/Paris')]
)
In such a case, i3pystatus will try to load the file designed by the
environment variable NOTMUCH_CONFIG and "~/.notmuch_config". and
retrieve the value "path" of the section [database].
Rationale:
-other backends don't require internet access
-displaying last unread count w/o connection seems reasonable
-however: error handling in get_connection() is quite wildcardy,
which is no good. Should be fixed asap.
Introducing a core exception for directly displaying errors may be a good idea at this point for next.
