/usr/share/doc/khal-doc/html/_sources/configure.rst.txt is in khal-doc 1:0.9.8-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 | Configuration
=============
:command:`khal` reads configuration files in the *ini* syntax, meaning it understands
keys separated from values by a **=**, while section and subsection names are
enclosed by single or double square brackets (like **[sectionname]** and
**[[subsectionname]]**).
Help with initial configuration
-------------------------------
If you do not have a configuration file yet, running :command:`khal configure`
will launch a small, interactive tool that should help you with initial
configuration of :command:`khal`.
Location of configuration file
------------------------------
:command:`khal` is looking for configuration files in the following places and
order: :file:`$XDG_CONFIG_HOME/khal/config` (on most systems this is
:file:`~/.config/khal/config`), :file:`~/.khal/khal.conf` (deprecated) and a
file called :file:`khal.conf` in the current directory (deprecated).
Alternatively you can specify which configuration file to use with :option:`-c
path/to/config` at runtime.
.. include:: configspec.rst
A minimal sample configuration could look like this:
Example
-------
.. literalinclude:: ../../tests/configs/simple.conf
:language: ini
Exemplary discover usage
-------------------------
If you have the following directory layout::
~/calendars
├- work/
├- home/
└─ family/
where `work`, `home` and `family` are all different vdirs, each containing one
calendar, a matching calendar section could look like this:
.. highlight:: ini
::
[[calendars]]
path = ~/calendars/*
type = discover
color = dark green
Syncing
-------
To get :command:`khal` working with CalDAV you will first need to setup
vdirsyncer_. After each start :command:`khal` will automatically check if
anything has changed and automatically update its caching db (this may take some
time after the initial sync, especially for large calendar collections).
Therefore, you might want to execute :command:`khal` automatically after syncing
with :command:`vdirsyncer` (e.g. via :command:`cron`).
.. _vdirsyncer: https://github.com/untitaker/vdirsyncer
|