source: trunk/third/nmh/man/mark.man @ 12455

Revision 12455, 5.4 KB checked in by danw, 26 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r12454, which included commits to RCS files with non-trunk default branches.
Line 
1.\"
2.\" %nmhwarning%
3.\" $Id: mark.man,v 1.1.1.1 1999-02-07 18:14:20 danw Exp $
4.\"
5.\" include the -mh macro file
6.so %etcdir%/tmac.h
7.\"
8.TH MARK %manext1% MH.6.8 [%nmhversion%]
9.SH NAME
10mark \- manipulate message sequences
11.SH SYNOPSIS
12.in +.5i
13.ti -.5i
14mark
15\%[+folder] \%[msgs]
16\%[\-sequence\ name\ ...]
17\%[\-add]
18.br
19\%[\-delete] \%[\-list]
20\%[\-public] \%[\-nopublic]
21\%[\-zero]
22.br
23\%[\-nozero]
24\%[\-version]
25\%[\-help]
26.in -.5i
27.SH DESCRIPTION
28The \fImark\fR command manipulates message sequences by adding or deleting
29message numbers from folder\-specific message sequences, or by listing
30those sequences and messages.
31
32A message sequence is a keyword, just like one of the \*(lqreserved\*(rq
33message names, such as \*(lqfirst\*(rq or \*(lqnext\*(rq.  Unlike the
34\*(lqreserved\*(rq message names, which have a fixed semantics on
35a per\-folder basis, the semantics of a message sequence may be
36defined, modified, and removed by the user.  Message sequences are
37folder\-specific, e.g., the sequence name \*(lqseen\*(rq in the context
38of folder \*(lq+inbox\*(rq need not have any relation whatsoever to the
39sequence of the same name in a folder of a different name.
40
41Three action switches direct the operation of \fImark\fR.  These switches
42are mutually exclusive: the last occurrence of any of them overrides
43any previous occurrence of the other two.
44
45The `\-add' switch tells \fImark\fR to add messages to sequences or to
46create a new sequence.  For each sequence named via the `\-sequence\ name'
47argument (which must occur at least once) the messages named via `msgs'
48(which defaults to \*(lqcur\*(rq if no `msgs' are given), are added to the
49sequence.  The messages to be added need not be absent from the sequence.
50If the `\-zero' switch is specified, the sequence will be emptied prior
51to adding the messages.  Hence, `\-add\ \-zero' means that each sequence
52should be initialized to the indicated messages, while `\-add\ \-nozero'
53means that each sequence should be appended to by the indicated messages.
54
55The `\-delete' switch tells \fImark\fR to delete messages from sequences,
56and is the dual of `\-add'.  For each of the named sequences, the
57named messages are removed from the sequence.  These messages need
58not be already present in the sequence.  If the `\-zero' switch is
59specified, then all messages in the folder are added to the sequence
60(first creating the sequence, if necessary) before removing the messages.
61Hence, `\-delete\ \-zero' means that each sequence should contain
62all messages except those indicated, while `\-delete\ \-nozero' means
63that only the indicated messages should be removed from each sequence.
64As expected, the command `mark\0\-sequence\0foo\0\-delete\0all' deletes
65the sequence \*(lqfoo\*(rq from the current folder.
66
67When creating or modifying sequences, you can specify the switches
68`\-public' or `\-nopublic' to force the new or modified sequences to be
69\*(lqpublic\*(rq or \*(lqprivate\*(rq.  The switch `\-public' indicates
70that the sequences should be made \*(lqpublic\*(rq.  These sequences
71will then be readable by all \fInmh\fR users with permission to read the
72relevant folders.  In contrast, the `\-nopublic' switch indicates that the
73sequences should be made \*(lqprivate\*(rq, and will only be accessible by
74you.  If neither of these switches is specified, then existing sequences
75will maintain their current status, and new sequences will default to
76\*(lqpublic\*(rq if you have write permission for the relevant folder.
77Check the mh\-sequence(5) man page for more details about the difference
78between \*(lqpublic\*(rq and \*(lqprivate\*(rq sequences.
79
80The `\-list' switch tells \fImark\fR to list both the sequences defined
81for the folder and the messages associated with those sequences.
82\fIMark\fR will list the name of each sequence given by
83`\-sequence\ name' and the messages associated with that sequence.  If the
84sequence is private, this will also be indicated.  If no sequence is
85specified by the `\-sequence' switch, then all sequences for this folder
86will be listed.  The `\-zero' switch does not affect the operation of
87`\-list'.
88
89The current restrictions on sequences are:
90
91.in +.25i
92The name used to denote a message sequence must consist of an alphabetic
93character followed by zero or more alphanumeric characters, and cannot
94be one of the (reserved) message names \*(lqnew\*(rq, \*(lqfirst\*(rq,
95\*(lqlast\*(rq, \*(lqall\*(rq, \*(lqnext\*(rq, or \*(lqprev\*(rq.
96
97Only a certain number of sequences may be defined for a given folder.
98This number is usually limited to 26 (10 on small systems).
99
100Message ranges with user\-defined sequence names are restricted to the
101form \*(lqname:n\*(rq, \*(lqname:+n\*(rq, or \*(lqname:-n\*(rq, and refer
102to the first or last `n' messages of the sequence `name', respectively.
103Constructs of the form \*(lqname1\-name2\*(rq are forbidden for user
104defined sequences.
105.in -.25i
106.Fi
107^$HOME/\&.mh\(ruprofile~^The user profile
108.Pr
109^Path:~^To determine the user's nmh directory
110.Ps
111^Current\-Folder:~^To find the default current folder
112.Sa
113flist(1), pick(1), mh-sequence(5)
114.De
115`+folder' defaults to the current folder
116.Ds
117`\-add' if `\-sequence' is specified, `\-list' otherwise
118.Ds
119`msgs' defaults to cur (or all if `\-list' is specified)
120.Ds
121`\-nozero'
122.Co
123If a folder is given, it will become the current folder.
124.Hh
125Use \*(lqflist\*(rq to find folders with a given sequence, and
126\*(lqpick sequence \-list\*(rq to enumerate those messages in
127the sequence (such as for use by a shell script).
128.En
Note: See TracBrowser for help on using the repository browser.