| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Using the -C option, *additional* commands can be given to Xmobar. This
allows a common configuration to be used and then differentiated in just
the -C calls.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hat tip Ivo van der Sangen.
|
|
An attempt to fix #60, that is, crashes after power resumes due to
unreadable battery stats files.
|
|
added applicative instance for ReaderT which was added in GHC7
|
|
To support multiple locales, an lock was introduced.
Although through this, supporting DateL and DateZoneL would be
cumbersome.
To simplify the usage, DateZone was replaced with DateZoneL.
Additionally the position of the Alias parameter was changed.
Using "" as Zone parameter for DateZoneL simulates DateL.
Providing also "" for locale simulates Date.
|
|
This commits adds support for localized datetime outputs like date(1).
|
|
skinner-screen_update
|
|
|
|
skinner-screen_update
Conflicts:
NEWS
src/XUtil.hsc
|
|
Switches HUP to USR1 and USR1 to USR2, as requested
|
|
|
|
Didn't tested xrandr events with that event detection.
Notify value is 0, the one used (keypress) is 1
|
|
|
|
The output just stopped at some point until a new XEvent was received
As XLockDisplay is in theory a good idea, with XNextEvent blocking its
not usable.
As it turned out, a window can be shared between display connections.
Now the eventloop has its own display connection (which also removes the
need for the lock introduced before).
Additionally the screeninfo doesn't need to be fetched into a TVar in
the eventerloop anymore.
Also this was needed for the signalHandlers to work correctly again.
|
|
*) replaced window destroy and create with a reposition
*) replaced the exception for redraw with an MVar
*) put nextEvent into an own thread, communication over the MVar
*) signal handlers for repositioning and screen swap
Notes:
*) getScreenInfo is a parameter of eventLoop because it blocks when there
is an nextEvent waiting for an new event
|
|
|
|
there is still the bug this plugin needs to be the last or parsing
the config file fails
|
|
|
|
catch alsa exception on decibel acquire
|
|
The last commit removed the exposure event which turned out to be a big
problem.
Although the bug still exists that not all xrandr events are received
when normal events are enabled.
To work around this problem a second display is created on which only
the xrandr events are enabled.
On an exposure event the eventqueue for this display is processed.
The results are very good, in the worst case an exposure event must be
triggered by the user on xmobar to update its position.
|
|
But I'm not sure if something is broken now...
|
|
handle doesn't get all events.
simple c program and simple haskell program are getting all of them.
there must be something in xmobar which catches about 3 of the
screenchange events ...
|
|
This closes #17.
For some reasons the alsa interface does not provide a dB value on all
systems. Instead an error is returned.
The alsa-mixer library checks for such return values and throws an
exception if one is detected.
This patch catches the exception and returns 0 as dB value.
|
|
|
|
|
|
It was only looked for a ']' followed by space-characters and either a
'}' or ','.
This looks good in generally but considering that a command can have as
its last input parameter an array e.g.
...
, Run Something ["Do"]
, Run XMonadLog
]
, sepChar = "%"
}
...
This will not work unless 'Something' is the last command in the array.
This patch fixes this problem, as a ',' is only accepted if it is not
followed by a "Run".
|
|
|
