The xmobar package

[Tags: bsd3, program]

Xmobar is a minimal status bar for the XMonad Window Manager.

It was inspired by the Ion3 status bar, and supports similar features.


[Skip to ReadMe]

Properties

Versions0.3, 0.3.1, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.9.1, 0.9.2, 0.10, 0.11, 0.11.1, 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18, 0.19, 0.20, 0.20.1, 0.21, 0.22, 0.22.1, 0.23, 0.23.1
Change logNone available
Dependenciesbase (>=2.0), filepath (>=1.0), mtl (>=1.0), parsec (>=2.0), unix (>=1.0), X11 (>=1.2.1) [details]
LicenseBSD3
AuthorAndrea Rossato
Maintainerandrea.rossato@unibz.it
CategorySystem
Home pagehttp://gorgias.mine.nu/repos/xmobar/
Executablesxmobar
UploadedFri Jul 13 12:45:41 UTC 2007 by AndreaRossato
DistributionsDebian:0.23.1, Fedora:0.22.1, FreeBSD:0.23.1, NixOS:0.23.1
Downloads11626 total (389 in last 30 days)
Votes
0 []
StatusDocs not available [build log]
All reported builds failed as of 2015-06-10 [all 2 reports]

Downloads

Maintainers' corner

For package maintainers and hackage trustees

Readme for xmobar-0.6

XMobar - a status bar for the XMonad Window Manager

ABOUT
=====

Xmobar is a minimalistic, text based, status bar, designed for the
XMonad Window Manager.

It was inspired by the Ion3 status bar, and supports similar features.
See xmobar.config-sample for a sample configuration.

Try it with:
xmobar xmobar.config-sample

INSTALLATION
============

tar xvfz xmobar-0.6
cd xmobar-0.6
runhaskell Setup.lhs configure --prefix=/usr/local
runhaskell Setup.lhs build
runhaskell Setup.lhs haddock (optional for building the code documentation)
runhaskell Setup.lhs install (possibly to be run as root)

Run with:
xmobar /path/to/config &
or
xmobar &
if you have the default configuration file saved as:
~/.xmobarrc

CONFIGURATION
=============

Quick Start
-----------

See xmobar.config-sample for an example.

For the output template:

- %command% will execute command and print the output. The output may
  contain markups to change the characters' color.

- <fc=#FF0000>string</fc> will print "string" with #FF0000 color (red).

Other configuration options:

font: Name of the font to be used
bgColor: Backgroud color
fgColor: Default font color
xPos: x position (origin in the upper left corner) of the XMobar window 
yPos: y position
width: width of the XMobar window 
height: height
align: text alignment 
refresh: Refresh rate in tenth of seconds
commands: For setting the options of the programs to run (optional)
sepChar: The character to be used for indicating commands in the
         output template (default '%')
template: The output template 

The Output Template
-------------------

The output template must contain at least one command. XMobar will
parse the template and will search for the command to be executed in
the "commands" configuration option. First an "alias" will be search
(internal commands such as Weather or Network have default aliasing,
see below). After that the command name will be tried. If a command is
found, the arguments specified in the "commands" list will be used. 

If no command is found in the "commands" list, XMobar will try to
execute a program with the name found in the template. If the
execution is not successful an error will be reported.
   
The "commands" Configuration Option
-----------------------------------

The "commands" configuration option is a list of commands' information
and arguments to be used by XMobar when parsing the output template.
Each member of the list consists in a command prefixed by the "Run"
keyword. Each command has arguments to control the way XMobar is going
to execute it.

Available template commands are: Weather, Network, Memory, Swap, Cpu,
Battery, and Com. This last one is used to execute external programs.

Other commands can be created as plugins with the Plugin
infrastructure.

This is an example of a command in the "commands" list:
Run Memory ["-t","Mem: <usedratio>%"] 10

Internal Commands and Aliases
-----------------------------

Each command in the "commands" configuration option list has an alias
to be used in the template.

Internal commands have default aliases:

Weather StationID Args RefreshRate
- aliases to the Station ID: so Weather "LIPB" [] can be used in template as %LIBP%
- Args: the argument list (see below)
- Variables that can be used with the "-t"/"--template" argument: 
	    "station", "stationState", "year", "month", "day", "hour",
	    "wind", "visibility", "skyCondition", "tempC", "tempF",
	    "dewPoint", "rh", "pressure"
- Default template: "<station>: <tempC>C, rh <rh>% (<hour>)"

Network Interface Args RefreshRate
- aliases to the interface name: so Network "eth0" [] can be used as %eth0%
- Args: the argument list (see below)
- Variables that can be used with the "-t"/"--template" argument: 
	    "dev", "rx", "tx"
- Default template: "<dev>: <rx>|<tx>"

