By default only local file systems are included now. In case a mounted
NFS share dissapears from the network the widget would be left hanging
there and has the potential to block everything else (including
awesome it self). File system widget now takes an optional argument
which, if true, will include remote file systems.
Widget returns the count of new and subject of last e-mail in a Gmail
inbox. Use ${count} and ${subject} in the format string to retrieve
the values. Widget takes a table with login information as an
argument.
I don't like how gmail widgets handle sensitive data but I gave in
seeing how popular they are. Better storing and handling of login
information would be in order but this isn't Python and I'm out of
ideas. For now use it on your own responsability, I would suggest to
set login info directly in the widget and file as read-only by user.
Now that vicious git repo is served trough a public web interface
there is no need for a full changelog. I considered removing it
completely, but it will have to wait - before the web interface
tarballed tags were requested much more than the repo was
cloned. Maybe that will change now, in which case the file should be
removed and stop wasting space.
With some recent commits we are matching a good number of custom
characters. Instead of waiting for another one that breaks it, just
match all punctuation characters. The regexp is pretty big and some
simplification is also welcomed.
Vicious tags from 1.0.12 will not be compatibile with awesome versions
prior to 3.4, tag 1.0.11 was the last one. Vicious was ported to the
new timer signals infrastructure and there is no backward
compatibility with hooks. In 1.0.12 even those C widgets that are
deprecated in awesome 3.4 (to be removed in 3.5) will not be
supported. Use awful.widget.progressbar and awful.widget.graph.
There were not many changes recently, but much more people are taking
the tarball instead of the development code so they will benefit from
the recent fixes and extended documentation.
- Prepend LANG=C to the df call, so it always gets the information in a way
it understands. Other languages do have other namings for "Filesystem" and
some use , instead of . for the number seperator.
- Adapt the line.match line so it actually matches values. (Have the - last
in the first match and teach it that mount targets can also have dots and colons
in it)
Widget returns speed and cache information for all available
CPUs/cores. It stores cpu speed in mhz and ghz in a table as well as
cpu cache in kb and mb. Values are retrieved using the CPU ID, i.e. we
would retrieve speed in ghz for CPU or core 1 with this format string:
${1 ghz}.
Adrian C. (anrxc)
Joerg Jaspert