diff options
Diffstat (limited to 'pith/pine.hlp')
| -rw-r--r-- | pith/pine.hlp | 1823 |
1 files changed, 3 insertions, 1820 deletions
diff --git a/pith/pine.hlp b/pith/pine.hlp index 6fbe15ac..e36c1bc5 100644 --- a/pith/pine.hlp +++ b/pith/pine.hlp @@ -89,7 +89,6 @@ Where "variable" is one of either: ALPINE_VERSION ALPINE_REVISION ALPINE_COMPILE_DATE - ALPINE_PATCHLEVEL ALPINE_TODAYS_DATE C_CLIENT_VERSION _LOCAL_FULLNAME_ @@ -160,14 +159,6 @@ Version <!--#echo var="ALPINE_VERSION"-->(<!--#echo var="ALPINE_REVISION"-->) </DIV> <P> -This version was modified from its original source code. More information -about some of the patches applied to this version can be found <A HREF="h_patches">here</A>. -<!--chtml if pinemode="running"--> -The patch level of this version, including creation date of the patch is: -<!--#echo var=ALPINE_PATCHLEVEL-->. -<!--chtml endif--> - -<P> Alpine is an "Alternatively Licensed Program for Internet News and Email" produced until 2008 by the University of Washington. It is intended to be an easy-to-use program for @@ -3192,11 +3183,9 @@ There are also additional details on <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a> <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a> <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a> -<li><a href="h_config_auto_read_msgs_rules">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs-using-rules"--></a> <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a> <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a> <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a> -<li><a href="h_config_circular_tab">FEATURE: <!--#echo var="FEAT_enable-circular-tab"--></a> <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a> <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a> <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a> @@ -3296,7 +3285,6 @@ There are also additional details on <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a> <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a> <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a> -<li><a href="h_config_ignore_size">FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></a> <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a> <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a> <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a> @@ -3310,7 +3298,6 @@ There are also additional details on <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a> <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a> <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a> -<li><a href="h_config_mark_for_group">FEATURE: <!--#echo var="FEAT_mark-for-me-in-group"--></a> <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a> <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a> <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a> @@ -3513,7 +3500,6 @@ There are also additional details on <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a> <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a> <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a> -<li><a href="h_config_sleep">OPTION: <!--#echo var="VAR_sleep-interval-length"--></a> <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a> <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a> <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a> @@ -3566,7 +3552,6 @@ There are also additional details on <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a> <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a> <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a> -<li><a href="h_config_special_text_to_color">OPTION: <!--#echo var="VAR_h_config_special_text_to_color"--></a> <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a> <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a> <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a> @@ -3595,11 +3580,9 @@ There are also additional details on <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a> <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a> <li><a href="h_config_signature_color">OPTION: Signature Color</a> -<li><a href="h_config_special_text_color">OPTION: Special Text Color</a> <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a> <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a> <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a> -<li><a href="h_config_thread_sort_key">OPTION: <!--#echo var="VAR_thread-sort-key"--></a> <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a> <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a> <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a> @@ -4459,10 +4442,6 @@ thread: message in the thread was sent to you as a cc:. This symbol will only show up if the feature "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default). - <LI> "." for messages that were sent to you as part of a group message, regardless - of if all addresses in the To: field are yours or not. This symbol will only show up if - the feature - "<A HREF="h_config_mark_for_group"><!--#echo var="FEAT_mark-for-me-in-group"--></A>" is turned on (which is the default). <LI> "X" for selected. You have selected at least one message in the thread by using the "select" command. (Some systems may optionally allow selected messages to be denoted by the index line being displayed in bold @@ -4622,10 +4601,6 @@ message: message was sent to you as a cc:. This symbol will only show up if the feature "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default). - <LI> "." for messages that were sent to you as part of a group message, regardless - of if all addresses in the To: field are yours or not. This symbol will only show up if - the feature - "<A HREF="h_config_mark_for_group"><!--#echo var="FEAT_mark-for-me-in-group"--></A>" is turned on (which is the default). <LI> "X" for selected. You have selected the message by using the "select" command. (Some systems may optionally allow selected messages to be denoted by the index line being displayed in bold @@ -5540,163 +5515,6 @@ the names of the carbon copy addresses of the message. <End of help on this topic> </BODY> </HTML> -======= h_thread_index_sort_arrival ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Arrival</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Arrival</H1> - -The <EM>Arrival</EM> sort option arranges threads according to the last -time that a message was added to it. In this order the last thread -contains the most recent message in the folder. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_date ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Date</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Date</H1> - -The <EM>Date</EM> sort option in the THREAD INDEX screen sorts -threads by the date in which messages were sent. The thread containing the -last message in this order is displayed last. -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_subj ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Subject</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Subject</H1> - -The <EM>Subject</EM> sort option has not been defined yet. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_ordsubj ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: OrderedSubject</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: OrderedSubject</H1> - -The <EM>OrderedSubject</EM> sort option in the THREAD INDEX screen is -the same as sorting by <A HREF="h_thread_index_sort_subj">Subject</A>. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_thread ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Thread</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Thread</H1> - -The <EM>Thread</EM> sort option in the THREAD INDEX screen sorts all -messages by the proposed algorithm by Crispin and Murchison. In this -method of sorting once threads have been isolated they are sorted by the -date of their parents, or if that is missing, the first message in that -thread. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_from ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: From</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: From</H1> - -The <EM>From</EM> sort option has not been defined yet. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_size ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Size</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Size</H1> - -The <EM>Size</EM> sort option sorts threads by their size (the number -of messages in the thread). This could be used to find conversations -where no reply has been sent by any of the participants in the thread -(e.g. those whose length is equal to one). Longer threads appear -below shorter ones. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_score ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Score</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Score</H1> - -The <EM>Score</EM> sort option means that threads are sorted according to -the maximum score of a message in that thread. A thread all of whose -messages contain a smaller score than a message in some other thread is -placed in an earlier place in the list of messages for that folder; that -is, threads with the highest scores appear at the bottom of the index -list. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_to ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: To</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: To</H1> - -The <EM>To</EM> sort option has not been defined yet. - -<P> -<End of help on this topic> -</BODY> -</HTML> -======= h_thread_index_sort_cc ======= -<HTML> -<HEAD> -<TITLE>SORT OPTION: Cc</TITLE> -</HEAD> -<BODY> -<H1>SORT OPTION: Cc</H1> - -The <EM>Cc</EM> sort option has not been defined yet. - -<P> -<End of help on this topic> -</BODY> -</HTML> ======= h_index_cmd_whereis ======= <HTML> <HEAD> @@ -6920,46 +6738,6 @@ hold down the "Control" key on your keyboard. The second "^" "type the character ^". <P> -This version of Alpine contains an enhanced algorithm for justification, -which allows you to justify text that contains more complicated quote -strings. This algorithm is based on pragmatics, rather than on a theory, -and seems to work well with most messages. Below you will find technical -information on how this algorithm works. - -<P> -When justifying, Alpine goes through each line of the text and tries to -determine for each line what the quote string of that line is. The quote -string you provided is always recognized. Among other characters -recognized is ">". - -<P> -Some other constructions of quote strings are recognized only if they -appear enough in the text. For example "Peter :" is only -recognized if it appears in two consecutive lines. - -<P> -Additionaly, Alpine recognizes indent-strings and justifies text in a -paragraph to the right of indent-string, padding with spaces if necessary. -An indent string is one which you use to delimit elements of a list. For -example, if you were to write a list of groceries, one may write: - -<UL> -<LI> Fruit -<LI> Bread -<LI> Eggs -</UL> - -<P> -In this case the character "*" is the indent-string. Aline -recognizes numbers (0, 1, 2.5, etc) also as indent-strings, and certain -combinations of spaces, periods, and parenthesis. In any case, numbers are -recognized <B>ONLY</B> if the line preceeding the given line is empty or -ends in one of the characters "." or ":". -In addition to the explanation of what constitutes a paragraph above, a -new paragraph is recognized when an indent-string is found in it (and -validated according to the above stated rules). - -<P> <End of help on this topic> </BODY> </HTML> @@ -18522,7 +18300,6 @@ This set of special tokens may be used in the <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option, in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option, in signature files, -in the <A HREF="h_config_reply_leadin_rules">"new-rules" option</A>, in template files used in <A HREF="h_rules_roles">"roles"</A>, and in the folder name that is the target of a Filter Rule. @@ -18535,7 +18312,7 @@ and in the target of Filter Rules. <P> <P> -<H1><EM>Tokens Available for all Cases (except Filter Rules or in some cases for new-rules)</EM></H1> +<H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1> <DL> <DT>SUBJECT</DT> @@ -18568,15 +18345,6 @@ email address, never the personal name. For example, "mailbox@domain". </DD> -<DT>ADDRESSTO</DT> -<DD> -This is similar to the "TO" token, only it is always the -email address of all people listed in the TO: field of the messages. Addresses -are separated by a blank space. Example, "mailbox@domain" when -the e-mail message contains only one person in the To: field, or -"peter@flintstones.com president@world.com". -</DD> - <DT>MAILBOX</DT> <DD> This is the same as the "ADDRESS" except that the @@ -18624,15 +18392,6 @@ are unavailable) of the persons specified in the message's "Cc:" header field. </DD> -<DT>ADDRESSCC</DT> -<DD> -This is similar to the "CC" token, only it is always the -email address of all people listed in the Cc: field of the messages. Addresses -are separated by a blank space. Example: "mailbox@domain" when -the e-mail message contains only one person in the Cc: field, or -"peter@flintstones.com president@world.com". -</DD> - <DT>RECIPS</DT> <DD> This token represents the personal names (or email addresses if the names @@ -18641,14 +18400,6 @@ message's "To:" header field and the message's "Cc:" header field. </DD> -<DT>ADDRESSRECIPS</DT> -<DD> -This token represent the e-mail addresses of the people in the To: and -Cc: fields, exactly in that order separated by a space. It is almost obtained -by concatenating the ADDRESSTO and ADDRESSCC tokens. -</DD> - - <DT>NEWSANDRECIPS</DT> <DD> This token represents the newsgroups from the @@ -18994,11 +18745,7 @@ aspects of the message's state. The first character is either blank, a '*' for message marked Important, or a '+' indicating a message addressed directly to you (as opposed to your having received it via a -mailing list, for example). The symbol '.' will be used -for messages that were sent to you as part of a group message, regardless -of if all addresses in the To: field are yours or not. This symbol will only show up if -the feature -"<A HREF="h_config_mark_for_group"><!--#echo var="FEAT_mark-for-me-in-group"--></A>" is turned on (which is the default). +mailing list, for example). When the feature "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is set, if the first character would have been @@ -19134,14 +18881,6 @@ The progression of sizes used looks like: <P> </DD> -<DT>SIZETHREAD</DT> -<DD> -This token represents the total size of the thread for a collapsed thread -or the size of the branch for an expanded thread. The field is omitted for -messages that are not top of threads nor branches and it defaults to -the SIZE token when your folders is not sorted by thread. -</DD> - <DT>SIZENARROW</DT> <DD> This token represents the total size, in bytes, of the message. @@ -19757,78 +19496,6 @@ This is an end of line marker. </DL> <P> -<H1><EM>Tokens Available Only for New-Rules</EM></H1> - -<DL> -<DT>FOLDER</DT> -<DD> -Name of the folder where the rule will be applied -</DD> -</DL> - -<DL> -<DT>COLLECTION</DT> -<DD> -Name of the collection list where the rule will be applied. -</DD> -</DL> - -<DL> -<DT>ROLE</DT> -<DD> -Name of the Role used to reply a message. -</DD> -</DL> - -<DL> -<DT>BCC</DT> -<DD> -Not implemented yet, but it will be implemented in future versions. It will -be used for <A HREF="h_config_compose_rules">compose</A> -<A HREF="h_config_reply_rules">reply</A> -<A HREF="h_config_forward_rules">forward</A> -rules. -</DD> -</DL> - -<DL> -<DT>LCC</DT> -<DD> -This is the value of the Lcc: field at the moment that you start the composition. -</DD> -</DL> - -<DL> -<DT>FORWARDFROM</DT> -<DD> -This corresponds to the personal name (or address if there's no personal -name) of the person who sent the message that you are forwarding. -</DD> -</DL> - -<DL> -<DT>FORWARDADDRESS</DT> -<DD> -This is the address of the person that sent the message that you -are forwarding. -</DD> -</DL> - - - - -<DL> -<DT>FLAG</DT> -<DD> -A string containing the value of all the flags associated to a specific -message. The possible values of allowed flags are "*" for Important, "N" -for recent or new, "U" for unseen or unread, "R" for seen or read, "A" for -answered and "D" for deleted. See an example of its use in the -<A HREF="h_config_new_rules">new rules</A> explanation and example help. -</DD> -</DL> - -<P> <H1><EM>Token Available Only for Templates and Signatures</EM></H1> <DL> @@ -20753,53 +20420,6 @@ give up and consider it a failed connection. <End of help on this topic> </BODY> </HTML> -====== h_config_sleep ====== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_sleep-interval-length"--> (UNIX Alpine only)</TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_sleep-interval-length"--> (UNIX Alpine only)</H1> - -<P> -When you open an attachment, Alpine goes through a list of viewers either -in your .mailcap file, or some other mailcap file in your system. The -normal behavior is that Alpine opens a local copy of the attachment, which -is removed from the system <B>after</B> the viewer has completed -displaying it. For example, if you open an attachment on a viewer and -later close the viewer, then control will return to the system and the -copy of the attachment will be removed from the system. This is the normal -behavior and has been accepted for years as the correct behavior. - -<P> -However, if an instance of the viewer is already open, the viewer may -return control to the system <B>before</B> it reads the copy of the -attachment. Given that Alpine removes the copy of the attachment after -control is returned to the system, this may cause Alpine to remove the -copy of the attachment <B>before</B> it is actually opened by the viewer. - -<P> -Since Alpine has no control over when a viewer returns from opening a file, -and viewers should not return before they read the file, Alpine has no control -over when the viewer will read the file and avoid the problem described above. - -<P> -The value of this option is the number of seconds that Alpine will wait -between the time that the viewer returns control to the system and the -when it will remove it from the system. You will not notice this -delay, since this will happen in the background. The default value is -0 which means that no delay will occur, and it is a value which may trigger -the problem described above with some viewers. By modifying the value of -this option you can set Alpine to wait longer. A reasonable small value is 5, -which works with all viewers tested to date. The maximum value is 120 -(2 minutes). -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_incoming_interv ====== <HTML> <HEAD> @@ -21864,102 +21484,6 @@ your account's home directory). <End of help on this topic> </BODY> </HTML> -====== h_config_maildir_location ====== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_maildir-location"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_maildir-location"--></H1> - -<P> -This option should be used only if you have a Maildir folder which you -want to use as your INBOX. If this is not your case (or don't know what -this is), you can safely ignore this option. - -<P> -This option overrides the default directory Pine uses to find the location of -your INBOX, in case this is in Maildir format. The default value of this -option is "Maildir", but in some systems, this directory could have been -renamed (e.g. to ".maildir"). If this is your case use this option to change -the default. - -<P> -The value of this option is prefixed with the "~/" string to determine the -full path to your INBOX. - -<P> -You should probably <A HREF="h_config_maildir">read</A> a few tips that -teach you how to configure your maildir for optimal performance. This -version also has <A HREF="h_config_courier_list">support</A> for the -Courier style file system when a maildir collection is accessed locally. - -<P><UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL> -<P> -<End of help on this topic> -</BODY> -</HTML> -====== h_config_maildir ===== -<HTML> -<HEAD> -<TITLE>Maildir Support</TITLE> -</HEAD> -<BODY> -<H1>Maildir Support</H1> - -This version of Alpine has been enhanced with Maildir support. This text is -intended to be a reference on its support. -<P> - -A Maildir folder is a directory that contains three directories called -cur, tmp and new. A program that delivers mail (e.g. postfix) will put new -mail in the new directory. A program that reads mail will look for for old -messages in the cur directory, while it will look for new mail in the new -directory. -<P> - -In order to use maildir support it is better to set your inbox-path to the -value "#md/inbox" (without quotes). This assumes that your mail -delivery agent is delivering new mail to ~/Maildir/new. If the directory -where new mail is being delivered is not called "Maildir", you can set the -name of the subdirectory of home where it is being delivered in the <A -HREF="h_config_maildir_location"><!--#echo var="VAR_maildir-location"--></A> configuration -variable. Most of the time you will not have to worry about the -<!--#echo var="VAR_maildirlocation"--> variable, because it will probably be set by your -administrator in the pine.conf configuration file. -<P> - -One of the advantages of the Maildir support of this version of Alpine is -that you do not have to stop using folders in another styles (mbox, mbx, -etc.). This is desirable since the usage of a specific mail storage system -is a personal decision. Folders in the maildir format that are part of the -Mail collection will be recognized without any extra configuration of your -part. If your mail/ collection is located under the mail/ directory, then -creating a new maildir folder in this collection is done by pressing "A" -and entering the string "#driver.md/mail/newfolder". Observe that adding a -new folder as "newfolder" may not create such folder in maildir format. - -<P> -If you would like to have all folders created in the maildir format by -default, you do so by adding a Maildir Collection. In order to convert -your current mail/ collection into a maildir collection, edit the -collection and change the path variable from "mail/" to -"#md/mail". In a maildir collection folders of any other format -are ignored. - -<P> Finally, This version also has -<A HREF="h_config_courier_list">support</A> for the Courier style file system -when a maildir collection is accessed locally. - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_literal_sig ===== <HTML> <HEAD> @@ -22722,45 +22246,6 @@ command, then it will not be re-sorted until the next time it is opened. <End of help on this topic> </BODY> </HTML> -====== h_config_thread_sort_key ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_thread-sort-key--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_thread-sort-key--></TITLE></H1> - -This option determines the order in which threads will be displayed. You -can choose from the options listed below. Each folder is sorted in one of -the sort orders displayed below first, then the thread containing the last -message of that sorted list is put at the end of the index. All messages -of that thread are "removed" from the sorted list and the -process is repeated with the remaining messages in that list. - -<P> -<UL> - <LI> <A HREF="h_thread_index_sort_arrival">Arrival</A> - <LI> <A HREF="h_thread_index_sort_date">Date</A> -<!-- <LI> <A HREF="h_thread_index_sort_subj">Subject</A> - <LI> <A HREF="h_thread_index_sort_ordsubj">OrderedSubj</A>--> - <LI> <A HREF="h_thread_index_sort_thread">Thread</A> -<!-- <LI> <A HREF="h_thread_index_sort_from">From</A> --> - <LI> <A HREF="h_thread_index_sort_size">Size</A> - <LI> <A HREF="h_thread_index_sort_score">Score</A> -<!-- <LI> <A HREF="h_thread_index_sort_to">To</A> - <LI> <A HREF="h_thread_index_sort_cc">Cc</A>--> -</UL> - -<P> Each type of sort may also be reversed. Normal default is by -"Thread". - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_other_startup ===== <HTML> <HEAD> @@ -23031,898 +22516,6 @@ character sets Alpine knows about by using the "T" ToCharsets command. <End of help on this topic> </BODY> </HTML> -====== h_config_procid ===== -<HTML> -<HEAD> -<TITLE>Token: PROCID</TITLE> -</HEAD> -<BODY> -<H1>TOKEN: PROCID explained</H1> - -<P> -The PROCID token is a way in which the user and the program can differentiate -between different parts of a program. It allows the user to tell the -program when to use a specific rule, and only use it at that specific -moment. - -<P> The normal way in which this is done is by adding a new configuration -variable. The idea behind the PROCID token is that instead of adding a new -configuration variable (which means the user has to go through more -configuration variables just to tune the program to his liking), we reuse -an old variable and let the user look inside that variable for the desired -behavior, which is actually set by setting the PROCID token. - -<P> -Consider the following examples for forward-rules: - -<P> -_ROLE_ == {work} => _SUBJECT_ := _COPY_{[tag] _SUBJECT_} - -<P> -and - -<P> -_ROLE_ == {work} => _LCC_ := _TRIM_{_FORWARDFROM_ <_FORWARDADDRESS_>} - -<P> -both are triggered by the same condition. Since both are configured in the -same variable, only one of them will be executed all the time (whichever -is first). Therefore in order to differentiate, we add a _PROCID_ token. -So, for example, the first example above will be executed only when we are -determining the subject. In this case, the following rule will accomplish -this task - -<P> -_PROCID_ == {fwd-subject} && _ROLE_ == {work} => _SUBJECT_ := _COPY_{[tag] _SUBJECT_} - -<P> -In this case, this rule will be tested fully only when we are determining -the subject line of a forwarded message, not otherwise. - -<P> -It is wise to add the _PROCID_ token as the first condition in a rule, so -that other conditions will not be tested in a long list of rules. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_compose_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_compose-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_compose-rules"--></H1> - -<P> At this time, this option is used to generate values for signature -files that is not possible to do with the use of -<A HREF="h_rules_roles">roles</A>. - -<P> For example, you can have a rule like:<BR> -_TO_ >> {Peter Flinstones} => _SIGNATURE_{~/.petersignature} - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_forward_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_forward-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_forward-rules"--></H1> - -<P> This option has several uses. This feature uses the PROCID function -to identify different features of forwarding. You can read more about PROCID -by following <A HREF="h_config_procid">this link</A>. - -<P> If you want to edit the subject of a forwarded message, use the -PROCID <I>fwd-subject</I>. For example you could have a rule like - -<P> -_ROLE_ == {admin} && _SUBJECT_ !> {[tag] } => _COPY_{[tag] _SUBJECT_} - -<P> Another way in which this option can be used, is to trim the values of -some fields. For this application the PROCID is <I>fwd-lcc</I>. For -example it can be used in the following way: - -<P> -_ROLE_ == {work} => _LCC_ := _TRIM_{_FORWARDFROM_ <_FORWARDADDRESS_>} - -<P> Other functions that can be used in this option are _EXEC_ and _REXTRIM_. - -<P> You can also use the _EXEC_ function. The documentation for this function -is in the -<A HREF="h_config_resub_rules"><!--#echo var="VAR_reply-subject-rules"--></A> -help text. - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_index_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_index-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_index-rules"--></H1> - -<P> This option is used to supersede the value of the option <A -HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> for specific folders. In -this form you can have different index-formats for different folders. For -example an entry here may be: - -<P> -_FOLDER_ == {INBOX} => _INDEX_{IMAPSTATUS DATE FROM(33%) SIZE SUBJECT(67%)} - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_pretty_command ===== -<HTML> -<HEAD> -<TITLE>Pretty-Command Explained</TITLE> -</HEAD> -<BODY> -<H1>Pretty Command Explained</H1> - -<P> This text explains how to encode keys so that they will be recognized -by Alpine in the _PKEY_ token. Most direct keystrokes are recognized in the -same way. For example, the key ~ is recognized by the same character. The -issue is how control, or functions keys are recognized. The internal code -is most times easy to find out. If the key you want to use is not already -recognized by Alpine simply press it. Alpine will print its code. For example, -the return key is not recognized in this screen, so if you press it, you -will see the following message. - -<P> [Command "RETURN" not defined for this screen. Use ? for help] - -<P> from here you can guess that the code for the return command is -RETURN. You can try other commands, like Control-C, the TAB key, F4, etc. -to see their codes. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_key_macro_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_key-definition-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_key-definition-rules"--></H1> - -<P> This option can be used to define macros, that is, to define a key that -when pressed executes a group of predetermined keystrokes. Since Alpine is -a menu driven program, sometimes the same key may have different meanings -in different screens, so a global redefinition of a key although possible -is not advisable. - -<P> <B>Always use the _SCREEN_ token as defined below.</B>. You have been -warned! - -<P> In each screen, every time you press a recognized key a command is -activated. In order to understand this feature, think of commands instead -of keystrokes. For example, you can think of the sort by thread command. -This command is associated to the keystrokes $ and h. You may want to -associate this command to a specific keystroke, like ~, so every time you -press the ~ key, Alpine understand the $ and h keystrokes, which activates -the sort by thread command. - -<P> Therefore, in order to use this option you must think of three -components. The screen where you will use the macro, the keystroke you -want to use and the set of keystrokes used by Alpine to accomplish the task -you want to accomplish. We will talk about these three components in what -follows. - -<P> First you must decide in which screen the macro will be used. This -feature is currently only available for the screen where your messages -are listed in index form (<A HREF="h_mail_index">MESSAGE INDEX</A>), -the screen where your message is displayed -(<A HREF="h_mail_view">MESSAGE TEXT</A>) and the screen where the list of -folders is displayed (<A HREF="h_folder_maint">FOLDER LIST</A>). The -internal names of these screens for this patch are "index", -"text" and -"folder" respectively. Please note that the internal names are -all in lowercase are are case sensitive. - -<P> In order to define the screen, you use the _SCREEN_ token, so for -example, you can write _SCREEN_ == {index}. - -<P> Second you must think of which key you will use to activate the macro. -Here you can use any key of your choice. The token you use to designate a -key is the _PKEY_ token (PKEY stands for "pressed key"). For -example you could use _PKEY_ == {~}, to designate the "~" -character to activate the command. Some keystrokes (like control, or -function keys) are encoded in special ways. You should read the -<A HREF="h_config_pretty_command">full explanation</A> on how to find -out the encoding for each keystroke. - -<P> Last, you must think of the list of keys you will use to accomplish -the task you want Alpine to perform. Say for example you want to have the -folder sorted by thread. That means you want Aline to execute the keys -"$" and "h". You use the _COMMAND_ function to specify -this. The syntax in this case is _COMMAND_{$,h}. - -<P> Observe that in the above example the different inputs are separated -by commas. This is the standard way in which the -<A HREF="h_config_init_cmd_list"><!--#echo var="VAR_initial-keystroke-list"--></A> command works from -the command line. Due to restrictions in the way Alpine works, a comma is a -special character, which when added to a configuration option like this -will cause the configuration to split into several lines in the -configuration screen. This has the effect of producing several -configuration options, all of which are incorrect. This is undesirable -because what you want is to have it all in one line. In order to force the -configuration into one line you must quote the comma. The best way to -accomplish this is by quoting the full definition of the rule. For -example. - -<P> -"_SCREEN_ == {index} && _PKEY_ == {~} => _COMMAND_{$,h}" - -<P> Another way to accomplish the same effect is by quoting the command and -not using quotes for the full command, nor commas to separate the -keystrokes in the command, for example - -<P> -_SCREEN_ == {index} && _PKEY_ == {~} => _COMMAND_{"$h"} - -<P> For more information on how to define the argument of the _COMMAND_ -token see the help of -<A HREF="h_config_init_cmd_list"><!--#echo var="VAR_initial-keystroke-list"--></A>. - -<P> Because the $ command can also be used as the first character in the -definition of an environemnt variable, no expansion of environment variables -is done when parsing this variable. The $ character does not need quoting -and quoting it will make Alpine fail to produce the correct result. - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_replace_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_replace-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_replace-rules"--></H1> - -<P> This option is used to have Alpine print different values for specific -tokens in the <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>. For example you -can replace strings like "To: newsgroup" by your name. - -<P> Here are examples of possible rules:<BR> -_FOLDER_ != {sent-mail} && _NICK_ != {} => _FROM_ := _REPLACE_{_FROM_ (_NICK_)} - -<P> or if you receive messages with tags that contain arbitrary numbers, and -you want them removed from the index (but not from the subject), use a rule -like the following<BR> -_FOLDER_ == {INBOX} => _SUBJECT_ := _REXTRIM_{\[some-tag-here #[0-9].*\]} - -<P> You can also use this configuration option to remove specific strings of -the index display screen, so that you can trim unnecessary information in -your index, like the reply leadin string in the OPENINGTEXTNQ token of the index. -<BR> -_FOLDER_ == {mailing-list} => _OPENINGTEXTNQ_ := _REXTRIM_{On.*wrote: } - -<P> or if you receive messages with tags that contain arbitrary numbers, and -you want them removed from the index (but not from the subject), use a rule -like the following<BR> - -<P> You can also use the _EXEC_ function. The documentation for this function -is in the -<A HREF="h_config_resub_rules"><!--#echo var="VAR_reply-subject-rules"--></A> -help text. - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_reply_leadin_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_reply-leadin-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_reply-leadin-rules"--></H1> - -<P> This option is used to have Alpine generate a different -<A HREF="h_config_reply_intro"><!--#echo var="VAR_reply-leadin"--></A> string dependent either on -the person you are replying to, or the folder where the message is being -replied is in, or both. - -<P> Here there are examples of how this can be used. One can use the definition -below to post to newsgroups and the pine-info mailing list, say: -<P> -_FOLDER_ << {pine-info;_NEWS_} => _REPLY_{*** _FROM_ _ADDRESS_("_FROM_" "" "(_ADDRESS_) ")wrote in_NEWS_("" " the" "") _FOLDER_ _NEWS_("" "list " "")_SMARTDATE_("Today" "today" "on _LONGDATE_"):} - -<P> Here there is an example that one can use to change the reply indent string -to reply people that speak spanish. -<P> -_FROM_{Condorito;Quico} => _REPLY_{*** _FROM_ (_ADDRESS_) escribió _SMARTDATE_("Today" "hoy" "en _LONGDATE_"):} - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_resub_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_reply-subject-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_reply-subject-rules"--></H1> - -<P> This option is used to have Alpine generate a different subject when -replying rather than the one Alpine would generate automatically. - -<P> Here there are a couple of examples about how to use this -configuration option: - -<P> In order to have messages with empty subject to be replied with the message -"your message" use the rule<BR> -<center>_SUBJECT_ == {} => _RESUB_{Re: your message}</center> - -<P> If you want to trim some parts of the subject when you reply use the -rule<BR> -<center>_SUBJECT_ >> {[one];two} => _SUBJECT_ := _TRIM_{[;];two}</center> - -<P>this rule removes the brackets "[" and "]" whenever the string "[one]" -appears in it, it also removes the word "two" from it. - -<P>Another example where you may want to use this rule is when you -correspond with people that change the reply string from "Re:" -to "AW:" or "Sv:". In this case a rule like<BR> -<center>_SUBJECT_ >> {Sv: ;AW: } => _SUBJECT_ := _TRIM_{Sv: ;AW: }</center> -<P> -would eliminate undesired strings in replies. - -<P> Another interesting use of this option is the use of the _EXEC_ function. -This function takes as an argument a program or a script. This program -must take as the input a file, and write its output to that file. For example, -below is a sample of a script that removes the letter "a" of a file. - -<PRE> -#!/bin/sh -sed 's/a//g' $1 > /tmp/mytest -mv /tmp/mytest $1 -</PRE> - -<P> -As you can see this script took "$1" as input file, the sed program -wrote its output to /tmp/mytest, and then the move program moved the file -/tmp/mytest to the input file "$1". This is the kind of behavior -that your program is expected to have. - -<P> -The content of the input file ("$1" above) is the value of a token -like _SUBJECT_. In order to indicate this, we use the notation - -<P> -_SUBJECT_ := _EXEC_{/path/to/script} - -<P> for the action. So for example - -<P> -_FOLDER_ := {sent-mail} => _SUBJECT_ := _EXEC_{/path/to/script} - -<P> is a valid rule. - -<P> You can also use this configuration option to customize reply subjects -according to the sender of the message. - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> -</BODY> -</HTML> -====== h_config_sort_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_sort-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_sort-rules"--></H1> - -<P> This option is used to have Alpine sort different folders in different orders -and thus override the value already set in the -<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A> configuration option. - -<P> Here's an example of the way it can be used. In this case all incoming -folders are mailing lists, except for INBOX, so we sort INBOX by arrival -(which is the default type of sort), but we want all the rest of mailing -lists and newsgroups to be sorted by thread. - -<P> -_COLLECTION_ >> {Incoming-Folders;News} && _FOLDER_ != {INBOX} => _SORT_{tHread} - -<P> Another example could be<BR> -_FOLDER_ == {Mailing List} => _SORT_{Reverse tHread} - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> - -</BODY> -</HTML> -====== h_config_save_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_save-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_save-rules"--></H1> - -<P> This option is used to specify which folder should be used to save a -message depending either on the folder the message is in, who the message -is from, or text that the message contains in specific headers (Cc:, -Subject:, etc). - -<P> If this option is set and the -<A HREF="h_config_auto_read_msgs"><!--#echo var="FEAT_auto-move-read-msgs"--></A> configuration -option is also enabled then these definitions will be used to move messages -from your INBOX when exiting Alpine. - -<P>Here there are some examples<BR> -_FLAG_ >> {D} -> Trash<BR> -_FROM_ == {U2} -> Bono<BR> -_FOLDER_ == {comp.mail.pine} -> pine-stuff<BR> -_NICK_ != {} -> _NICK_/_NICK_<BR> -_DATEISO_ >> {02-10;02-11} -> archive-oct-nov-2002 - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> - -</BODY> -</HTML> -====== h_config_reply_indent_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_reply-indent-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_reply-indent-rules"--></H1> - -<P> This option is used to specify which reply-indent-string is to be used -when replying to an e-mail. If none of the rules are successful, the result in -the variable <a href="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></a> -is used. - -<P> The associated function to this configuration option is called "RESTR" (for -REply STRing). Some examples of its use are:<BR> -_FROM_ == {Your Boss} => _RESTR_{"> "}<BR> -_FROM_ == {My Wife} => _RESTR_{":* "}<BR> -_FROM_ == {Perter Flinstone;Wilma Flinstone} => _RESTR_{"_INIT_ > "}<BR> - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> - -</BODY> -</HTML> -====== h_config_smtp_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_smtp-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_smtp-rules"--></H1> - -<P> This option is used to specify which SMTP server should be used when -sending a message, if this rule is not defined, or the execution of the rule -results in no server selected, then Alpine will look for -the value from the role that is being used to compose the message. If no smtp -server is defined in that role or you are not using a role, then Alpine will get -the name of the server from the -<A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> configuration -option according to the rules used in that variable. - -<P> The function associated to this configuration option is _SMTP_, an example -of the use of this function is<BR> -_ADDRESSTO_ == {peter@bedrock.com} => _SMTP_{smtp.bedrock.com} - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> - -</BODY> -</HTML> -====== h_config_startup_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_startup-rules"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_startup-rules"--></H1> - -<P> This option is used when a folder is being opened. You can use it to specify its <A -HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A> and override -Alpine's global value set for all folders. - -<P> An example of the usage of this option is:<BR> -_FOLDER_ == {Lynx;pine-info;_NEWS_} => _STARTUP_{first-unseen} - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P><End of help on this topic> - -</BODY> -</HTML> -====== h_config_new_rules ===== -<HTML> -<HEAD> -<TITLE>OPTION: New Rules Explained</TITLE> -</HEAD> -<BODY> -<H1>OPTION: New Rules Explained</H1> - -This is a quite powerful option. Here you can define rules that override -the values of any other option you have set in Alpine. - -<P> - For example, you can set your folders to be sorted in a certain way when -you open them (say by Arrival). You may want, however, your newsgroups to -be sorted by thread. The set of "rules" options allows you to -configure this and many other options, including the index-format for -specific folders, the way the subject is displayed in the index screen or -the reply-leadin-string, to name a few. - -<P> - Every rule has three parts: a condition, a separator and an action. The -action is what will happen if the condition of the rule is satisified. - -<P> - Here is an example: - -<P> - _FROM_ == {Fred Flinstone} => _SAVE_{Fred} - -<P> - Here the separator is "=>". Whatever is to the left of the separator -is the condition (that is _FROM_ == {Fred Flinstone}) and to the right is -the action (_SAVE_{Fred}). The condition means that the rule will be -applied only if the message that you are reading is from "Fred -Flinstone", and the action will be that you will be offered to save -it in the folder "Fred", whenever you press the letter -"S" to save a message. - -<P> - The separator is always "=>", with one exception to be seen -later. But for the most part this will be the only one you will ever need. - -<P> - Now let us see how to do it. There are 13 functions already defined for -you. These are: _EXEC_, _INDEX_, _REPLACE_, _REPLY_, _RESUB_, _SAVE_, -_SIGNATURE_, _SORT_, _STARTUP_, _TRIM_, _REXTRIM_, _THREADSTYLE and -_THREADINDEX_. The parameter of a function has to be enclosed between -"{" and "}", so for example you can specify -_SAVE_{saved-messages} as a valid sentence. - -<P> - Later in the document you will find examples. Here is a short -description of what each function does: - -<P> -<UL> -<LI> _EXEC_ : This function takes as an argument a program. This program -gets as the input a file and must rewrite its output to that file, which -is then taken as the value to replace from the contents of that file. You -can use this function with -<A HREF="h_config_resub_rules"><!--#echo var="VAR_reply-subject-rules"--></A>, -<A HREF="h_config_replace_rules"><!--#echo var="VAR_replace-rules"--></A> and -<A HREF="h_config_forward_rules"><!--#echo var="VAR_forward-rules"--></A>. -See the help of those options for examples of how to use this function -and configure these rules. -<BR> <BR> -<LI> _INDEX_ : This function takes as an argument an index-format, and -makes that the index-format for the specified folder. -<BR> <BR> -<LI> _REPLACE_ : This function replaces the subject/from of the given e-mail by -another subject/from only when displaying the index. -<BR> <BR> -<LI> _REPLY_ : This function takes as an argument a definition of a -reply-leadin-string and makes this the reply-leading-string of the -specified folder or person. -<BR> <BR> -<LI> _RESTR_ : This function takes as an argument the value of the -reply-indent-string to be used to answer the message being replied to. -<BR> <BR> -<LI> _RESUB_ : This function replaces the subject of the given e-mail by -another subject only when replying to a message. -<BR> <BR> -<LI> _SAVE_ : The save function takes as an argument the name of a -possibly non existing folder, whenever you want to save a message, that -folder will be offered for you to save. -<BR> <BR> -<LI> _SIGNATURE_ : This function takes as an argument a signature file and -uses that file as the signature for the message you are about to -compose/reply/forward. -<BR> <BR> -<LI> _SMTP_ : This function takes as an argument the definition of a -SMTP server. -<BR> <BR> -<LI> _SORT_ : This function takes as an argument a Sort Style, and sorts a -specified folder in that sort order. -<BR> <BR> -<LI> _TRIM_ : This function takes as an argument a list of strings that -you want removed from another string. At this time this only works for -_FROM_ and _SUBJECT_. -<BR> <BR> -<LI> _REXTRIM_ : Same as _TRIM_ but its argument is one and -only one extended regular expression. -<BR> <BR> -<LI> _STARTUP_ : This function takes as an argument an -incoming-startup-rule, and open an specified folder using that rule. -<BR> <BR> -<LI> _THREADSTYLE_ : This function takes as an argument a -threading-display-style and uses it to display threads in a folder. -<BR> <BR> -<LI> _THREADINDEX_ : This function takes as an argument a -threading-index-style and uses it to display threads in a folder. -</UL> - -<P> -You must me wondering how to define the person/folder over who to apply -the action. This is done in the condition. When you specify a rule, the -rule is only executed if the condition is satisfied. In another words for -the rule: - -<P> - _FROM_ == {Fred Flinstone} => _SAVE_{Fred} - -<P> it will only be applied if the from is "Fred Flinstone". If -the From is "Wilma Flinstone" the rule will be skipped. - -<P> In order to test a condition you can use the following tokens (in -alphabetical order): _ADDRESS_, _CC_, _FOLDER_, _FROM_,_NICK_, _ROLE, -_SENDER_, _SUBJECT_ and _TO_. The token will always be tested against what -it is between "{" and "}" in the condition, this part -of the condition is called the "condition set". The definition -of each token can be found <A HREF="h_index_tokens">here</A>. - -<P> A special testing token called _PROCID_ can be used to differentiate -inside a rule, between two rules that are triggered by the same condition. -A full explanation of the _PROCID_ token can be found in -<A HREF="h_config_procid">this link</A>. - -<P> There are two more tokens related to the option -<A HREF="h_config_key_macro_rules">key-definition-rules</A>. Those tokens -are only specific to that option, and hence are not explained here. - -<P> You can also test in different ways, you can use the following -"test operands": <<, !<, >>, !>, == and !=. -All of them are two strings long. Here is the meaning of them: - -<P> -<UL> -<LI> << : It tests if the value of the token is contained in -the condition set. Here for example if the condition set were equal to -"Freddy", then the condition: _NICK_ << {Freddy}, would be true if -the value of _NICK_ were "Fred", "red" or "Freddy". You are just looking -for substrings here. -<LI> >> : It tests if the value of the token contains the value of -the condition set. Here for example if the condittion set were equal to -"Fred", then the condition: _FROM_ >> {Fred}, would be true if -the value of _FROM_ were "Fred Flinstone" or "Fred P. Flinstone" or "Freddy". -<LI> == : It tests if the value of the token is exactly equal to the value -of the set condition. For example _NICK_ == {Fred} will be false if the value -of _NICK_ is "Freddy" or "red". -<LI> !< : This is true only when << is false and viceversa. -<LI> !> : This is true only when >> is false and viceversa. -<LI> != : This is true only when == is false and viceversa. -</UL> - -<P> - Now let us say that you want the same action to be applied to more than -one person or folder, say you want "folder1" and "folder2" to be sorted by -Ordered Subject upon entering. Then you can list them all of them in the -condition part separting them by a ";". Here is the way to do it. - -<P> - _FOLDER_ << {folder1; folder2} => _SORT_{OrderedSubj} - -<P> - Here is the first subtelty about these definitions. Notice that the -following rule: - -<P> - _FOLDER_ == {folder1; folder2} => _SORT_{Reverse OrderedSubj} - -<P> works only for "folder1" but not for "folder2". This is because the -comparison of the name of the folder is done with whatever is in between -"{", ";" or "}", so in the above rule you would be testing <BR> -"folder2" == " folder2". The extra space makes the difference. -The reason why the first rule does not fail is because -"folder2" << " folder2" is actually -true. If something ever fails this may be something to look into. - -<P> - Here are a few examples of what we have talked about before. - -<P> -_NICK_ == {lisa;kika} => _SAVE_{_NICK_/_NICK_} <BR> -This means that if the nick is lisa, it will -save the message in the folder "lisa/lisa", and if the nick -is "kika", it will save the message in the folder "kika/kika" - -<P> -_FOLDER_ == {Lynx} -> lynx <BR> -This, is an abreviation of the following rule:<BR> -_FOLDER_ == {Lynx} => _SAVE_{lynx} <BR> -(note the change in separator from "=>" to "->"). In the future -I will use that abreviation. - -<P> _FOLDER_ << {comp.mail.pine; pine-info; pine-alpha} -> pine <BR> -Any message in the folders "comp.mail.pine", "pine-info" or "pine-alpha" -will be saved to the folder "pine". - -<P> _FROM_ << {Pine Master} -> pine <BR> -Any message whose From field contains -"Pine Master" will be saved in the folder pine. - -<P> _FOLDER_ << {Lynx; pine-info; comp.mail.pine} => -_INDEX_{IMAPSTATUS MSGNO DATE FROMORTO(33%) SUBJECT(66%)} <BR> Use a -different index-format for the folders "Lynx", "pine-info" and -"comp.mail.pine", where the size is not present. - -<P> _FOLDER_ == {Lynx;pine-info} => _REPLY_{*** _FROM_ (_ADDRESS_) -wrote in the _FOLDER_ list _SMARTDATE_("Today" "today" "on -_LONGDATE_"):}<BR> If a message is in one of the incoming folders "Lynx" -or "pine-info", create a reply-leadin-string that acknowledges that. Note -the absence of "," in the function _SMARTDATE_. For example answering to a -message in the pine-info list would look like: - -<P> -*** Steve Hubert (hubert@cac.washington.edu) wrote in the pine-info list today: - -<P> -However replying for a message in the Lynx list would look: - -<P> -*** mattack@area.com (mattack@area.com) wrote in the Lynx list today: - -<P> -If you write in more than one language you can use this feature to create -Reply-leadin-strings in different languages. - -<P> Note that at least for people you can create particular -reply-leadin-string using the role features, but it does not work as this -one does. This seems to be the right way to do it. - -<P> _FOLDER_ << {Lynx; comp.mail.pine; pine_info; pine-alpha} => -_SORT_{OrderedSubj}<BR> This means upon opening, sort the folders "Lynx", -"comp.mail.pine", etc in ordered subject. All the others use the default -sort order. You can not sort in reverse in this form. The possible -arguments of this function are listed in the definition of the -default-sort-rule (Arrival, scorE, siZe, etc). - -<P> The last examples use the function _TRIM_ which has a special form. -This function can only be used in the index list. - -<P> _FOLDER_ << {Lynx} => _SUBJECT_ := _TRIM_{lynx-dev }<BR> In -the folder "Lynx" eliminate from the subject the string "lynx-dev " (with -the space at the end). For example a message whose subject is "Re: -lynx-dev unvisited Visited Links", would be shown in the index with -subject: "Re: unvisited Visited Links", making the subject shorter and -giving the same information. - -<P> _FROM_ >> {Name (Comment)} => _FROM_ := -_TRIM_{ (Comment)}<BR> Remove the part " (Comment)" -from the _FROM_, so when displaying in the index the real From "Name" -will appear. - -<P> _SUBJECT_ == {} => _RESUB_{Re: your mail without subject} -If there is no subject in the message, use the subject "Re: your mail -wiyhout subject" as a subject for the reply message. - -<P> You can add more complexity to your rules by checking more than one -conditions before a rule is executed. For example: Assume that you want to -answer every email that contains the string "bug report", with the subject -"Re: About your bug report", you could make - -<P> -_SUBJECT_ == {bug report} => _RESUB_{Re: About your _SUBJECT_} - -<P> The problem with this construction is that if the person emails you -back, then the next time you answer the message the subject will be: "Re: -About your Re: About your bug report", so it grew. You may want to avoid -this growth by using the following rule: - -<P> -_SUBJECT_ >> {bug report} && _SUBJECT_ !> {Re: } => _RESUB_{Re: About your _SUBJECT_}<BR> - -<P> -which will only add the string "Re: About your" only the first time the -message is replied. - -<P> - Say your personal name is "Fred Flinstones", and assume that you don't -like to see "To: comp.mail.pine" in every post you make to this newsgroup, -but instead would like to see it as everyone else sees it. <BR> -_FOLDER_ == {comp.mail.pine} && _FROM_ == {Fred Flinstones} => _FROM_ := _REPLACE_{_FROM_} - -<P> - You can also list your index by nick, in the following way:<BR> -_NICK_ != {} => _FROM_ := _REPLACE_{_NICK_} - -<P> - If you want to open the folder "pine-info" in the first non-read message -use the rule:<BR> -_FOLDER_ == {pine-info} => _STARTUP_{first-unseen} - -<P> - If you want to move your deleted messages to a folder, called "Trash", use -the following rule:<BR> -_FLAG_ >> {D} -> Trash - -<P> -The reason why the above test is not "_FLAG_ == {D}" is because that would mean -that this is the only flag set in the message. It's better to test by containment in this case. - -<P> If you want to use a specific signature when you are in a specific collection -use the following rule:<BR> -_COLLECTION_ == {Mail} => _SIGNATURE_{/full/path/to/.signature} - -<P> Finally about the question of which rule will be executed. Only the -first rule that matches will be executed. It is important to notice though -that "saving" rules do not compete with "sorting" rules. So the first -"saving" rule that matches will be executed in the case of saving and so -on. - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_char_set ===== <HTML> <HEAD> @@ -24234,43 +22827,6 @@ That won't work because spell works in a different way. <End of help on this topic> </BODY> </HTML> -====== h_config_special_text_to_color ===== -<HTML> -<HEAD> -<TITLE>OPTION: <!--#echo var="VAR_special-text-color"--></TITLE> -</HEAD> -<BODY> -<H1>OPTION: <!--#echo var="VAR_special-text-color"--></H1> - -Use this option to enter patterns (text or regular expressions) that -Alpine will highlight in the body of the text that is not part of a handle -(an internal or external link that Alpine paints in a different color). - -<P> -Enter each pattern in a different line. Pine will internally merge these -patterns (by adding a "|" character), or you can add them all in one line -by separating them by a "|" character. There is only a <A -HREF="h_regex_text">set</A> of regular expressions that are matched. - -<P> -Pine will use the colors defined in the -<A HREF="h_config_special_text_color">Special Text Color</A> variable. -to paint any match. - -<P> -If the Special Text Color is not set, setting this variable will not -cause that special text to be indicated in any special way. It will look -like any normal text. You must set those colors in order to make Pine -paint the screen differently when it finds the patterns specified in this -variable. - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_display_filters ===== <HTML> <HEAD> @@ -24435,12 +22991,6 @@ specified. Command Modifying Tokens: <DL> -<DT>_ADDRESS_</DT> -<DD>When the command is executed, this token is replaced -with the address of the person sending the message in the format -mailbox@host. -</DD> - <DT>_RECIPIENTS_</DT> <DD>When the command is executed, this token is replaced with the space delimited list of recipients of the @@ -27553,76 +26103,6 @@ the From field is used to show the relationships instead of the Subject field. <End of help on this topic> </BODY> </HTML> -====== h_config_thread_display_style_rule ===== -<HTML> -<HEAD> -<TITLE>OPTION: Threading-Display-Style-Rule</TITLE> -</HEAD> -<BODY> -<H1>OPTION: Threading-Display-Style-Rule</H1> - -This option is very similar to <A HREF="h_config_thread_disp_style"> -<!--#echo var="VAR_threading-display-style"--></A>, but it is a rule which specifies the -display styles for a thread that you want displayed in a specific -folder or collection. -<P> -The token to be used in this function is _THREADSTYLE_. Here there is -an example of its use -<P> -_FOLDER_ == {pine-info} => _THREADSTYLE_{mutt-like} -<P> -The values that can be given for the _THREADSTYLE_ function are the -values of the threading-display-style function, which can be found -listed in the <A HREF="h_config_thread_disp_style">threading-display-style</A> -configuration option. - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> -====== h_config_thread_index_style_rule ===== -<HTML> -<HEAD> -<TITLE>OPTION: Threading-Index-Style-Rule</TITLE> -</HEAD> -<BODY> -<H1>OPTION: Threading-Index-Style-Rule</H1> - -This option is very similar to <A HREF="h_config_thread_index_style"> -<!--#echo var="VAR_threading-index-style"--></A>, but it is a rule which specifies the -index styles for a thread that you want displayed in a specific -folder or collection. -<P> -The token to be used in this function is _THREADINDEX_. Here there is -an example of its use -<P> -_FOLDER_ == {pine-info} => _THREADINDEX_{regular-index-with-expanded-threads} -<P> -The values that can be given for the _THREADINDEX_ function are the -values of the threading-index-display function, which can be found -listed in the <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A> -configuration option. - -<P> This configuration option is just one of many that allow you to -override the value of some global configurations within Alpine. There is a -help text explaining how to define all of them, which you can read by -following this <A HREF="h_config_new_rules">link</A>. - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_pruning_rule ===== <HTML> <HEAD> @@ -29529,22 +28009,6 @@ See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-chang <End of help on this topic> </BODY> </HTML> -====== h_config_use_domain ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_return-path-uses-domain-name"--> </TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_return-path-uses-domain-name"--></H1> - -If you enable this configuration option Pine will use your domain name and your -username in that domain name to construct your Return-Path header, if not Pine -will use the address that you have set in the From: field to construct it. - -<P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_use_sender_not_x ===== <HTML> <HEAD> @@ -30141,71 +28605,6 @@ of flowed text. <End of help on this topic> </BODY> </HTML> -====== h_config_alt_reply_menu ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></H1> - -This feature controls the menu that is displayed when Reply is selected. -If set, a list of options will be presented, with each option representing -the type of composition that could be used. This feature is most useful -for users who want to avoid being prompted with each option separately, or -would like to override some defaults set in your configuration for the -message that you are replying (e.g. you may have set the option to strip -signatures, but for the message you are answering you would like not to do -that) - -<P> -The way this feature works is as follows. Initially you get the question -if you want to include the message, and in the menu you will see several -options, each option is accompanied by some text explaining what will -happen if you press the associated command. For example, if you read the -text "S Strip Sig", it means that if you press the letter -"S" the signature will be stripped off the message you are -replying. Observer that the menu will change to -"S No Strip", which means that if you press "S", the -signature will not be stripped off from the message. Your choices are -activated when you press RETURN. - -<P> -Another way to remember what Pine will do, is that what will be done is -exactly the opposite of what you read in the menu. - -<P> -The possible options are: - -<OL> -<LI> A: This determines if Pine will include or not the attachments sent to -you in the message that you are replying. By default Pine will use the value -of the configuration option -<A HREF="h_config_attach_in_reply"><!--#echo var="FEAT_include-attachments-in-reply"--></A>, but -you can use this option to override such behavior in a per message basis. - -<LI> F: To decide if you want to send flowed text or not. This option appears -unless you have quelled sending flowed text. - -<LI> H: This option determines if the headers of a message are to be -included in the body of the message that is being replied. By default Pine -will use the value of the configuration option -<A HREF="h_config_include_header"><!--#echo var="FEAT_include-header-in-reply"--></A>, but -you can use this option to override such behavior in a per message basis. - -<LI> R: To set a role, if you do not want Pine to set one automatically for you -or would like to set one when you can not select any. - -<LI> S: To strip the signature from a message, only available is the feature - <a href="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></a> or the -<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a> option are -enabled. - -</OL> -<P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_del_from_dot ===== <HTML> <HEAD> @@ -30729,38 +29128,6 @@ Ctrl-B key can be used to select the previous web hostnames in the same way. <End of help on this topic> </BODY> </HTML> -====== h_config_enable_long_url ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-long-url"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-long-url"--></H1> - -This feature modifies the behavior of Alpine's MESSAGE TEXT screen. When this feature -is set alpine will attempt to recognize long urls (those that spread over several -lines in the text) for the HTTP protocol, even when they have not been enclosed between -delimiters "<" and ">". - -<P>The normal behavior in Alpine is that if a URL is preceeded by the "<" -character and this URL was not finished before the end of the line, then a -continuation of the URL is searched in the following line(s). Normally, this type of -URLs will be ended by the ">" character, and if it is not, there is a -possibility of including erroneous text into the URL. - -<P>Enabling this feature will make Alpine search for a continuation of certain URLs in -lines following its location. This will be of great help most times, but in some cases -the algorithm will catch some text into the URL that is not part of the URL. - -<P>If you find that Alpine failed to recognize correctly a URL simply edit the URL before -passing it to your browser. - -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_enable_view_addresses ===== <HTML> <HEAD> @@ -30795,27 +29162,6 @@ Ctrl-B key can be used to select the previous web hostnames in the same way. <End of help on this topic> </BODY> </HTML> -====== h_config_circular_tab ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_enable-circular-tab"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_enable-circular-tab"--></H1> - -<P> -This Feature is like -<A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>, -in the sense that you can use TAB to browse through all of your Incoming -Folders checking for new mail. Once it gets to the last folder of the -collection it goes back to check again until it returns to the original -folder where it started. -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_enable_view_arrows ===== <HTML> <HEAD> @@ -31089,49 +29435,6 @@ than across the columns as is the default. <End of help on this topic> </BODY> </HTML> -====== h_config_courier_list ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_courier-folder-list"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_courier-folder-list"--></H1> - -In a maildir collection, a folder could be used as a directory to store -folders. In the Courier server if you create a folder, then a directory -with the same name is created. If you use this patch to access a -collection created by the Courier server, then the display of such -collection will look confusing. The best way to access a maildir -collection created by the Courier server is by using the "#mc/" -prefix instead of the "#md/" prefix. If you use this alternate -prefix, then this feature applies to you, otherwise you can safely ignore -the text that follows. -<P> -Depending on if you have enabled the option -<a href="h_config_separate_fold_dir_view"><!--#echo var="FEAT_separate-folder-and-directory-entries"--></a> -a folder may be listed as "folder[.]", or as two entries in the -list by "folder" and "folder.". -<P> -If this option is disabled, Pine will list local folders that are in Courier -style format, as "folder", and those that are also directories as -"folder[.]". This makes the default display cleaner. -<P> -If this feature is enabled then creating folders in a maildir collection -will create a directory with the same name. If this feature is disabled, then -a folder is considered a directory only if it contains subfolders, so you can -not create a directory with the same name as an exisiting folder unless -you create a subfolder of that folder first (e.g. if you have a folder -called "foo" simply add "foo.bar" directly. This will -create the directory "foo" and the subfolder "bar" of it). -<P> -Observe that this feature works only for maildir collections that are accessed -locally. If a collection is accessed remotely then this feature has no value, -as the report is created in a server, and Pine only reports what received -from the server in this case. -<P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_verbose_post ===== <HTML> <HEAD> @@ -31286,29 +29589,6 @@ them as deleted in the INBOX. Messages in the INBOX marked with an <End of help on this topic> </BODY> </HTML> -====== h_config_auto_read_msgs_rules ===== -<HTML> -<HEAD> -<TITLE>FEATURE: auto-move-read-msgs-using-rules</TITLE> -</HEAD> -<BODY> -<H1>FEATURE: auto-move-read-msgs-using-rules</H1> -This feature controls an aspect of Alpine's behavior upon quitting. If set, -and the -<A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A> -option is also set, then Alpine will automatically transfer all read -messages to the designated folder using the rules that you have defined in -your -<A HREF="h_config_save_rules">"<!--#echo var="VAR_save-rules"-->"</A> and mark -them as deleted in the INBOX. Messages in the INBOX marked with an -"N" (meaning New, or unseen) are not affected. -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_auto_fcc_only ===== <HTML> <HEAD> @@ -31759,23 +30039,6 @@ Reply Use, Forward Use, and Compose Use. <End of help on this topic> </BODY> </HTML> -====== h_config_enhanced_thread ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_enhanced-fancy-thread-support"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_enhanced-fancy-thread-support"--></H1> - -If this option is set certain commands in Pine will operate in loose -threads too. For example, the command ^R marks a thread deleted, but if -this feature is set, it will remove all threads that share the same missing -parent with this thread. - -<P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_news_cross_deletes ===== <HTML> <HEAD> @@ -32254,40 +30517,6 @@ but that is not implemented. <End of help on this topic> </BODY> </HTML> -====== h_config_ignore_size ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></H1> - -When you have an account residing in an IMAP server, Alpine gets the size of -each message from the server. However, when Alpine saves a message residing -in an IMAP server, Alpine computes the size of the message independently. If -these two numbers do not match for a message, Alpine asks you if you still -want to take the risk of saving the message, since data corruption or loss -of data could result of this save. - -<P> -Sometimes the root of this problem is that the server is defective, and -there will not be loss of information when saving such message. Enabling -this feature will make Aline ignore such error and continue saving the -message. If you can determine that this is the case, enable this feature -so that the saving operation will succeed. An example of a defective server -is the Gmail IMAP server. Another example is some versions of the Exchange -server. - -<P> -It is recommended that this feature be disabled most of the time and only -enabled when you find a server which you can determine that has the above -mentioned defect, but be disabled again after making this operation -succeed. - -<P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_force_low_speed ===== <HTML> <HEAD> @@ -32975,30 +31204,6 @@ to see the available Editing and Navigation commands. <End of help on this topic> </BODY> </HTML> -====== h_config_special_text_color ===== -<HTML> -<HEAD> -<TITLE>OPTION: Special Text Color</TITLE> -</HEAD> -<BODY> -<H1>OPTION: Special Text Color</H1> - -Sets the color Pine uses for coloring any text in the body of the message -that is not part of a handle (and internal or external link that Pine -paints in a different color). By default, this variable is not defined, -which means that text that matches the pattern is not painted in any -particular way. This variable must be set in a special form if you -want text to be painted. - -<P> -<A HREF="h_color_setup">Descriptions of the available commands</A> -<P> -Look <A HREF="h_edit_nav_cmds">here</A> -to see the available Editing and Navigation commands. -<P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_index_arrow_color ===== <HTML> <HEAD> @@ -34808,28 +33013,6 @@ messages. <End of help on this topic> </BODY> </HTML> -====== h_config_mark_for_group ===== -<HTML> -<HEAD> -<TITLE>FEATURE: <!--#echo var="FEAT_mark-for-me-in-group"--></TITLE> -</HEAD> -<BODY> -<H1>FEATURE: <!--#echo var="FEAT_mark-for-me-in-group"--></H1> - -This feature affects Alpine's MESSAGE INDEX display. -By default, a '+' is displayed in the first column if the -message is addressed directly to you. -When this feature is set and the message is addressed to you as part of a group message -(that is, your address appears in the To: field, but there is more than one recipient), then a -'.' character is displayed instead. - -<P> -<UL> -<LI><A HREF="h_finding_help">Finding more information and requesting help</A> -</UL><P> -<End of help on this topic> -</BODY> -</HTML> ====== h_config_mark_for_cc ===== <HTML> <HEAD> @@ -34839,7 +33022,7 @@ When this feature is set and the message is addressed to you as part of a group <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1> This feature affects Alpine's MESSAGE INDEX display. -By default, a '+' or a '.' is displayed in the first column if the +By default, a '+' is displayed in the first column if the message is addressed directly to you. When this feature is set and the message is not addressed to you, then a '-' character is displayed if the message is instead Cc'd directly |