Memory Args RefreshRate
- aliases to "memory"
- Args: the argument list (see below)
- Variables that can be used with the "-t"/"--template" argument: 
	    "total", "free", "buffer", "cache", "rest", "used", "usedratio"
- Default template: "Mem: <usedratio>% (<cache>M)"

Swap Args RefreshRate
- aliases to "swap"
- Args: the argument list (see below)
- Variables that can be used with the "-t"/"--template" argument: 
	    "total", "used", "free", "usedratio"
- Default template: "Swap: <usedratio>%"

Cpu Args RefreshRate
- aliases to "cpu"
- Args: the argument list (see below)
- Variables that can be used with the "-t"/"--template" argument: 
	    "total", "user", "nice", "system", "idle"
- Default template: "Cpu: <total>"

Battery Args RefreshRate
- aliases to "battery"
- Args: the argument list (see below)
- Variables that can be used with the "-t"/"--template" argument: 
	    "left"
- Default template: "Batt: <left>"

Internal Commands Arguments
---------------------------

These are the arguments that can be used for internal commands in the
"commands" configuration option:

-H number           --High=number               The high threshold
-L number           --Low=number                The low threshold
-h color number     --high=color number         Color for the high threshold: es "#FF0000"
-n color number     --normal=color number       Color for the normal threshold: es "#00FF00"
-l color number     --low=color number          Color for the low threshold: es "#0000FF"
-t output template  --template=output template  Output template of the command.

Commands' arguments must be set as a list. Es:
Run Weather "EGPF" ["-t","<station>: <tempC>C"] 36000

In this case XMobar will run the weather monitor, getting information
for the weather station ID EGPF (Glasgow Airport, as a homage to GHC)
every hour (36000 tenth of seconds), with a template that will output
something like:
"Glasgow Airport: 16.0C"

Executing External Commands
---------------------------

In order to execute an external command you can either write the
command name in the template, in this case it will be executed without
arguments, or you can configure it in the "commands" configuration
option list with the Com template command:

Com ProgarmName Args Alias RefreshRate
- ProgramName: the name of the program
- Args: the arguments to be passed to the program at execution time
- Alias: a name to be used in the template. If the alias is en empty
  string the program name can be used in the template.
Es:
Run Com "uname" ["-s","-r"] "" 36000
can be used in the output template as %uname%

Run Com "date" ["+\"%a %b %_d %H:%M\""] "mydate" 600
can be used in the output template as %mydate%

PLUGINS
=======

Writing a Plugin
----------------

Writing a plugin for XMobar should be very simple. You need to create
a data type with at least one constructor.

Next you must declare this data type an instance of the Exec class, by
defining the 3 needed methods:

    run :: e -> IO String
    rate :: e -> Int
    alias :: e -> String

"run" must produce the IO String that will be displayed by XMobar.
"rate" is the refresh rate for you plugin (the number of tenth of
seconds between two succesive runs);
"alias" is the name to be used in the output template.

That requires importing the plugin API (the Exec class definition),
that is exported by Plugins.hs. So you just need to import it in your
module with:

import Plugins

After that your type constructor can be used as an argument for the
Runnable type constructor "Run" in the "commands" list of the
configuration options.

This requires importing you plugin into Config.hs and adding you type
to the type list in the type signature of Config.runnableTypes.

For a vary basic example see Plugins/HelloWorld.hs that is distributed
with XMobar.

Installing a Plugin
-------------------

Installing a plugin should require 3 steps. Here we are going to
install the HelloWorld plugin that comes with XMobar:

1. import the plugin module in Config.hs, by adding: 
   
import Plugins.HelloWorld

2. add the plugin data type to the list of data types in the type
   signauture of "runnableTypes" in Config.hs. For instance, for the
   HelloWorld plugin, chnage "runnableTypes" into:

runnableTypes :: (Command,(HelloWorld,()))
runnableTypes = undefined

3. Rebuild and reinstall XMobar. Now test it with:

xmobar Plugins/helloworld.config

As you may see in the example configuration file, the plugin can be
used by adding, in the "commands" list:

Run HelloWorld

and, in the output template, the alias of the plugin:

%helloWorld%

That's it.

AUTHOR
======

Andrea Rossato <andrea.rossato@unibz.it>

CREDITS
=======

Thanks to Robert Manea for his help in understanding how X works. He
gave me suggestions on how to solve many many problems with XMobar.

XMobar incorporates patches from:
Krzysztof Kosciuszkiewicz

LINKS
=====

The XMobar home page:
http://gorgias.mine.nu/repos/xmobar/

XMobars darcs repository:
http://gorgias.mine.nu/repos/xmobar/

The XMonad Window Manager
http://xmonad.org