summaryrefslogtreecommitdiffstats
path: root/files/manual.html
blob: c468fe9b3d34f7e0f3c1a6309a6452c4f57ec1e5 (plain) (blame)
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
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CALCURSE - text-based organizer</title><link rel="stylesheet" type="text/css" href="docbook-xsl.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.77.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idp26315904"></a>CALCURSE - text-based organizer</h2></div></div><hr /></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="section"><a href="#_introduction">1. Introduction</a></span></dt><dt><span class="section"><a href="#_overview">2. Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#_creation_history">2.1. Creation history</a></span></dt><dt><span class="section"><a href="#_important_features">2.2. Important features</a></span></dt></dl></dd><dt><span class="section"><a href="#_installation">3. Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#_requirements">3.1. Requirements</a></span></dt><dt><span class="section"><a href="#install_process">3.2. Install process</a></span></dt></dl></dd><dt><span class="section"><a href="#_calcurse_basics">4. calcurse basics</a></span></dt><dd><dl><dt><span class="section"><a href="#_invocation">4.1. Invocation</a></span></dt><dt><span class="section"><a href="#_user_interface">4.2. User interface</a></span></dt><dt><span class="section"><a href="#basics_daemon">4.3. Background mode</a></span></dt><dt><span class="section"><a href="#basics_files">4.4. calcurse files</a></span></dt><dt><span class="section"><a href="#_import_export_capabilities">4.5. Import/Export capabilities</a></span></dt><dt><span class="section"><a href="#_online_help">4.6. Online help</a></span></dt></dl></dd><dt><span class="section"><a href="#_options">5. Options</a></span></dt><dd><dl><dt><span class="section"><a href="#options_general">5.1. General options</a></span></dt><dt><span class="section"><a href="#options_keys">5.2. Key bindings</a></span></dt><dt><span class="section"><a href="#_color_themes">5.3. Color themes</a></span></dt><dt><span class="section"><a href="#_layout_configuration">5.4. Layout configuration</a></span></dt><dt><span class="section"><a href="#_sidebar_configuration">5.5. Sidebar configuration</a></span></dt><dt><span class="section"><a href="#options_notify">5.6. Notify-bar settings</a></span></dt></dl></dd><dt><span class="section"><a href="#_known_bugs">6. Known bugs</a></span></dt><dt><span class="section"><a href="#bugs">7. Reporting bugs and feedback</a></span></dt><dt><span class="section"><a href="#contribute">8. How to contribute?</a></span></dt><dd><dl><dt><span class="section"><a href="#_translating_documentation">8.1. Translating documentation</a></span></dt><dt><span class="section"><a href="#_calcurse_i18n">8.2. calcurse i18n</a></span></dt></dl></dd><dt><span class="section"><a href="#_links">9. Links</a></span></dt><dd><dl><dt><span class="section"><a href="#_calcurse_homepage">9.1. calcurse homepage</a></span></dt><dt><span class="section"><a href="#_calcurse_announce_list">9.2. calcurse announce list</a></span></dt><dt><span class="section"><a href="#links_others">9.3. Other links</a></span></dt></dl></dd><dt><span class="section"><a href="#_thanks">10. Thanks</a></span></dt></dl></div><div class="abstract"><a id="_abstract"></a><div class="titlepage"></div><p>This manual describes <code class="literal">calcurse</code> functionalities, and how to use them. The
installation from source is first described, together with the available
command line arguments. The user interface is then presented, with all of the
customizable options that change <code class="literal">calcurse</code> behavior. Last, bug reporting
procedure is explained, as well as the way one can contribute to <code class="literal">calcurse</code>
development.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_introduction"></a>1. Introduction</h2></div></div></div><p><code class="literal">calcurse</code> is a text-based calendar and scheduling application. It helps
keeping track of events, appointments and everyday tasks.  A configurable
notification system reminds user of upcoming deadlines, and the curses based
interface can be customized to suit user needs.  All of the commands are
documented within an online help system.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_overview"></a>2. Overview</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_creation_history"></a>2.1. Creation history</h3></div></div></div><p>I started thinking about this project when I was finishing my Ph.D.  in
Astrophysics… It started to be a little hard to organize myself, and I really
needed a good tool to help me in that difficult task ;)</p><p>I like programs which use Text User Interfaces, because they are simple, fast,
portable and efficient, so I thought about working on coding a simple calendar
using such an interface.  Moreover, I wanted to go on learning the <code class="literal">C</code>
language, which I only used for a while during my undergraduate studies. So I
thought that would be the good project to start in order to get organized and
to learn about a few <code class="literal">C</code> things !</p><p>Unfortunately, I finished my Ph.D. before finishing <code class="literal">calcurse</code>, but anyway, I
still wanted to work on it, hoping it would be helpful to other people.  So
here it is…</p><p>But why <span class="emphasis"><em>calcurse</em></span> anyway ?  Well, it is simply the concatenation of <span class="emphasis"><em>CALendar</em></span>
and <span class="emphasis"><em>nCURSEs</em></span>, the name of the library used to build the user interface.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_important_features"></a>2.2. Important features</h3></div></div></div><p><code class="literal">Calcurse</code> is multi-platform and intended to be lightweight, fast and reliable.
It is to be used inside a console or terminal, locally or on a distant machine
within an ssh (or similar) connection.</p><p><code class="literal">Calcurse</code> can be run in two different modes : interactive or non-interactive
mode. The first mode allows oneself to view its own personal organizer almost
everywhere, thanks to the text-based interface.  The second mode permits to
easily build reminders just by adding <code class="literal">calcurse</code> with appropriate command line
arguments inside a cron tab or within a shell init script.</p><p>Moreover, <code class="literal">calcurse</code> was created with the end-user in mind, and tends to be as
friendly as possible. This means a complete on-line help system, together with
having all of the possible actions displayed at any time inside a status bar.
The user interface is configurable, and one can choose between several color
and layout combinations.  Key bindings are also configurable, to fit everyone’s
needs.  Last, a configurable notification system reminds user of upcoming
appointments. The reminders are sent even if the user’s interface is not
running, as calcurse is able to run in background.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_installation"></a>3. Installation</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_requirements"></a>3.1. Requirements</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_ncurses_library"></a>ncurses library</h4></div></div></div><p><code class="literal">Calcurse</code> requires only a <code class="literal">C</code> compiler, such as <code class="literal">cc</code> or <code class="literal">gcc</code>, and the
<code class="literal">ncurses</code> library.  It would be very surprising not to have a valid <code class="literal">ncurses</code>
library already installed on your computer, but if not, you can find it at the
following url: <a class="ulink" href="http://ftp.gnu.org/pub/gnu/ncurses/" target="_top">http://ftp.gnu.org/pub/gnu/ncurses/</a></p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>It is also possible to link <code class="literal">calcurse</code> against the <code class="literal">ncursesw</code> library
      (ncurses with support for unicode).</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="install_requirements_gettext"></a>gettext library</h4></div></div></div><p><code class="literal">calcurse</code> supports internationalization (<span class="strong"><strong>i18n</strong></span> hereafter) through the
<code class="literal">gettext</code> utilities. This means <code class="literal">calcurse</code> can produce multi-lingual messages
if compiled with native language support (i.e. <span class="strong"><strong>NLS</strong></span>).</p><p>However, <span class="strong"><strong>NLS</strong></span> is optionnal and if you do not want to have support for
multi-lingual messages, you can disable this feature.  This is done by giving
the <code class="literal">--disable-nls</code> option to <code class="literal">configure</code> (see section
<a class="link" href="#install_process" title="3.2. Install process">Install process</a>).  To check if the <code class="literal">gettext</code> utilities are
installed on your system, you can search for the <code class="literal">libintl.h</code> header file for
instance:</p><pre class="screen">$ locate libintl.h</pre><p>If this header file is not found, then you can obtain the <code class="literal">gettext</code> sources at
the following url : <a class="ulink" href="http://ftp.gnu.org/pub/gnu/gettext/" target="_top">http://ftp.gnu.org/pub/gnu/gettext/</a></p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>Even if <code class="literal">libintl.h</code> is found on your system, it can be wise to specify
      its location during the <a class="link" href="#install_process" title="3.2. Install process">install process</a>, by using the
      <code class="literal">--with-libintl-prefix</code> option with <code class="literal">configure</code>. Indeed, the <code class="literal">configure</code>
      could fail to locate this library if installed in an uncommon place.</p></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="install_process"></a>3.2. Install process</h3></div></div></div><p>First you need to gunzip and untar the source archive:</p><pre class="screen">$ tar zxvf calcurse-3.0.0.tar.gz</pre><p>Once you meet the requirements and have extracted the archive, the install
