summaryrefslogtreecommitdiffhomepage
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/compiling.org6
-rw-r--r--doc/quick-start.org27
-rw-r--r--doc/window-managers.org4
-rw-r--r--doc/write-your-own-plugin.org4
4 files changed, 20 insertions, 21 deletions
diff --git a/doc/compiling.org b/doc/compiling.org
index e780b5b..3ede1a9 100644
--- a/doc/compiling.org
+++ b/doc/compiling.org
@@ -6,14 +6,14 @@ code in a variety of ways:
- From [[http://hackage.haskell.org/package/xmobar/][Hackage]]. Just download the latest release from xmobar's hackage
page.
-- From [[http://github.com/jaor/xmobar/][Github]]. There are also tarballs available for every tagged
- release on [[https://github.com/jaor/xmobar/releases][Github's releases page]]
+- From [[http://codeberg.org/jao/xmobar/][Codeberg]]. There are also tarballs available for every tagged
+ release on [[https://codeberg.org/jao/xmobar/releases][Codeberg's releases page]]
- From the bleeding edge repo. If you prefer to live dangerously, just
get the latest and greatest (and buggiest, I guess) using git:
#+begin_src shell
- git clone git://github.com/jaor/xmobar
+ git clone git://codeberg.org/jao/xmobar
#+end_src
If you have cabal installed, you can now use it from within xmobar's
diff --git a/doc/quick-start.org b/doc/quick-start.org
index 929deb6..7625d50 100644
--- a/doc/quick-start.org
+++ b/doc/quick-start.org
@@ -7,7 +7,7 @@ loot at [[../examples/xmobar.hs][examples/xmobar.hs]] or, for a more complicated
[[https://gitlab.com/jaor/xmobar-config/][the author's configuration]].
There is also an example of a config using the configuration language
-available [[http://github.com/jaor/xmobar/raw/master/examples/xmobar.config][here]].
+available [[https://codeberg.org/jao/xmobar/src/branch/master/examples/xmobar.config][here]].
* Command Line Options
@@ -410,11 +410,11 @@ available [[http://github.com/jaor/xmobar/raw/master/examples/xmobar.config][her
*** Dynamically sizing xmobar
- See [[https://github.com/jaor/xmobar/issues/239#issuecomment-233206552][this idea]] by Jonas Camillus Jeppensen for a way of adapting
- dynamically xmobar's size and run it alongside a system tray widget such
- as trayer or stalonetray (although the idea is not limited to trays,
- really). For your convenience, there is a version of Jonas' script in
- [[../examples/padding-icon.sh][examples/padding-icon.sh]].
+ See [[https://codeberg.org/jao/xmobar/issues/239#issuecomment-233206552][this idea]] by Jonas Camillus Jeppensen for a way of adapting
+ dynamically xmobar's size and run it alongside a system tray widget such
+ as trayer or stalonetray (although the idea is not limited to trays,
+ really). For your convenience, there is a version of Jonas' script in
+ [[../examples/padding-icon.sh][examples/padding-icon.sh]].
*** Signal Handling
@@ -426,15 +426,14 @@ available [[http://github.com/jaor/xmobar/raw/master/examples/xmobar.config][her
screen.
* The DBus Interface
- When compiled with the optional =with_dbus= flag, xmobar can be
- controlled over dbus. All signals defined in [[https://github.com/jaor/xmobar/blob/master/src/Xmobar/System/Signal.hs][src/Signal.hs]] as =data
- SignalType= can now be sent over dbus to xmobar.
+ When compiled with the optional =with_dbus= flag, xmobar can be controlled
+ over dbus. All signals defined in [[../src/Xmobar/System/Signal.hs][src/Signal.hs]] as =data SignalType= can now
+ be sent over dbus to xmobar.
- Due to current limitations of the implementation only one process of
- xmobar can acquire the dbus. This is handled on a
- first-come-first-served basis, meaning that the first process will
- get the dbus interface. Other processes will run without further
- problems, yet have no dbus interface.
+ Due to current limitations of the implementation only one process of xmobar
+ can acquire the dbus. This is handled on a first-come-first-served basis,
+ meaning that the first process will get the dbus interface. Other processes
+ will run without further problems, yet have no dbus interface.
- Bus Name: =org.Xmobar.Control=
- Object Path: =/org/Xmobar/Control=
diff --git a/doc/window-managers.org b/doc/window-managers.org
index f60ee37..ea3aeea 100644
--- a/doc/window-managers.org
+++ b/doc/window-managers.org
@@ -58,7 +58,7 @@ choice.
- Aliases to =PropName=
- Reads the X property named by =PropName= (a string) and displays its
- value. The [[https://github.com/jaor/xmobar/raw/master/examples/xmonadpropwrite.hs][examples/xmonadpropwrite.hs script]] in xmobar's distribution
+ value. The [[../examples/xmonadpropwrite.hs][examples/xmonadpropwrite.hs script]] in xmobar's distribution
can be used to set the given property from the output of any other
program or script.
@@ -153,7 +153,7 @@ choice.
=/tmp/xmobar_status= will reveal xmonad for 1.5 seconds and
temporarily overwrite the window titles.
- - Take a look at [[http://github.com/jaor/xmobar/raw/master/examples/status.sh][examples/status.sh]]
+ - Take a look at [[../examples/status.sh][examples/status.sh]]
- Expands environment variables for the pipe path
diff --git a/doc/write-your-own-plugin.org b/doc/write-your-own-plugin.org
index d558e40..a877ad8 100644
--- a/doc/write-your-own-plugin.org
+++ b/doc/write-your-own-plugin.org
@@ -23,8 +23,8 @@ an example.
=run= can be used for simpler plugins. If you define only =run= the
plugin will be run every second. To overwrite this default you just need
to implement =rate=, which must return the number of tenth of seconds
-between every successive runs. See [[https://github.com/jaor/xmobar/blob/master/examples/xmobar.hs][examples/xmobar.hs]] for an example of
-a plugin that runs just once, and [[https://github.com/jaor/xmobar/blob/master/src/Xmobar/Plugins/Date.hs][src/Xmobar/Plugins/Date.hs]] for one
+between every successive runs. See [[../examples/xmobar.hs][examples/xmobar.hs]] for an example of
+a plugin that runs just once, and [[../src/Xmobar/Plugins/Date.hs][src/Xmobar/Plugins/Date.hs]] for one
that implements =rate=.
Notice that Date could be implemented as: