aboutsummaryrefslogtreecommitdiff
path: root/ctct.1.in
blob: 3ac3cb8af106f42908d82dbaea2f4fe903b335b6 (plain)
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
.\" ctct.1 - the man page for ctct
.\"
.\" Copyright 2015 - 2018 Einhard Leichtfuß
.\"
.\" This file is part of ctct.
.\" 
.\" ctct is free software: you can redistribute it and/or modify
.\" it under the terms of the GNU Affero General Public License as published
.\" by the Free Software Foundation, either version 3 of the License, or
.\" (at your option) any later version.
.\"
.\" ctct is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" GNU Affero General Public License for more details.
.\"
.\" You should have received a copy of the GNU Affero General Public License
.\" along with ctct.  If not, see <https://www.gnu.org/licenses/>.
.\"
.TH CTCT 1 "2018-12-24" "ctct @PACKAGE_VERSION@"
.\"
.\"
.SH NAME
ctct \- a simple console contact manager
.\"
.\"
.SH SYNOPSIS
.B ctct
.I name
.br
.B ctct \-s
.I pattern
.br
.B ctct \-S
.I regex
.br
.B ctct \-e
.I name
.br
.B ctct \-d
.IR name " \.\.\."
.br
.B ctct \-\-rename
.I old new
.br
.B ctct \-\-version
.br
.B ctct \-h
.\"
.\"
.SH DESCRIPTION
.P
.B ctct
manages a set of simple contact entries, identified by name\.
If called with no special arguments,
the contact entry identified by
.I name
is displayed\.
If no such contact entry exists, the result will be similar to that
provided by the
.B --search-by-name
option\.
.P
.I name
may optionally contain exactly one dot (\(aq\.\(aq), which serves as a
separator between two name parts considered equal in relevance\.
This syntax is intended for first and last names of natural persons,
however is obviously not restricted to such\.
.P
It is recommended to stick to a common semantical order at creation, such
as
.IR first \. last
where
.I first
and
.I last
denote the first respectively last name of a natural person,
so that for example the listing of all contact entries is in a reasonable
order\.
.\"This will notably allow for a listing of all the contact entries in a
.\"reasonable order\.
.P
A name or name's part may further contain \(aq_\(aq and \(aq\-\(aq as
separators\.
These may be useful in compound names\.
All other characters must be common letters, according to your locale\.
.P
Contact entries are stored in separate files and may contain arbitrary
text\.
It may be a good idea though to stick to a common syntax\.
For example, a table of the form
.I attribute: value
might make for a good header\.
.P
Configuration is done in
.BR ctct_config (5)\.
For example, the program used to display a contact entry may be changed
(e\.g\.,
.BR less (1))\.
Also, encryption of contact entries may be configured, using your favourite
encryption program (e\.g\.,
.BR gpg (1))\.
.\"
.\"
.SH OPTIONS
.TP
.BR \-s ", " \-\-search\-by\-name " \fIpattern\fP \.\.\."
Search for contacts whose names contain
.I pattern
as a substring\.
If the name is constituted of two dot separated parts,
.I pattern
must be a substring of one of them, hence
.I pattern
will not match if it contains a dot (\(aq\.\(aq)\.
If several patterns are given, all must match\.
Comparison is case insensitive\.
.\"
.TP
.BR \-S ", " \-\-search\-by\-data " \fIregexp\fP \.\.\."
Search for entries that match all the provided extended regular
expressions\.
Matching is case insensitive\.
See also
.BR grep (1)\.
.\"
.TP
.BR \-l ", " \-\-list\-all
List all contacts alphabetically by name\.
If a contact entry is composed of two dot separated parts, these parts'
order is the one chosen at creation respectively renaming\.
.\"
.TP
.BR \-e ", " \-\-edit " \fIname\fP"
Edit and, if non-existent, create the entry identified by
.IR name \.
For the format of
.IR name ,
see
.BR DESCRIPTION \.
Due to the format limitations, it may be a good idea to correctly specify
the actual name inside the contact entry, on whose format there are
precisely no restrictions\.
.\"
.TP
.BR \-d ", " \-\-delete " \fIname\fP \.\.\."
Delete all specified contact entries\.
.\"
.TP
.BI "\-\-rename " "old new"
Rename the entry
.I old
to
.IR new \.
.\"
.TP
.B \-\-version
Show brief version and licensing information\.
.\"
.TP
.BR \-h ", " \-\-help
Show a simple help text basically depicting the above options\.
.\"
.\"
.SH EXIT STATUS
.TP
.B @ret_success@
Successfull operation\.
In case of
.BR \-\-search\-by\-name
or
.BR \-\-search\-by\-data ,
at least one matching entry was found\.
.\"
.TP
.B @ret_failure@
In case of
.BR \-\-search\-by\-name
or
.BR \-\-search\-by\-data ,
no matching entry was found\.
Elsewise, the action did not succeed, for example due to the requested name
not referring to an existing contact entry\.
.\"
.TP
.B @ret_badsyntax@
The used command contains bad syntax which will fail under any conditions\.
.\"
.TP
.B @ret_error@
An unexpected error occurred, for example due to missing permissions in
.BR datadir \.
.\"
.\"
.SH ENVIROMENT
.TP
.B EDITOR
The editor to use when \fBctct\fP is called with the \fB\-\-edit\fP
option and \fBdefault_editor\fP is not set in \fBctct_config\fP(5)\.
.\"
.\"
.SH SEE ALSO
.BR ctct_config (5),
.BR grep (1)
.\"
.\" vi: tw=75