process is quite simple, and follows the standard three steps process:</p><pre class="screen">$ ./configure
$ make
$ make install    # (may require root privilege)</pre><p>Use <code class="literal">./configure --help</code> to obtain a list of possible options.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_calcurse_basics"></a>4. calcurse basics</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_invocation"></a>4.1. Invocation</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="basics_invocation_commandline"></a>Command line arguments</h4></div></div></div><p><code class="literal">calcurse</code> takes the following options from the command line (both short and
long options are supported):</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">-a, --appointment</code>
</span></dt><dd>
  Print the appointments and events for the current day and exit.  The calendar
  from which to read the  appointments can be specified using the <code class="literal">-c</code> flag.
</dd><dt><span class="term">
<code class="literal">-c &lt;file&gt;, --calendar &lt;file&gt;</code>
</span></dt><dd>
  Specify the calendar file to use.  The default  calendar is
  <code class="literal">~/.calcurse/apts</code> (see section <a class="link" href="#basics_files" title="4.4. calcurse files">calcurse files</a>).
</dd><dt><span class="term">
<code class="literal">-d &lt;date|num&gt;, --day &lt;date|num&gt;</code>
</span></dt><dd><p class="simpara">
  Print the appointments for the given date  or  for  the given  number  of
  upcoming days, depending on the argument format. Two possible formats are
  supported:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
a date (possible formats described below).
</li><li class="listitem">
a number <code class="literal">n</code>.
</li></ul></div><p class="simpara">In the first  case,  the  appointment  list  for  the specified  date will be
returned, while in the second case the appointment list for the <code class="literal">n</code>  upcoming
days will be returned.  As an example, typing <code class="literal">calcurse -d  3</code>  will  display
your  appointments  for  today, tomorrow, and the day after tomorrow.  Possible
formats for specifying the date are defined inside the general configuration
menu (see <a class="link" href="#options_general" title="5.1. General options">General options</a>), using the
<code class="literal">format.inputdate</code> variable.</p><p class="simpara">Note: as for the <code class="literal">-a</code> flag, the calendar  from which to  read  the appointments
can be specified using the <code class="literal">-c</code> flag.</p></dd><dt><span class="term">
<code class="literal">-D &lt;dir&gt;, --directory &lt;dir&gt;</code>
</span></dt><dd>
  Specify  the  data directory to use. This option is incompatible  with  -c.
  If  not  specified,   the default directory is <code class="literal">~/.calcurse/</code>.
</dd><dt><span class="term">
<code class="literal">--format-apt &lt;format&gt;</code>
</span></dt><dd>
  Specify a format to control the output of appointments in non-interactive
  mode. See the <a class="link" href="#basics_format_strings" title="Format strings">Format strings</a> section for detailed
  information on format strings.
</dd><dt><span class="term">
<code class="literal">--format-recur-apt &lt;format&gt;</code>
</span></dt><dd>
  Specify a format to control the output of recurrent appointments in
  non-interactive mode. See the <a class="link" href="#basics_format_strings" title="Format strings">Format strings</a>
  section for detailed information on format strings.
</dd><dt><span class="term">
<code class="literal">--format-event &lt;format&gt;</code>
</span></dt><dd>
  Specify a format to control the output of events in non-interactive mode. See
  the <a class="link" href="#basics_format_strings" title="Format strings">Format strings</a> section for detailed information
  on format strings.
</dd><dt><span class="term">
<code class="literal">--format-recur-event &lt;format&gt;</code>
</span></dt><dd>
  Specify a format to control the output of recurrent events in non-interactive
  mode. See the <a class="link" href="#basics_format_strings" title="Format strings">Format strings</a> section for detailed
  information on format strings.
</dd><dt><span class="term">
<code class="literal">--format-todo &lt;format&gt;</code>
</span></dt><dd>
  Specify a format to control the output of todo items in non-interactive mode.
  See the <a class="link" href="#basics_format_strings" title="Format strings">Format strings</a> section for detailed
  information on format strings.
</dd><dt><span class="term">
<code class="literal">-g, --gc</code>
</span></dt><dd>
  Run the garbage collector for note files and exit.
</dd><dt><span class="term">
<code class="literal">-h, --help</code>
</span></dt><dd>
  Print  a  short  help  text  describing  the  supported command-line options,
  and exit.
</dd><dt><span class="term">
<code class="literal">-i &lt;file&gt;, --import &lt;file&gt;</code>
</span></dt><dd>
  Import the icalendar data contained in <code class="literal">file</code>.
</dd><dt><span class="term">
<code class="literal">-n, --next</code>
</span></dt><dd><p class="simpara">
  Print the next appointment within upcoming 24 hours and exit.  The indicated
  time is the number of hours and minutes left before this appointment.
</p><p class="simpara">Note: the calendar from which to read the appointments can be specified using
the <code class="literal">-c</code> flag.</p></dd><dt><span class="term">
<code class="literal">-r[num], --range[=num]</code>
</span></dt><dd>
  Print events and appointments for the num number of days and exit. If no num
  is given, a range of 1 day is considered.
</dd><dt><span class="term">
<code class="literal">--read-only</code>
</span></dt><dd><p class="simpara">
  Don’t save configuration nor appointments/todos.
</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Use this this with care! If you run an interactive calcurse instance
in read-only mode, all changes from this session will be lost without warning!</p></div></dd><dt><span class="term">
<code class="literal">-s[date], --startday[=date]</code>
</span></dt><dd>
  Print  events  and appointments from date and exit.  If no date is given, the
  current day is considered.
</dd><dt><span class="term">
<code class="literal">-S&lt;regex&gt;, --search=&lt;regex&gt;</code>
</span></dt><dd>
  When used with the <code class="literal">-a</code>, <code class="literal">-d</code>, <code class="literal">-r</code>, <code class="literal">-s</code>, or <code class="literal">-t</code> flag, print only the items
  having a description that matches the given regular expression.
</dd><dt><span class="term">
<code class="literal">--status</code>
</span></dt><dd>
  Display  the  status of running instances of calcurse. If calcurse is
  running, this will tell  if  the  interactive mode  was  launched  or  if
  calcurse is running in background.  The process pid will also be indicated.
</dd><dt><span class="term">
<code class="literal">-t[num], --todo[=num]</code>
</span></dt><dd>
  Print the <code class="literal">todo</code> list and exit. If the optional number <code class="literal">num</code> is given, then
  only todos having a priority equal to <code class="literal">num</code> will be returned. The priority
  number must be between 1 (highest) and 9 (lowest). It is also possible to
  specify <code class="literal">0</code> for the priority, in which case only completed tasks will be
  shown.
</dd><dt><span class="term">
<code class="literal">-v, --version</code>
</span></dt><dd>
  Display <code class="literal">calcurse</code> version and exit.
</dd><dt><span class="term">
<code class="literal">-x[format], --export[=format]</code>
</span></dt><dd><p class="simpara">
  Export user data to specified format. Events, appointments and todos are
  converted and echoed to stdout.  Two possible formats are available: ical and
  pcal (see section <a class="link" href="#links_others" title="9.3. Other links">Links</a> below).  If the optional
  argument <code class="literal">format</code> is not given, ical format is selected by default.
</p><p class="simpara">Note: redirect standard output to export data to a file, by issuing a command
such as:</p><pre class="screen">$ calcurse --export &gt; my_data.dat</pre></dd></dl></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>The <code class="literal">-N</code> option has been removed in calcurse 3.0.0. See the
<a class="link" href="#basics_format_strings" title="Format strings">Format strings</a> section on how to print note along
with appointments and events.</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="basics_format_strings"></a>Format strings</h4></div></div></div><p>Format strings are composed of printf()-style format specifiers — ordinary
characters are copied to stdout without modification. Each specifier is
introduced by a <code class="literal">%</code> and is followed by a character which specifies the field to
print. The set of available fields depends on the item type.</p><div class="section"><div class="titlepage"><div><div><h5 class="title"><a id="_format_specifiers_for_appointments"></a>Format specifiers for appointments</h5></div></div></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">s</code>
</span></dt><dd>
  Print the start time of the appointment as UNIX time stamp
