| Age | Commit message (Collapse) | Author |
|---|
|
* Removed PipeReader2
* PipeReader pipename can be prefixed with default. (e.g. "I am default:/home/foo/pipe")
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously Hide, Reveal and Toggle were immediate actions. This is the
same behaviour as if called now with 0 as parameter.
If the parameter is a positive non zero value it is taken as a delay for
the requested action.
After the delay (implemented using threadDelay) a new signal is sent
with zero with no timeout being effective immediately. This is necessary
to evaluate the persistency flag after the delay because it might have
changed in the meantime.
Effectively this means that it is possible to cancel the delayed
operation by calling TogglePersistent.
|
|
The problem was a race condition which occured when running multiple
threads with a small timeout value. Then the TMVar could be left empty.
(e.g. hitting a key which causes an operation to write to the pipe very fast)
This meant that tryTakeTMVar would return Nothing which would cause all
subsequent reset threads to not call cb and keep a stale string on
display.
By using a Maybe String wrapped in a TVar there is always a valid value
available which can be used to restore the display (or not if it's
Nothing, but that's desired then and not because another thread was
scheduled earlier).
|
|
This commit updates the mpris plugin to use the DBus 0.10 interface.
DBus-Core does no longer exist and is deprecated.
DBus 0.10 does not use proxies anymore.
The dependency on Data.Text also disappeared.
Since I do not have/use mpris I cannot test if this works. It should
however, since the functionality was just transformed to use the new
interface.
|
|
safeHead is a very general utility function with suits better into a
common Util module.
|
|
The window became hidden although the toggling behaviour was set to
False for a particular pipe. This fixes this behaviour and hides the
window only if the configuration option is set to True.
|
|
This solves a problem when there is only one pipe in place. With a
default value of "" and only one pipe with a timeout the value is
overwritten with "" after the timeout. To prevent this from happening a
TMVar is used which will never be filled if there is only one pipe.
|
|
Using the trigger method activity on a pipe can now cause the window to
appear (reveal) and disappear again after a given timeout. The timeout
for hiding the window is the same as for restoring the pipes content.
The timeout value is given in tenth of seconds.
|
|
Realign methods, remove unnecessary imports and remove clutter
|
|
This plugin allows to display data from multiple pipes.
New data will always overwrite the currently displayed data.
However, if a timeout is specified, the previous content is restored.
Configuration works like this:
BufferedPipeReader <Alias> [ ( Timeout, "/path/to/fifo/pipe" ), (..), .. ]
If Timeout is set to 0 then the content is persistent, i.e. it will be
reset to any previous value, it will itself become the previous value.
If Timeout is set to a negative value the earth will stop spinning, so
don't do it.
|
|
We're using now the recommended statvfs interface, instead of the
obsolete statfs64. Moreover, we compute correctly the used space.
|
|
Conflicts:
xmobar.cabal
|
|
Now all values are returned as 'Value' wrapped entries.
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
This allows monitors to define update times other than time-based.
|
|
Since a kernel upgrade about two months ago, DiskU just blows up my
xmobar apparently at random.
|
|
|
|
|
|
|
|
|
|
Apparently, temp1_label does not follow the same naming pattern as the
rest of label files.
|
|
|
|
|
|
|
|
|
|
dev/add-incremental-config-option
|
|
Computing used space from total and available (rather than free) space.
|
|
|
|
Just as the Date plugin used the old-time package which would honor all
the available flags, so too did the DateZone plugin.
|
|
The Date plugin used the old-time package to format times which does not
honor all escape sequences and optional flags (e.g. the - (hyphen) that
should not pad the field).
|
|
|
|
Hat tip David U.
|
|
We were getting confused by devices appearing in mtab by their
symbolic path (such as an entry in /dev/disk/by-uuid and the like).
|
|
|
|
Must have been a glitch in my kernel version (?)
|
|
|
|
|
|
|
|
|
|
We no longer use -c to specify cases when only _design exists, but try
to detect that automatically (as well as the energy/charge dichotomy).
Also fixed a bug that precluded display of <watts> when no threshold
colours were specified.
|
|
|
|
|
|
|
