summaryrefslogtreecommitdiffhomepage
path: root/doc
diff options
context:
space:
mode:
authorjao <jao@gnu.org>2022-08-09 23:48:44 +0100
committerjao <jao@gnu.org>2022-08-09 23:48:44 +0100
commit63303977071f34d8142709960e8dae97cea1951e (patch)
tree19ea7c2704548f64d01619d9418581156f35dea9 /doc
parent474a7ebbe2589ae6b03f13c8318f36e9d3fde00b (diff)
downloadxmobar-63303977071f34d8142709960e8dae97cea1951e.tar.gz
xmobar-63303977071f34d8142709960e8dae97cea1951e.tar.bz2
examples -> etc
Diffstat (limited to 'doc')
-rw-r--r--doc/plugins.org8
-rw-r--r--doc/quick-start.org9
-rw-r--r--doc/using-haskell.org4
3 files changed, 10 insertions, 11 deletions
diff --git a/doc/plugins.org b/doc/plugins.org
index 558bdef..ccf5780 100644
--- a/doc/plugins.org
+++ b/doc/plugins.org
@@ -1385,9 +1385,9 @@
- Aliases to =PropName=
- Reads the X property named by =PropName= (a string) and displays its
- 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.
+ value. The [[../etc/xmonadpropwrite.hs][etc/xmonadpropwrite.hs script]] in xmobar's distribution can be
+ used to set the given property from the output of any other program or
+ script.
*** =UnsafeXPropertyLog PropName=
@@ -1480,7 +1480,7 @@
=/tmp/xmobar_status= will reveal xmonad for 1.5 seconds and
temporarily overwrite the window titles.
- - Take a look at [[../examples/status.sh][examples/status.sh]]
+ - Take a look at [[../etc/status.sh][etc/status.sh]]
- Expands environment variables for the pipe path
diff --git a/doc/quick-start.org b/doc/quick-start.org
index 4b060e2..a206a45 100644
--- a/doc/quick-start.org
+++ b/doc/quick-start.org
@@ -3,9 +3,8 @@
Xmobar can either be configured using the configuration language, or [[file:using-haskell.org][used as a
Haskell library]] (similar to xmonad) and compiled with your specific
configuration. For an example of a configuration file using the plain
-configuration language, see [[../examples/xmobar.config][examples/xmobar.config]], and you can have a look at
-[[../examples/xmobar.hs][examples/xmobar.hs]] for an example of how to write your own xmobar using
-Haskell.
+configuration language, see [[../etc/xmobar.config][etc/xmobar.config]], and you can have a look at
+[[../etc/xmobar.hs][etc/xmobar.hs]] for an example of how to write your own xmobar using Haskell.
* Command Line Options
@@ -432,7 +431,7 @@ Haskell.
Other options are ~Ansi~, ~Pango~, and ~Swaybar~.
** Showing xmobar output in Emacs tab or mode line
Using xmobar's ANSI color text ouput, one can plug it inside Emacs, and
- display your monitors in the mode line or the tab bar. The [[../examples/xmobar.el][xmobar.el
+ display your monitors in the mode line or the tab bar. The [[../etc/xmobar.el][xmobar.el
package]] provides a simple way of doing it.
** Using xmobar in wayland with swaybar or waybar
:PROPERTIES:
@@ -476,7 +475,7 @@ Haskell.
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]].
+ [[../etc/padding-icon.sh][etc/padding-icon.sh]].
** Signal handling
diff --git a/doc/using-haskell.org b/doc/using-haskell.org
index 667ab4d..4020557 100644
--- a/doc/using-haskell.org
+++ b/doc/using-haskell.org
@@ -75,7 +75,7 @@
=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 [[../examples/xmobar.hs][examples/xmobar.hs]] for an example of a plugin
+ every successive runs. See [[../etc/xmobar.hs][etc/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=.
@@ -114,7 +114,7 @@
To use your new plugin, you just need to use a pure Haskell configuration
for xmobar (as explained [[#xmobar-in-haskell][above]]) and load your definitions in your =xmobar.hs=
- file. You can see an example in [[../examples/xmobar.hs][examples/xmobar.hs]] showing you how to write
+ file. You can see an example in [[../etc/xmobar.hs][etc/xmobar.hs]] showing you how to write
a Haskell configuration that uses a new plugin, all in one file.
When xmobar runs with the full path to that Haskell file as its argument