Annotated edit history of
read-ical(1) version 2 showing authors affecting page license.
View with all changes included.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
READ-ICAL |
|
|
2 |
!!!READ-ICAL |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
USEAGE |
|
|
7 |
AUTHOR |
|
|
8 |
---- |
|
|
9 |
!!NAME |
|
|
10 |
|
|
|
11 |
|
|
|
12 |
read-ical - coverts information on your Palm Computing Device into an Ical-formatted calendar |
|
|
13 |
!!SYNOPSIS |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
__read-ical /dev/tty[[ |
|
|
17 |
__ |
|
|
18 |
!!DESCRIPTION |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
This manual page documents the small application |
|
|
22 |
__read-ical__. __read-ical__ allows the user to |
|
|
23 |
retrieve the contents of the !ToDo and Datebook databases on |
|
|
24 |
a a Pilot, and convert their contents to an Ical calendar. |
|
|
25 |
Once __read-ical__ is started, the user must invoke |
|
|
26 |
!HotSync on the target device. |
|
|
27 |
|
|
|
28 |
|
|
|
29 |
Note that the calendar file named by __filename__ will be |
|
|
30 |
deleted, so do not use your main calendar. Instead, use a |
|
|
31 |
separate one for this purpose, and include it in your main |
|
|
32 |
calendar. |
|
|
33 |
|
|
|
34 |
|
|
|
35 |
As __read-ical__ works by passing a script to ical, ical |
|
|
36 |
must be in your path. |
|
|
37 |
|
|
|
38 |
|
|
|
39 |
__OPTIONS__ |
|
|
40 |
|
|
|
41 |
|
|
|
42 |
!!USEAGE |
|
|
43 |
|
|
|
44 |
|
|
|
45 |
The program will connect to a target device, retrieve the |
|
|
46 |
!ToDo and Datebook databases (ToDoDB.pdb and DatebookDB.pdb |
|
|
47 |
respectively), then instruct __ical__ to write a calendar |
|
|
48 |
file based on the retrieved information. |
|
|
49 |
!!AUTHOR |
|
|
50 |
|
|
|
51 |
|
|
|
52 |
__read-ical__ was written by Kenneth |
|
|
53 |
Albanowski |
|
|
54 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.