</dd><dt><span class="term">
<code class="literal">S</code>
</span></dt><dd>
  Print the start time of the appointment using the <code class="literal">hh:mm</code> format
</dd><dt><span class="term">
<code class="literal">d</code>
</span></dt><dd>
  Print the duration of the appointment in seconds
</dd><dt><span class="term">
<code class="literal">e</code>
</span></dt><dd>
  Print the end time of the appointment as UNIX time stamp
</dd><dt><span class="term">
<code class="literal">E</code>
</span></dt><dd>
  Print the end time of the appointment using the <code class="literal">hh:mm</code> format
</dd><dt><span class="term">
<code class="literal">m</code>
</span></dt><dd>
  Print the description of the item
</dd><dt><span class="term">
<code class="literal">n</code>
</span></dt><dd>
  Print the name of the note file belonging to the item
</dd><dt><span class="term">
<code class="literal">N</code>
</span></dt><dd>
  Print the note belonging to the item
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a id="_format_specifiers_for_events"></a>Format specifiers for events</h5></div></div></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">m</code>
</span></dt><dd>
  Print the description of the item
</dd><dt><span class="term">
<code class="literal">n</code>
</span></dt><dd>
  Print the name of the note file belonging to the item
</dd><dt><span class="term">
<code class="literal">N</code>
</span></dt><dd>
  Print the note belonging to the item
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a id="_format_specifiers_for_todo_items"></a>Format specifiers for todo items</h5></div></div></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">p</code>
</span></dt><dd>
  Print the priority of the item
</dd><dt><span class="term">
<code class="literal">m</code>
</span></dt><dd>
  Print the description of the item
</dd><dt><span class="term">
<code class="literal">n</code>
</span></dt><dd>
  Print the name of the note file belonging to the item
</dd><dt><span class="term">
<code class="literal">N</code>
</span></dt><dd>
  Print the note belonging to the item
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a id="_examples"></a>Examples</h5></div></div></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">calcurse -r7 --format-apt='- %S -&gt; %E\n\t%m\n%N'</code>
</span></dt><dd>
  Print appointments and events for the next seven days. Also, print the notes
  attached to each regular appointment (simulates <code class="literal">-N</code> for appointments).
</dd><dt><span class="term">
<code class="literal">calcurse -r7 --format-apt=' - %m (%S to %E)\n' --format-recur-apt=' - %m (%S to %E)\n'</code>
</span></dt><dd>
  Print appointments and events for the next seven days and use a custom format
  for (recurrent) appointments: ` - Some appointment (18:30 to 21:30)`.
</dd><dt><span class="term">
<code class="literal">calcurse -t --format-todo '(%p) %m\n'</code>
</span></dt><dd>
  List all todo items and put parentheses around the priority specifiers.
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a id="_extended_format_specifiers"></a>Extended format specifiers</h5></div></div></div><p>Extended format specifiers can be used if you want to specify advanced
formatting options. Extended specifiers are introduced by <code class="literal">%(</code> and are
terminated by a closing parenthesis (<code class="literal">)</code>). The following list includes all
short specifiers and corresponding long options:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<code class="literal">s</code>: <code class="literal">(start)</code>
</li><li class="listitem">
<code class="literal">S</code>: <code class="literal">(start:epoch)</code>
</li><li class="listitem">
<code class="literal">d</code>: <code class="literal">(duration)</code>
</li><li class="listitem">
<code class="literal">e</code>: <code class="literal">(end)</code>
</li><li class="listitem">
<code class="literal">E</code>: <code class="literal">(end:epoch)</code>
</li><li class="listitem">
<code class="literal">m</code>: <code class="literal">(message)</code>
</li><li class="listitem">
<code class="literal">n</code>: <code class="literal">(noteid)</code>
</li><li class="listitem">
<code class="literal">N</code>: <code class="literal">(note)</code>
</li><li class="listitem">
<code class="literal">p</code>: <code class="literal">(priority)</code>
</li></ul></div><p>The <code class="literal">(start)</code> and <code class="literal">(end)</code> specifiers support strftime()-style extended
formatting options that can be used for fine-grained formatting. Additionally,
the special formats <code class="literal">epoch</code> (which is equivalent to <code class="literal">(start:%s)</code> or <code class="literal">(end:%s)</code>)
and <code class="literal">default</code> (which is mostly equivalent to <code class="literal">(start:%H:%M)</code> or <code class="literal">(end:%H:%M)</code>
but displays <code class="literal">..:..</code> if the item doesn’t start/end at the current day) are
supported.</p></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="basics_invocation_variable"></a>Environment variable for i18n</h4></div></div></div><p><code class="literal">calcurse</code> can be compiled with native language support (see
<a class="link" href="#install_requirements_gettext" title="gettext library">gettext library</a>). Thus, if you wish to have
messages displayed into your native language, first make sure it is available
by looking at the <code class="literal">po/LINGUAS</code> file.  This file indicates the set of available
languages by showing the two-letters corresponding code (for exemple, <span class="strong"><strong>fr</strong></span>
stands for french).  If you do not find your language, it would be greatly
appreciated if you could help translating <code class="literal">calcurse</code> (see the <a class="link" href="#contribute" title="8. How to contribute?">How to contribute?</a> section).</p><p>If your language is available, run <code class="literal">calcurse</code> with the following command:</p><pre class="screen">$ LC_ALL=fr_FR calcurse</pre><div class="orderedlist"><ol class="orderedlist" type="i"><li class="listitem">
where <span class="strong"><strong>fr_FR</strong></span> is the locale name in this exemple, but should be replaced by
the locale corresponding to the desired language.
</li></ol></div><p>You should also specify the charset to be used, because in some cases the
accents and such are not displayed correctly.  This charset is indicated at the
beginning of the po file corresponding to the desired language. For instance,
you can see in the fr.po file that it uses the iso-8859-1 charset, so you could
run <code class="literal">calcurse</code> using the following command:</p><pre class="screen">$ LC_ALL=fr_FR.ISO8859-1 calcurse</pre></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_other_environment_variables"></a>Other environment variables</h4></div></div></div><p>The following environment variables affect the way <code class="literal">calcurse</code> operates:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">VISUAL</code>
</span></dt><dd>
  Specifies the external editor to use for writing notes.
</dd><dt><span class="term">
<code class="literal">EDITOR</code>
</span></dt><dd>
  If the <code class="literal">VISUAL</code> environment variable is not set, then <code class="literal">EDITOR</code> will be used
  as the default external editor. If none of those variables are set, then
  <code class="literal">/usr/bin/vi</code> is used instead.
</dd><dt><span class="term">
<code class="literal">PAGER</code>
</span></dt><dd>
  Specifies the default viewer to be used for reading notes.  If this variable
  is not set, then <code class="literal">/usr/bin/less</code> is used.
</dd></dl></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_user_interface"></a>4.2. User interface</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_non_interactive_mode"></a>Non-interactive mode</h4></div></div></div><p>When called with at least one of the following arguments: <code class="literal">-a</code>, <code class="literal">-d</code>, <code class="literal">-h</code>,
<code class="literal">-n</code>, <code class="literal">-t</code>, <code class="literal">-v</code>, <code class="literal">-x</code>, <code class="literal">calcurse</code> is started in non-interactive mode.  This
means the desired information will be displayed, and after that, <code class="literal">calcurse</code>
simply quits and you are driven back to the shell prompt.</p><p>That way, one can add a line such as <code class="literal">calcurse --todo --appointment</code> in its
init config file to display at logon the list of tasks and appointments
scheduled for the current day.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="basics_interface_interactive"></a>Interactive mode</h4></div></div></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>Key bindings that are indicated in this manual correspond to the default
      ones, defined when <code class="literal">calcurse</code> is launched for the first time. If those
      key bindings do not suit user’s needs, it is possible to change them
      within the keys configuration menu (see <a class="link" href="#options_keys" title="5.2. Key bindings">key bindings</a>).</p></div><p>When called without any argument or only with the <code class="literal">-c</code> option, <code class="literal">calcurse</code> is
