mu/man/mu-server.1

62 lines
1.5 KiB
Groff
Raw Normal View History

2020-01-19 20:38:05 +01:00
.TH MU-SERVER 1 "January 2020" "User Manuals"
.SH NAME
mu server \- the mu backend for the mu4e e-mail client
2012-07-19 19:44:49 +02:00
.SH SYNOPSIS
.B mu server [options]
.SH DESCRIPTION
2020-01-19 20:38:05 +01:00
\fBmu server\fR starts a simple shell in which one can query and manipulate the
2020-02-12 17:42:56 +01:00
mu database. The output uses s-expressions. \fBmu server\fR is not meant for use
2020-01-19 20:38:05 +01:00
by humans, except for debugging purposes. Instead, it is designed specifically
for the \fBmu4e\fR e-mail client.
In this man-page, we document the commands \fBmu server\fR accepts, as well as
2020-01-19 20:38:05 +01:00
their responses. In general, the commands sent to the server are s-expressions
of the form:
.nf
2020-01-19 20:38:05 +01:00
(<command-name> :param1 value1 :param2 value2)
.fi
2020-01-19 20:38:05 +01:00
For example, to view a certain message, the command would be:
.nf
2020-01-19 20:38:05 +01:00
(view :docid 12345)
.fi
2020-01-19 20:38:05 +01:00
Parameters can be sent in any order; they must be of the correct type though.
2020-02-12 17:42:56 +01:00
See \fBlib/utils/mu-sexp-parser.hh\fR and \fBlib/utils/mu-sexp-parser.cc\fR in
2020-01-19 20:38:05 +01:00
source-tree for the details.
.SH OUTPUT FORMAT
\fBmu server\fR accepts a number of commands, and delivers its results in
the form:
.nf
\\376<length>\\377<s-expr>
.fi
\\376 (one byte 0xfe), followed by the length of the s-expression expressed as
an hexadecimal number, followed by another \\377 (one byte 0xff), followed by
the actual s-expression.
By prefixing the expression with its length, it can be processed more
efficiently. The \\376 and \\377 were chosen since they never occur in valid
UTF-8 (in which the s-expressions are encoded).
2020-01-19 20:38:05 +01:00
.sh COMMANDS
2012-09-23 10:42:35 +02:00
.SH AUTHOR
Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>
.SH "SEE ALSO"
2018-03-10 21:08:17 +01:00
.BR mu (1)