-
-
Notifications
You must be signed in to change notification settings - Fork 3
/
config.sample.toml
40 lines (33 loc) · 1.24 KB
/
config.sample.toml
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
################################################################################
#### Preset configuration ######################################################
################################################################################
[presets.example]
# TCP configuration, used by server binders and clients. Requires the
# cargo feature "tcp".
#
tcp.host = "localhost"
tcp.port = 1234
# A cycle is a step in the timer lifetime, represented by a name and a
# duration. You can either define custom cycles:
#
cycles = [
{ name = "Work", duration = 5 },
{ name = "Rest", duration = 3 },
]
# Predefined cycles can also be used:
#
#preset = "pomodoro" | "52/17"
# Force the timer to stop after the given amount of loops:
#
#cycles-count = 5
# Customize the timer precision. Available options: second, minute, hour.
#
#timer-precision = "minute"
# A hook can be either a shell command or a system notification. Hook
# names follow the format "on-{name}-{event}", where "name" is the
# kebab-case version of the cycle name, and "event" the type of event:
# begin, running, set, pause, resume, end.
#
#hooks.on-work-begin.cmd = "echo 'Work started!' >> /tmp/log"
hooks.on-work-begin.notify.summary = "Comodoro"
hooks.on-work-begin.notify.body = "Work started!"