started in interactive mode. In this mode, you are shown an interface
containing three different panels which you can browse using the <code class="literal">TAB</code> key,
plus a notification bar and a status bar (see figure below).</p><pre class="screen"> appointment panel---.                                   .---calendar panel
                     |                                   |
                     v                                   v
 +------------------------------------++----------------------------+
 |          Appointments              ||          Calendar          |
 |------------------------------------||----------------------------|
 |                 (|)  April 6, 2006 ||         April 2006         |
 |                                    ||Mon Tue Wed Thu Fri Sat Sun |
 |                                    ||                      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 |
 |                                    ||                            |
 |                                    |+----------------------------+
 |                                    |+----------------------------+
 |                                    ||            ToDo            | todo
 |                                    ||----------------------------| panel
 |                                    ||                            |   |
 |                                    ||                            |   |
 |                                    ||                            |&lt;--.
 |                                    ||                            |
 +------------------------------------++----------------------------+
 |---[ Mon 2006-11-22 | 10:11:43 ]---(apts)----&gt; 01:20 :: lunch &lt;---|&lt;--.
 +------------------------------------------------------------------+ notify-bar
 | ? Help     R Redraw    H/L -/+1 Day      G GoTo       C Config   |
 | Q Quit     S Save      J/K -/+1 Week   Tab Chg View              |&lt;-.
 +------------------------------------------------------------------+  |
                                                                       |
                                                                 status bar</pre><p>The first panel represents a calendar which allows to highlight a particular
