The current method of calculating the amount of free memory is
incorrect. The linux kernel provides a method of getting this value,
MemAvailable, which we can simply use directly
* used memory (values 1 and 2) are: everything but free+cache
* laundry is counted as freeable, but not free.
** "notfreeable memory" (values 11 and 12) are: active+inactive+wired
* removes unused variables
* enhances one-character-variables for better readabilitiy
* fixes calculation errors
** used memory: active, inactive, and wired
** available memory: cached, laundry, and free
see https://wiki.freebsd.org/Memory for more information
* Added option for a table to configure volume widget, allowing device specification also.
* Updated README.md with new configuration options for volume widget
* volume: allow passing a list of commandline arguments
This avoids using a unicode character that looks just like a hyphen but
isn't, leading to subtle bugs when developers write code that interacts
with the bat_linux widget.
For some time now, gmail feeds are in a single line. The goal of this patch is to handle
both cases (single and multiline). It will find the text between title tags after the
first entry tag.
Since the first feed title is skiped with this regex, title regexes aren't needed anymore.
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
Or the percentage value will be different from alsamixer or desktop
environment's indicator, which confuses users.
Quote from amixer's manpage, "Use the mapped volume for evaluating the
percentage representation like alsamixer, to be more natural for human
ear."
ref:
http://git.alsa-project.org/?p=alsa-utils.git;a=blob;f=alsamixer/volume_mapping.c
Signed-off-by: Adam Lee <adam8157@gmail.com>
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
Modern batteries should expose information about their design capacity
which we can compare to current capacity and deduce how much 'wear'
the battery got and expose that as a negative value percentage.
Feature sent in August took a while to convince the maintainer many
modern batteries provide this information.
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
Previously, a simple hyphen (“-”) was used to show that the battery is
discharging. The minus sign is a distinct char, and also distinct from
the en-dash (“–”) and the em-dash (“—”).
With this commit, I put in a unicode “MINUS SIGN” (0x2212) which I
created with a Digraph in Vim `^k-2`.
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
This reverts commit a6a73f47, because the issue was solved in mpd
release 0.18.2. I imported the workaround for historical reasons and
in case someone gets stuck with version 0.18 on his preferred OS
distribution.
Checkupdates is a good tool avoiding any need for period pacman -Sy
jobs from root crontab, however it works by maintaining its own
database in /tmp by default (and _that_ is a tmpfs by default) so on
every initialization it would stall awesome until it makes the first
sync. Better approach would be to keep its db inside $HOME for
persistence, and then to initiate the first (and longest) sync
manually before converting your package widgets to "Arch C".
All this is the reason I can't recommend it as the default right
now...
Years ago iwconfig started its life in /sbin. Then some distributions
moved it to /usr/bin. Then in 2012 some projects started pushing for
deprecation of /usr/sbin and merging everything into /usr/bin.
We now search paths including /usr/bin for the iwconfig binary. This
is because sbin paths are not usually in non privileged user PATH, so
we help io.popen locate the binary on the file-system.
We do this search in the following way:
- default to basename only, 'iwconfig' for the iwconfig variable
- search paths one by one once and redeclare variable iwconfig with
full path if binary is found in any
- avoid searching paths on next execution if iwconfig variable
already contains a path
Test case:
lua> foo = require("vicious.widgets.os")
lua> print(foo()[1])
/usr/share/lua/5.1/vicious/widgets/os.lua:66: attempt to call
field 'getenv' (a nil value)
In Lua 5.2 io.lines() has to be used to iterate until EOF, otherwise
the fd will not be closed and eventually tons of naughty messages
will start to pop up saying that no more fd can be opened.
Signed-off-by: Arvydas Sidorenko <asido4@gmail.com>
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
Now that we are so nice to provide default frequency values check if
frequency exists before calculating voltage, not to screw up *those*
default values.
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
In some cases not all cpu informations will be provided.
(ex. in virtual machines)
Therefore default to "N/A".
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
Since Linux 3.0 most if not all people have temp1_input file missing,
so default to temp2_input. But also allow an optional third argument
to change to yet another file to avoid this kind of problem in the
future.
If the battery state change from charging to full,
power_now is reseted to zero for a little time.
This cause division by zero, which was visible as a very big negative
number because of the behaviour of string.format.
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
In cpufreq widget, governor char is the same for ondemand and
conservative which makes it impossible to overload symbols to
different values for these two governors in a format function.
Signed-off-by: Adrian C. (anrxc) <anrxc@sysphere.org>
Lorenzo Gaggini
Enric Morales
mutlusun
Juan Carlos Menonita
Alexander Koch
Nguyễn Gia Phong
Jörg Thalheim
Jay Kamat
Andreas Geisenhainer
Brandon Hartshorn
getzze
David Udelson
Roberto
starenka
Elric Milon
Mellich
zhrtz
Keith Hughitt
Jörg Thalheim
Benoît Zugmeyer
Andrew Merenbach
Lyderic Lefever
Adam Lee
Normal Ra
Jonathan McCrohan
Martin Ueding
Adrian C. (anrxc)
joe di castro
Andrea Scarpino
Juergen Descher
Jörg Thalheim
Arvydas Sidorenko
jinleileiking
Sébastien Luttringer