day, the second one contains the list of the events and appointments on that
day, and the last one contains a list of tasks to do but which are not assigned
to any specific day.</p><p>Depending on the selected view, the calendar could either display a monthly
(default as shown in previous figure) or weekly view.  The weekly view would
look like the following:</p><pre class="screen">+------------------------------------+
|              Calendar              |
|----------------------------(# 13)--|
|    Mon Tue Wed Thu Fri Sat Sun     |
|     29  30  31  01  02  03  04     |
|                               &lt;----+--  slice 1: 00:00 to 04:00 AM
|       --  --  --  --  --  --       |
|                               &lt;----+--  slice 2: 04:00 to 08:00 AM
|       --  --  --  --  --  --       |
|                               &lt;----+--  slice 3: 08:00 to 12:00 AM
|    -  --  --  --  --  --  --  -  &lt;-+--  midday
|                               &lt;----+--  slice 4: 12:00 to 04:00 PM
|       --  --  --  --  --  --       |
|                               &lt;----+--  slice 5: 04:00 to 08:00 PM
|       --  --  --  --  --  --       |
|                               &lt;----+--  slice 6: 08:00 to 12:00 PM
+------------------------------------+</pre><p>The current week number is displayed on the top-right side of the panel (<span class="strong"><strong># 13</strong></span>
meaning it is the 13th week of the year in the above example). The seven days
of the current week are displayed in column. Each day is divided into slices of
4 hours each (6 slices in total, see figure above). A slice will appear in a
different color if an appointment falls into the corresponding time-slot.</p><p>In the appointment panel, one can notice the <span class="strong"><strong><code class="literal">(|)</code></strong></span> sign just in front of the
date.  This indicates the current phase of the moon.  Depending on which is the
current phase, the following signs can be seen:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
`  |) `
</span></dt><dd>
  first quarter
</dd><dt><span class="term">
` (|) `
</span></dt><dd>
  full moon
</dd><dt><span class="term">
`  (| `
</span></dt><dd>
  last quarter
</dd><dt><span class="term">
`  |  `
</span></dt><dd>
  new moon
</dd><dt><span class="term">
no sign
</span></dt><dd>
  Phase of the moon does not correspond to any of the above ones.
</dd></dl></div><p>At the very bottom of the screen there is a status bar, which indicates the
possible actions and the corresponding keystrokes.</p><p>Just above this status bar is the notify-bar, which indicates from left to
right : the current date, the current time, the calendar file currently in use
(apts on the above example, which is the default calendar file, see the
following section), and the next appointment within the upcoming 24 hours. Here
it says that it will be lunch time in one hour and twenty minutes.</p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>Some actions, such as editing or adding an item, require to type in some
      text. This is done with the help of the built-in input line editor.</p></div><p>Within this editor, if a line is longer than the screen width, a <code class="literal">&gt;</code>, <code class="literal">*</code>, or
<code class="literal">&lt;</code> character is displayed in the last column indicating that there are more
character after, before and after, or before the current position,
respectively. The line is scrolled horizontally as necessary.</p><p>Moreover, some editing commands are bound to particular control characters.
Hereafter are indicated the available editing commands (<code class="literal">^</code> stands for the
control key):</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">^a</code>
</span></dt><dd>
  moves the cursor to the beginning of the input line
</dd><dt><span class="term">
<code class="literal">^b</code>
</span></dt><dd>
  moves the cursor backward
</dd><dt><span class="term">
<code class="literal">^d</code>
</span></dt><dd>
  deletes one character forward
</dd><dt><span class="term">
<code class="literal">^e</code>
</span></dt><dd>
  moves the cursor to the end of the input line
</dd><dt><span class="term">
<code class="literal">^f</code>
</span></dt><dd>
  moves the cursor forward
</dd><dt><span class="term">
<code class="literal">^h</code>
</span></dt><dd>
  deletes one character backward
</dd><dt><span class="term">
<code class="literal">^k</code>
</span></dt><dd>
  deletes the input from the cursor to the end of the line
</dd><dt><span class="term">
<code class="literal">^w</code>
</span></dt><dd>
  deletes backward to the beginning of the current word
</dd><dt><span class="term">
<code class="literal">ESCAPE</code>
</span></dt><dd>
    cancels the editing
</dd></dl></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="basics_daemon"></a>4.3. Background mode</h3></div></div></div><p>When the daemon mode is enabled in the notification configuration menu (see
<a class="link" href="#options_notify" title="5.6. Notify-bar settings">Notify-bar settings</a>), <code class="literal">calcurse</code> will stay in background
when the user interface is not running. In background mode, <code class="literal">calcurse</code> checks
for upcoming appointments and runs the user-defined notification command when
  necessary. When the user interface is started again, the daemon automatically
  stops.</p><p>‘calcurse` background activity can be logged (set the <code class="literal">daemon.log</code> variable in
the notification configuration <a class="link" href="#options_notify" title="5.6. Notify-bar settings">menu</a>), and in that case,
information about the daemon start and stop time, reminders’ command launch
time, signals received… will be written in the <code class="literal">daemon.log</code> file (see section
<a class="link" href="#basics_files" title="4.4. calcurse files">files</a>).</p><p>Using the <code class="literal">--status</code> command line option (see section
<a class="link" href="#basics_invocation_commandline" title="Command line arguments">Command line arguments</a>), one can know if
<code class="literal">calcurse</code> is currently running in background or not.  If the daemon is
running, a message like the following one will be displayed (the pid of the
daemon process will be shown):</p><pre class="screen">calcurse is running in background (pid 14536)</pre><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>To stop the daemon, just send the <code class="literal">TERM</code> signal to it, using a command
      such as: <code class="literal">kill daemon_pid</code>, where <span class="strong"><strong>daemon_pid</strong></span> is the process id of the
      daemon (14536 in the above example).</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="basics_files"></a>4.4. calcurse files</h3></div></div></div><p>The following structure is created in your <code class="literal">$HOME</code>  directory (or in the
directory you specified with  the  -D  option) the first time <code class="literal">calcurse</code> is run
:</p><pre class="screen">$HOME/.calcurse/
           |___notes/
           |___conf
           |___keys
           |___apts
           |___todo</pre><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">notes/</code>
</span></dt><dd>
  this subdirectory contains descriptions of the notes which are attached to
  appointments, events or todos. Since the file name of each note file is a
  SHA1 hash of the note itself, multiple items can share the same note file.
  calcurse provides a garbage collector (see the <code class="literal">-g</code> command line parameter)
  that can be used to remove note files which are no longer linked to any item.
</dd><dt><span class="term">
<code class="literal">conf</code>
</span></dt><dd>
  this file contains the user configuration
</dd><dt><span class="term">
<code class="literal">keys</code>
</span></dt><dd>
  this file contains the user-defined key bindings
</dd><dt><span class="term">
<code class="literal">apts</code>
</span></dt><dd>
  this file contains  all  of the events and user’s appointments
</dd><dt><span class="term">
<code class="literal">todo</code>
</span></dt><dd>
  this file contains the todo list
</dd></dl></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>If the logging of calcurse daemon activity was set in the notification
      configuration menu, the extra file <code class="literal">daemon.log</code> will appear in calcurse
      data directory. This file contains logs about calcurse activity when
      running in background.</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_import_export_capabilities"></a>4.5. Import/Export capabilities</h3></div></div></div><p>The import and export capabilities offered by <code class="literal">calcurse</code> are described below.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_import"></a>Import</h4></div></div></div><p>Data in icalendar format as described in the rfc2445 specification (see
<a class="link" href="#links_others" title="9.3. Other links">links</a> section below) can be imported into calcurse.  Calcurse
ical parser is based on version 2.0 of this specification, but for now on, only
a subset of it is supported.</p><p>The following icalendar properties are handled by calcurse:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<code class="literal">VTODO</code> items: "PRIORITY", "VALARM", "SUMMARY", "DESCRIPTION"
</li><li class="listitem">
<code class="literal">VEVENT</code> items: "DTSTART", "DTEND", "DURATION", "RRULE", "EXDATE", "VALARM",
  "SUMMARY", "DESCRIPTION"
</li></ul></div><p>The icalendar <code class="literal">DESCRIPTION</code> property will be converted into calcurse format by
adding a note to the item. If a "VALARM" property is found, the item will be
flagged as important and the user will get a notification (this is only
applicable to appointments).</p><p>Here are the properties that are not implemented:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
negative time durations are not taken into account (item is skipped)
</li><li class="listitem">
some recurence frequences are not recognize: "SECONDLY" / "MINUTELY" /
  "HOURLY"
</li><li class="listitem">
some recurrence keywords are not recognized (all those starting with <code class="literal">BY</code>):
  "BYSECOND" / "BYMINUTE" / "BYHOUR" / "BYDAY" / "BYMONTHDAY" / "BYYEARDAY" /
  "BYWEEKNO" / "BYMONTH" / "BYSETPOS" plus "WKST"
</li><li class="listitem">
the recurrence exception keyword "EXRULE" is not recognized
</li><li class="listitem">
timezones are not taken into account
</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_export"></a>Export</h4></div></div></div><p>Two possible export formats are available: <code class="literal">ical</code> and <code class="literal">pcal</code> (see section
<a class="link" href="#links_others" title="9.3. Other links">Links</a> below to find out about those formats).</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_online_help"></a>4.6. Online help</h3></div></div></div><p>At any time, the built-in help  system  can  be  invoked  by pressing the <code class="literal">?</code>
key. Once viewing the help screens, informations on a specific command can be
accessed  by  pressing the keystroke corresponding to that command.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_options"></a>5. Options</h2></div></div></div><p>All of the <code class="literal">calcurse</code> parameters are configurable from the Configuration menu
available when pressing <code class="literal">C</code>. You are then driven to a submenu with five
possible choices : pressing <code class="literal">C</code> again will lead you to the Color scheme
configuration, pressing <code class="literal">L</code> allows you to choose the layout of the main
<code class="literal">calcurse</code> screen (in other words, where to put the three different panels on
screen), pressing <code class="literal">G</code> permits you to choose between different general options,
pressing <code class="literal">K</code> opens the key bindings configuration menu, and last you can modify
the notify-bar settings by pressing <code class="literal">N</code>.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="options_general"></a>5.1. General options</h3></div></div></div><p>These options control <code class="literal">calcurse</code> general behavior, as described below:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">general.autosave</code> (default: <span class="strong"><strong>yes</strong></span>)
</span></dt><dd>
  This option allows to automatically save the user’s data (if set to <span class="strong"><strong>yes</strong></span>)
  when quitting.  &lt;p class="rq"&gt;&lt;span class="valorise"&gt;warning:&lt;/span&gt; No data
  will be automatically saved if <code class="literal">general.autosave</code> is set to <span class="strong"><strong>no</strong></span>.  This means
  the user must press <code class="literal">S</code> (for saving) in order to retrieve its modifications.
</dd><dt><span class="term">
<code class="literal">general.autogc</code> (default: <span class="strong"><strong>no</strong></span>)
</span></dt><dd>
  Automatically run the garbage collector for note files when quitting.
</dd><dt><span class="term">
<code class="literal">general.periodicsave</code> (default: <span class="strong"><strong>0</strong></span>)
</span></dt><dd>
  If different from <code class="literal">0</code>, user’s data will be automatically saved every
  <span class="strong"><strong>general.periodicsave</strong></span> minutes.  When an automatic save is performed, two
  asterisks (i.e. <code class="literal">**</code>) will appear on the top right-hand side of the screen).
</dd><dt><span class="term">
<code class="literal">general.confirmquit</code> (default: <span class="strong"><strong>yes</strong></span>)
</span></dt><dd>
  If set to <span class="strong"><strong>yes</strong></span>, confirmation is required before quitting, otherwise pressing
  <code class="literal">Q</code> will cause <code class="literal">calcurse</code> to quit without prompting for user confirmation.
</dd><dt><span class="term">
<code class="literal">general.confirmdelete</code> (default: <span class="strong"><strong>yes</strong></span>)
</span></dt><dd>
  If this option is set to <span class="strong"><strong>yes</strong></span>, pressing <code class="literal">D</code> for deleting an item (either a
  <span class="strong"><strong>todo</strong></span>, <span class="strong"><strong>appointment</strong></span>, or <span class="strong"><strong>event</strong></span>), will lead to a prompt asking for user
  confirmation before removing the selected item from the list.  Otherwise, no
  confirmation will be needed before deleting the item.
</dd><dt><span class="term">
<code class="literal">general.systemdialogs</code> (default: <span class="strong"><strong>yes</strong></span>)
</span></dt><dd>
  Setting this option to <span class="strong"><strong>no</strong></span> will result in skipping the system dialogs
  related to the saving and loading of data.  This can be useful to speed up
  the input/output processes.
</dd><dt><span class="term">
<code class="literal">general.progressbar</code> (default: <span class="strong"><strong>yes</strong></span>)
</span></dt><dd>
  If set to <span class="strong"><strong>no</strong></span>, this will cause the disappearing of the progress bar which is
  usually shown when saving data to file.  If set to <span class="strong"><strong>yes</strong></span>, this bar will be
  displayed, together with the name of the file being saved (see section
  <a class="link" href="#basics_files" title="4.4. calcurse files">calcurse files</a>).
</dd><dt><span class="term">
<code class="literal">appearance.calendarview</code> (default: <span class="strong"><strong>0</strong></span>)
</span></dt><dd>
  If set to <code class="literal">0</code>, the monthly calendar view will be displayed by default
  otherwise it is the weekly view that will be displayed.
</dd><dt><span class="term">
<code class="literal">general.firstdayofweek</code> (default: <span class="strong"><strong>monday</strong></span>)
</span></dt><dd>
  One can choose between Monday and Sunday as the first day of the week. If
  <code class="literal">general.firstdayofweek</code> is set to <span class="strong"><strong>monday</strong></span>, Monday will be first in the
  calendar view. Otherwise, Sunday will be the first day of the week.
</dd><dt><span class="term">
<code class="literal">format.outputdate</code> (default: <span class="strong"><strong>%D</strong></span>)
</span></dt><dd>
  This option indicates the format to be used when displaying dates in
  non-interactive mode. Using the default values, dates are displayed the
  following way: <span class="strong"><strong>mm/dd/aa</strong></span>.  You can see all of the possible formats by typing
  <code class="literal">man 3 strftime</code> inside a terminal.
</dd><dt><span class="term">
<code class="literal">format.inputdate</code> (default: <span class="strong"><strong>1</strong></span>)
</span></dt><dd><p class="simpara">
  This option indicates the format that will be used to enter dates in
  <span class="strong"><strong>calcurse</strong></span>. Four choices are available:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
mm/dd/yyyy
</li><li class="listitem">
dd/mm/yyyy
</li><li class="listitem">
yyyy/mm/dd
</li><li class="listitem">
yyyy-mm-dd
</li></ol></div></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="options_keys"></a>5.2. Key bindings</h3></div></div></div><p>One can define ones own key bindings within the <code class="literal">Keys</code> configuration menu. The
default keys look like the one used by the <code class="literal">vim</code> editor, especially the
displacement keys. Anyway, within this configuration menu, users can redefine
all of the keys available from within calcurse’s user interface.</p><p>To define new key bindings, first highlight the action to which it will apply.
Then, delete the actual key binding if necessary, and add a new one. You will
then be asked to press the key corresponding to the new binding. It is possible
to define more than one key binding for a single action.</p><p>An automatic check is performed to see if the new key binding is not already
set for another action. In that case, you will be asked to choose a different
one. Another check is done when exiting from this menu, to make sure all
possible actions have a key associated with it.</p><p>The following keys can be used to define bindings:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
lower-case, upper-case letters and numbers, such as <code class="literal">a</code>, <code class="literal">Z</code>, <code class="literal">0</code>
</li><li class="listitem">
CONTROL-key followed by one of the above letters
</li><li class="listitem">
escape, horizontal tab, and space keys
</li><li class="listitem">
arrow keys (up, down, left, and right)
</li><li class="listitem">
<code class="literal">HOME</code> and <code class="literal">END</code> keys
</li></ul></div><p>While inside the key configuration menu, an online help is available for each
one of the available actions. This help briefly describes what the highlighted
action is used for.</p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>As of calcurse 3.0.0, displacement commands can be preceded by an
      optional number to repeat the command. For example, <code class="literal">10k</code> will move the
      cursor ten weeks forwards if you use default key bindings.</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_color_themes"></a>5.3. Color themes</h3></div></div></div><p><code class="literal">calcurse</code> color theme can be customized to suit user’s needs. To change the
default theme, the configuration page displays possible choices for foreground
and background colors.  Using arrows or calcurse displacement keys to move, and
<code class="literal">X</code> or space to select a color, user can preview the theme which will be
applied.  It is possible to keep the terminal’s default colors by selecting the
corresponding choice in the list.</p><p>The chosen color theme will then be applied to the panel borders, to the
titles, to the keystrokes, and to general informations displayed inside status
bar. A black and white theme is also available, in order to support non-color
terminals.</p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>Depending on your terminal type and on the value of the <code class="literal">$TERM</code>
      environment variable, color could or could not be supported. An error
      message will appear if you try to change colors whereas your terminal
      does not support this feature.  If you do know your terminal supports
      colors but could not get <code class="literal">calcurse</code> to display them, try to set your
      <code class="literal">$TERM</code> variable to another value (such as <span class="strong"><strong>xterm-xfree86</strong></span> for instance).</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_layout_configuration"></a>5.4. Layout configuration</h3></div></div></div><p>The layout corresponds to the position of the panels inside <code class="literal">calcurse</code> screen.
The default layout makes the calendar panel to be displayed on the top-right
corner of the terminal, the todo panel on the bottom-right corner, while the
appointment panel is displayed on the left hand-side of the screen (see the
figure in section <a class="link" href="#basics_interface_interactive" title="Interactive mode">Interactive mode</a> for an
example of the default layout).  By choosing another layout in the
configuration screen, user can customize <code class="literal">calcurse</code> appearance to best suit his
needs by placing the different panels where needed.</p><p>The following option is used to modify the layout configuration:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">appearance.layout</code> (default: <span class="strong"><strong>0</strong></span>)
</span></dt><dd>
  Eight different layouts are to be chosen from (see layout configuration
  screen for the description of the available layouts).
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_sidebar_configuration"></a>5.5. Sidebar configuration</h3></div></div></div><p>The sidebar is the part of the screen which contains two panels: the calendar
and, depending on the chosen layout, either the todo list or the appointment
list.</p><p>The following option is used to change the width of the sidebar:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">appearance.sidebarwidth</code> (default: <span class="strong"><strong>0</strong></span>)
</span></dt><dd>
  Width (in percentage, 0 being the minimum width) of the side bar.
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="options_notify"></a>5.6. Notify-bar settings</h3></div></div></div><p>The following options are used to modify the notify-bar behavior:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<code class="literal">appearance.notifybar</code> (default: <span class="strong"><strong>yes</strong></span>)
</span></dt><dd>
  This option indicates if you want the notify-bar to be displayed or not.
</dd><dt><span class="term">
<code class="literal">format.notifydate</code> (default: <span class="strong"><strong>%a %F</strong></span>)
</span></dt><dd>
  With this option, you can specify the format to be used to display the
  current date inside the notification bar. You can see all of the possible
  formats by typing <code class="literal">man 3 strftime</code> inside a terminal.
</dd><dt><span class="term">
<code class="literal">format.notifytime</code> (default: <span class="strong"><strong>%T</strong></span>)
</span></dt><dd>
  With this option, you can specify the format to be used to display the
  current time inside the notification bar. You can see all of the possible
  formats by typing <code class="literal">man 3 strftime</code> inside a terminal.
</dd><dt><span class="term">
<code class="literal">notification.warning</code> (default: <span class="strong"><strong>300</strong></span>)
</span></dt><dd>
  When there is an appointment which is flagged as <code class="literal">important</code> within the next
  <code class="literal">notification.warning</code> seconds, the display of that appointment inside the
  notify-bar starts to blink. Moreover, the command defined by the
  <code class="literal">notification.command</code> option will be launched.  That way, the user is warned
  and knows there will be soon an upcoming appointment.
</dd><dt><span class="term">
<code class="literal">notification.command</code> (default: <span class="strong"><strong>printf <span class="emphasis"><em>\a</em></span></strong></span>)
</span></dt><dd><p class="simpara">
  This option indicates which command is to be launched when there is an
  upcoming appointment flagged as <code class="literal">important</code>. This command will be passed to
  the user’s shell which will interpret it. To know what shell must be used,
  the content of the <code class="literal">$SHELL</code> environment variable is used. If this variable is
  not set, <code class="literal">/bin/sh</code> is used instead.
</p><div class="informalexample"><p>Say the <code class="literal">mail</code> command is available on the user’s system, one can use the
following command to get notified by mail of an upcoming appointment (the
appointment description will also be mentioned in the mail body):</p><pre class="screen">$ calcurse --next | mail -s "[calcurse] upcoming appointment!" user@host.com</pre></div></dd><dt><span class="term">
<code class="literal">notification.notifyall</code> (default: <span class="strong"><strong>no</strong></span>)
</span></dt><dd>
  Invert the sense of flagging an appointment as <code class="literal">important</code>. If this is
  enabled, all appointments will be notified - except for flagged ones.
</dd><dt><span class="term">
<code class="literal">daemon.enable</code> (default: <span class="strong"><strong>no</strong></span>)
</span></dt><dd>
  If set to yes, daemon mode will be enabled, meaning <code class="literal">calcurse</code> will run into
  background when the user’s interface is exited. This will allow the
  notifications to be launched even when the interface is not running. More
  details can be found in section <a class="link" href="#basics_daemon" title="4.3. Background mode">Background mode</a>.
</dd><dt><span class="term">
<code class="literal">daemon.log</code> (default: <span class="strong"><strong>no</strong></span>)
</span></dt><dd>
  If set to yes, <code class="literal">calcurse</code> daemon activity will be logged (see section
  <a class="link" href="#basics_files" title="4.4. calcurse files">files</a>).
</dd></dl></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_known_bugs"></a>6. Known bugs</h2></div></div></div><p>Incorrect highlighting of items appear when using calcurse black and white
theme together with a <code class="literal">$TERM</code> variable set to <span class="strong"><strong>xterm-color</strong></span>.  To fix this bug,
and as advised by Thomas E. Dickey (<code class="literal">xterm</code> maintainer), <span class="strong"><strong>xterm-xfree86</strong></span> should
be used instead of <span class="strong"><strong>xterm-color</strong></span> to set the <code class="literal">$TERM</code> variable:</p><div class="blockquote"><blockquote class="blockquote"><p>"The xterm-color value for $TERM is a bad choice for XFree86 xterm because it
is commonly used for a <code class="literal">terminfo</code> entry which happens to not support bce. Use
the xterm-xfree86 entry which is distributed with XFree86 xterm (or the similar
one distributed with ncurses)."</p></blockquote></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="bugs"></a>7. Reporting bugs and feedback</h2></div></div></div><p>Please send bug reports and feedback to: <code class="literal">misc .at. calcurse .dot. org</code>.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="contribute"></a>8. How to contribute?</h2></div></div></div><p>If you would like to contribute to the project, you can first send your
feedback on what you like or dislike, and if there are features you miss in
<code class="literal">calcurse</code>.  For now on, possible contributions concern the translation of
<code class="literal">calcurse</code> messages and documentation.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_translating_documentation"></a>8.1. Translating documentation</h3></div></div></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>We recently dropped all translations of the manual files from the
      distribution tarball. There are plan to reintroduce them in form of a
      Wiki on the calcurse website. Please follow the mailing lists for
      up-to-date information.</p></div><p>The <span class="strong"><strong>doc/</strong></span> directory of the source package already contains translated version
of <code class="literal">calcurse</code> manual. However, if the manual is not yet available into your
native language, it would be appreciated if you could help translating it.</p><p>To do so, just copy one of the existing manual file to <code class="literal">manual_XX.html</code>, where
<span class="strong"><strong>XX</strong></span> identifies your language. Then translate this newly created file and send
it to the author (see <a class="link" href="#bugs" title="7. Reporting bugs and feedback">Reporting bugs and feeback</a>), so that it can be
included in the next <code class="literal">calcurse</code> release.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_calcurse_i18n"></a>8.2. calcurse i18n</h3></div></div></div><p>As already mentioned, <code class="literal">gettext</code> utilities are used by <code class="literal">calcurse</code> to produce
multi-lingual messages. We are currently using
<a class="ulink" href="http://www.transifex.net/" target="_top">Transifex</a> to manage those translations.</p><p>This section provides informations about how to translate those messages into
your native language. However, this howto is deliberately incomplete, focusing
on working with <code class="literal">gettext</code> for <code class="literal">calcurse</code> specifically.  For more comprehensive
informations or to grasp the Big Picture of Native Language Support, you should
refer to the <code class="literal">GNU gettext</code> manual at:
<a class="ulink" href="http://www.gnu.org/software/gettext/manual/" target="_top">http://www.gnu.org/software/gettext/manual/</a></p><div class="important" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Important</h3><p>Since we switched to Transifex, editing <span class="strong"><strong>po</strong></span> files is not necessary
           anymore as Transifex provides a user-friendly, intuitive web
           interface for translators. Knowledge of <code class="literal">gettext</code> and the <span class="strong"><strong>po</strong></span>
           format is still useful for those of you who prefer the command line
           and local editing. If you want to use the web UI to edit the
           translation strings, you can skip over to <a class="link" href="#transifex_webui" title="Using the Transifex web UI">Using            the Transifex web UI</a> tough.</p></div><p>Basically, three different people get involved in the translation chain:
coders, language coordinator, and translators. After a quick overview of how
things work, the translator tasks will be described hereafter.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_overview_2"></a>Overview</h4></div></div></div><p>To be able to display texts in the native language of the user, two steps are
required: <span class="strong"><strong>internationalization</strong></span> (i18n) and <span class="strong"><strong>localization</strong></span> (l10n).</p><p>i18n is about making <code class="literal">calcurse</code> support multiple languages. It is performed by
coders, who will mark translatable texts and provide a way to display them
translated at runtime.</p><p>l10n is about making the i18n’ed <code class="literal">calcurse</code> adapt to the specific language of
the user, ie translating the strings previously marked by the developers, and
setting the environment correctly for <code class="literal">calcurse</code> to use the result of this
translation.</p><p>So, translatable strings are first marked by the coders within the <code class="literal">C</code> source
files, then gathered in a template file (<span class="strong"><strong>calcurse.pot</strong></span> - the <span class="strong"><strong>pot</strong></span> extension
meaning <span class="strong"><strong>portable object template</strong></span>). The content of this template file is then
merged with the translation files for each language (<span class="strong"><strong>fr.po</strong></span> for French, for
instance - with <span class="strong"><strong>po</strong></span> standing for <span class="strong"><strong>portable object</strong></span>, ie meant to be read and
edited by humans). A given translation team will take this file, translate its
strings, and send it back to the developers. At compilation time, a binary
version of this file (for efficiency reasons) will be produced (<span class="strong"><strong>fr.mo</strong></span> - <span class="strong"><strong>mo</strong></span>
stands for <span class="strong"><strong>machine object</strong></span>, i.e. meant to be read by programs), and then
installed.  Then <code class="literal">calcurse</code> will use this file at runtime, translating the
strings according to the locale settings of the user.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_translator_tasks"></a>Translator tasks</h4></div></div></div><p>Suppose someone wants to initiate the translation of a new language. Here are
the steps to follow:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
First, find out what the locale name is. For instance, for french, it is
  <code class="literal">fr_FR</code>, or simply <code class="literal">fr</code>. This is the value the user will have to put in his
  <code class="literal">LC_ALL</code> environment variable for software to be translated (see
  <a class="link" href="#basics_invocation_variable" title="Environment variable for i18n">Environment variable for i18n</a>).
</li><li class="listitem">
Then, go into the <span class="strong"><strong>po/</strong></span> directory, and create a new po-file
  from the template file using the following command: <code class="literal">msginit -i calcurse.pot
  -o fr.po -l fr --no-translator</code> If you do not have <code class="literal">msginit</code> installed on
  your system, simply copy the <span class="strong"><strong>calcurse.pot</strong></span> file to <span class="strong"><strong>fr.po</strong></span> and edit the
  header by hand.
</li></ul></div><p>Now, having this <span class="strong"><strong>fr.po</strong></span> file, the translator is ready to begin.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_po_files"></a>po-files</h4></div></div></div><p>The format of the po-files is quite simple. Indeed, po-files are made of four
things:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
<span class="strong"><strong>location lines:</strong></span> tells you where the strings can be seen (name of file and
   line number), in case you need to see a bit of context.
</li><li class="listitem">
<span class="strong"><strong>msgid lines:</strong></span> the strings to translate.
</li><li class="listitem">
<span class="strong"><strong>msgstr lines:</strong></span> the translated strings.
</li><li class="listitem">
<span class="strong"><strong>lines prefixed with <code class="literal">#</code>:</strong></span> comments (some with a special meaning, as we will
   see below).
</li></ol></div><p>Basically, all you have to do is fill the <span class="strong"><strong>msgstr</strong></span> lines with the translation
of the above <span class="strong"><strong>msgid</strong></span> line.</p><p>A few notes:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
<span class="strong"><strong>Fuzzy strings</strong></span>
</span></dt><dd>
  You will meet strings marked with a <code class="literal">"#, fuzzy"</code> comment. <code class="literal">calcurse</code> won’t
  use the translations of such strings until you do something about them.  A
  string being fuzzy means either that the string has already been translated
  but has since been changed in the sources of the program, or that this is a
  new string for which <code class="literal">gettext</code> made a <span class="emphasis"><em>wild guess</em></span> for the translation, based
  on other strings in the file.  It means you have to review the translation.
  Sometimes, the original string has changed just because a typo has been
  fixed. In this case, you won’t have to change anything. But sometimes, the
  translation will no longer be accurate and needs to be changed.  Once you are
  done and happy with the translation, just remove the <code class="literal">"#, fuzzy"</code> line, and
  the translation will be used again in <code class="literal">calcurse</code>.
</dd><dt><span class="term">
<span class="strong"><strong>c-format strings and special sequences</strong></span>
</span></dt><dd>
  Some strings have the following comment: <code class="literal">"#, c-format"</code>.  This tells that
  parts of the string to translate have a special meaning for the program, and
  that you should leave them alone.  For instance, %-sequences, like <code class="literal">"%s"</code>.
  These means that <code class="literal">calcurse</code> will replace them with another string. So it is
  important it remains.  There are also \-sequences, like <code class="literal">\n</code> or <code class="literal">\t</code>. Leave
  them, too. The former represents an end of line, the latter a tabulation.
</dd><dt><span class="term">
<span class="strong"><strong>Translations can be wrapped</strong></span>
</span></dt><dd><p class="simpara">
  If lines are too long, you can just break them like this:
</p><pre class="screen">msgid ""
"some very long line"
"another line"</pre></dd><dt><span class="term">
<span class="strong"><strong>po-file header</strong></span>
</span></dt><dd><p class="simpara">
  At the very beginning of the po-file, the first string form a header, where
  various kind of information has to be filled in. Most important one is the
  charset. It should resemble
</p><pre class="screen">"Content-Type: text/plain; charset=utf-8\n"</pre><p class="simpara">You should also fill in the Last-Translator field, so that potential
contributors can contact you if they want to join you in the translation team,
or have remarks/typo fixes to give about the translations. You can either just
give your name/nick, or add an email address, for exemple:</p><pre class="screen">"Last-Translator: Frederic Culot &lt;frederic@culot.org&gt;\n"</pre></dd><dt><span class="term">
<span class="strong"><strong>Comments</strong></span>
</span></dt><dd>
  Adding comments (lines begining with the <code class="literal">#</code> character) can be a good way to
  point out problems or translation difficulties to proofreaders or other
  members of your team.
</dd><dt><span class="term">
<span class="strong"><strong>Strings size</strong></span>
</span></dt><dd>
  <code class="literal">calcurse</code> is a curses/console program, thus it can be heavily dependant on
  the terminal size (number of columns). You should think about this when
  translating. Often, a string must fit into a single line (standard length is
  80 characters). Don’t translate blindly, try to look where your string will
  be displayed to adapt your translation.
</dd><dt><span class="term">
<span class="strong"><strong>A few useful tools</strong></span>
</span></dt><dd><p class="simpara">
  The po-file format is very simple, and the file can be edited with a standard
  text editor.  But if you prefer, there are few specialized tools you may find
  convenient for translating:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<code class="literal">poEdit</code> (<a class="ulink" href="http://www.poedit.org/" target="_top">http://www.poedit.org/</a>)
</li><li class="listitem">
<code class="literal">KBabel</code> (<a class="ulink" href="http://i18n.kde.org/tools/kbabel/" target="_top">http://i18n.kde.org/tools/kbabel/</a>)
</li><li class="listitem">
<code class="literal">GTranslator</code> (<a class="ulink" href="http://gtranslator.sourceforge.net/" target="_top">http://gtranslator.sourceforge.net/</a>)
</li><li class="listitem">
<code class="literal">Emacs</code> po mode
</li><li class="listitem">
<code class="literal">Vim</code> po mode
</li></ul></div></dd><dt><span class="term">
<span class="strong"><strong>And finally</strong></span>
</span></dt><dd>
  I hope you’ll have fun contributing to a more internationalized world. :) If
  you have any more questions, don’t hesitate to contact us at <span class="strong"><strong>misc .at.
  calcurse .dot. org</strong></span>.
</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="transifex_uploading"></a>Uploading to Transifex</h4></div></div></div><p>There’s several different ways to upload a finished (or semi-finished)
translation for a new language to Transifex. The easiest way is to browse to
the <a class="ulink" href="http://www.transifex.net/projects/p/calcurse/teams/" target="_top">Translation Teams</a> page
and request the addition of a new team.</p><p>As soon as we accepted your request, you will be able to upload your <span class="strong"><strong>po</strong></span> file
on the
<a class="ulink" href="http://www.transifex.net/projects/p/calcurse/resource/calcursepot/" target="_top">calcurse
resource page</a> by clicking the <span class="strong"><strong>Add translation</strong></span> button at the bottom.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_using_transifex_client"></a>Using transifex-client</h4></div></div></div><p>You can also use a command line client to submit translations instead of having
to use the web interface every time you want to submit an updated version. If
you have a recent version of <code class="literal">setuptools</code> installed, you can get the CLI client
by issuing the following command:</p><pre class="screen">$ easy_install -U transifex-client</pre><p>Alternatively, you can get the source code of transifex-client at
<a class="ulink" href="http://pypi.python.org/pypi/transifex-client" target="_top">http://pypi.python.org/pypi/transifex-client</a>.</p><p>After you downloaded and installed the client, run the following commands in
the calcurse source directory to checkout the translation resources of
<span class="strong"><strong>calcurse</strong></span>:</p><pre class="screen">$ tx pull -a</pre><p>To submit changes back to the server, use:</p><pre class="screen">$ tx push -r calcurse.calcursepot -t -l &lt;locale&gt;</pre><p>For more details, read up on <code class="literal">transifex-client</code> usage at the
<a class="ulink" href="http://help.transifex.net/user-guide/client/" target="_top">The Transifex Command-line Client
v0.4</a> section of the <a class="ulink" href="http://help.transifex.net/" target="_top">Transifex documentation</a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="transifex_webui"></a>Using the Transifex web UI</h4></div></div></div><p>As an alternative to editing <span class="strong"><strong>po</strong></span> files, there is a web-based interface that
can be used to create and update translations. After having signed up and
created a new translation team (see <a class="link" href="#transifex_uploading" title="Uploading to Transifex">Uploading to Transifex</a> on how to do that), click the <span class="strong"><strong>Add translation</strong></span> button at the
bottom on the
<a class="ulink" href="http://www.transifex.net/projects/p/calcurse/resource/calcursepot/" target="_top">calcurse
resource page</a>, select the language you’d like to translate and choose
<span class="strong"><strong>Translate Online</strong></span>.</p></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_links"></a>9. Links</h2></div></div></div><p>This section contains links and references that may be of interest to you.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_calcurse_homepage"></a>9.1. calcurse homepage</h3></div></div></div><p>The <code class="literal">calcurse</code> homepage can be found at <a class="ulink" href="http://calcurse.org" target="_top">http://calcurse.org</a></p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_calcurse_announce_list"></a>9.2. calcurse announce list</h3></div></div></div><p>If you are interested in the project and want to be warned when a new release
comes out, you can subscribe to the <code class="literal">calcurse</code> announce list. In doing so, you
will receive an email as soon as a new feature appears in <code class="literal">calcurse</code>.</p><p>To subscribe to this list, send a message to <span class="strong"><strong>announce+subscribe .at. calcurse
.dot. org</strong></span> with "subscribe" in the subject field.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="links_others"></a>9.3. Other links</h3></div></div></div><p>You may want to look at the ical format specification (rfc2445) at:
<a class="ulink" href="http://tools.ietf.org/html/rfc2445" target="_top">http://tools.ietf.org/html/rfc2445</a></p><p>The pcal project page can be found at: <a class="ulink" href="http://pcal.sourceforge.net/" target="_top">http://pcal.sourceforge.net/</a></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_thanks"></a>10. Thanks</h2></div></div></div><p>Its time now to thank other people without whom this program would not exist!
So here is a list of contributing persons I would like to thank :</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Alex for its patches, help and advices with <code class="literal">C</code> programming
</li><li class="listitem">
Gwen for testing and general discussions about how to improve <code class="literal">calcurse</code>
</li><li class="listitem">
Herbert for packaging <code class="literal">calcurse</code> for FreeBSD
</li><li class="listitem">
Zul for packaging <code class="literal">calcurse</code> for NetBSD
</li><li class="listitem">
Wain, Steffen and Ronald for packaging <code class="literal">calcurse</code> for Archlinux
</li><li class="listitem">
Kevin, Ryan, and fEnIo for packaging <code class="literal">calcurse</code> for Debian and Ubuntu
</li><li class="listitem">
Pascal for packaging <code class="literal">calcurse</code> for Slackware
</li><li class="listitem">
Alexandre and Markus for packaging <code class="literal">calcurse</code> for Mac OsX and Darwin
</li><li class="listitem">
Igor for packaging <code class="literal">calcurse</code> for ALT Linux
</li><li class="listitem">
Joel for its calendar script which inspired <code class="literal">calcurse</code> calendar view
</li><li class="listitem">
Michael Schulz and Chris M. for the german translation of <code class="literal">calcurse</code> and its
  manual
</li><li class="listitem">
Jose Lopez for the spanish translation of <code class="literal">calcurse</code> and its manual
</li><li class="listitem">
Neil Williams for the english translation
</li><li class="listitem">
Leandro Noferini for the italian translation
</li><li class="listitem">
Tony for its patch which helped improving the recur_item_inday() function,
  and for implementing the date format configuration options
</li><li class="listitem">
Jeremy Roon for the dutch translation
</li><li class="listitem">
Erik Saule for its patch implementing the <code class="literal">-N</code>, <code class="literal">-s</code>, <code class="literal">-S</code>, <code class="literal">-r</code> and <code class="literal">-D</code>
  flags
</li><li class="listitem"><p class="simpara">
people who write softwares I like and which inspired me, especially :
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem">
<code class="literal">vim</code> for the displacement keys
</li><li class="listitem">
<code class="literal">orpheus</code> and <code class="literal">abook</code> for documentation
</li><li class="listitem">
<code class="literal">pine</code> and <code class="literal">aptitude</code> for the text user interface
</li><li class="listitem">
<code class="literal">tmux</code> for coding style
</li></ul></div></li></ul></div><p>And last, many many thanks to all of the <code class="literal">calcurse</code> users who sent me their
feedback.</p></div></div></body></html>