From fee81d0fc769f0b5734e7a8ee9531a0ac7e10c1b Mon Sep 17 00:00:00 2001 From: Rocco Rutte Date: Sun, 31 Aug 2008 15:27:11 +0200 Subject: [PATCH] Manual: Use quoting for DocBook rather than ``''. All quotes characters are now rendered to Unicode quote chars in the HTML output (as does, too) but still " for manual.txt. --- doc/makedoc.c | 21 ++- doc/manual.xml.head | 434 ++++++++++++++++++++++---------------------- doc/manual.xml.tail | 4 +- init.h | 36 ++-- 4 files changed, 257 insertions(+), 238 deletions(-) diff --git a/doc/makedoc.c b/doc/makedoc.c index 36259fe86..ba82bdfdc 100644 --- a/doc/makedoc.c +++ b/doc/makedoc.c @@ -1185,7 +1185,26 @@ static int print_it (int special, char *str, FILE *out, int docstat) if (docstat & D_TAB) fputs (str, out); else - sgml_fputs (str, out); + { + while (*str) + { + for (; *str; str++) + { + if (!strncmp (str, "``", 2)) + { + fputs ("", out); + str++; + } + else if (!strncmp (str, "''", 2)) + { + fputs ("", out); + str++; + } + else + sgml_fputc (*str, out); + } + } + } break; } } diff --git a/doc/manual.xml.head b/doc/manual.xml.head index ac8327baf..3c9d4545c 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -13,7 +13,7 @@ - ``All mail clients suck. This one just sucks less.'' -me, circa 1995 + All mail clients suck. This one just sucks less. -me, circa 1995 @@ -160,7 +160,7 @@ pages. See the Mutt homepage for more The keybindings described in this section are the defaults as distributed. Your local system administrator may have altered the defaults for your site. -You can always type ``?'' in any menu to display the current bindings. +You can always type ? in any menu to display the current bindings. @@ -175,10 +175,10 @@ either the mutt man page or the reference. Mutt is a text-based application which interacts with users through different menus which are mostly line-/entry-based or page-based. A -line-based menu is the so-called ``index'' menu (listing all messages of -the currently opened folder) or the ``alias'' menu (allowing you to +line-based menu is the so-called index menu (listing all messages of +the currently opened folder) or the alias menu (allowing you to select recipients from a list). Examples for page-based menus are the -``pager'' (showing one message at a time) or the ``help'' menu listing +pager (showing one message at a time) or the help menu listing all available key bindings. @@ -192,7 +192,7 @@ interactive commands. Because Mutt allows for customizing almost all key bindings, there're -so-called ``functions'' which can be executed manually (using the +so-called functions which can be executed manually (using the command line) or in macros. Macros allow the user to bind a sequence of commands to a single key or a short key sequence instead of repeating a sequence of actions over and over. @@ -201,7 +201,7 @@ sequence of actions over and over. Many commands (such as saving or copying a message to another folder) can be applied to a single message or a set of messages (so-called -``tagged'' messages). To help selecting messages, Mutt provides a rich +tagged messages). To help selecting messages, Mutt provides a rich set of message patterns (such as recipients, sender, body contents, date sent/received, etc.) which can be combined into complex expressions using the boolean and and or @@ -211,7 +211,7 @@ messages. -Mutt supports a ``hook'' concept which allows the user to execute +Mutt supports a hook concept which allows the user to execute arbitrary configuration commands and functions in certain situations such as entering a folder, starting a new message or replying to an existing one. These hooks can be used to highly customize Mutt's @@ -363,8 +363,8 @@ the history's valuable entries with unwanted entries. Similar to many other mail clients, there are two modes in which mail is read in Mutt. The first is the index of messages in the mailbox, which is -called the ``index'' in Mutt. The second mode is the display of the -message contents. This is called the ``pager.'' +called the index in Mutt. The second mode is the display of the +message contents. This is called the pager. @@ -428,11 +428,11 @@ in the index menu can be customized using the In addition to who sent the message and the subject, a short summary of the disposition of each message is printed beside the message number. -Zero or more of the ``flags'' in +Zero or more of the flags in may appear, some of which can be turned on or off using these functions: <set-flag> and <clear-flag> -bound by default to ``w'' and ``W'' respectively. +bound by default to w and W respectively. @@ -523,10 +523,10 @@ the pager, such as <delete-message> or <cop Also, the internal pager supports a couple other advanced features. For -one, it will accept and translate the ``standard'' nroff sequences for +one, it will accept and translate the standard nroff sequences for bold and underline. These sequences are a series of either the letter, backspace (ˆH), the letter again for bold or the letter, backspace, -``_'' for denoting underline. Mutt will attempt to display these +_ for denoting underline. Mutt will attempt to display these in bold and underline respectively if your terminal supports them. If not, you can use the bold and underline color objects to specify a color or mono attribute for them. @@ -691,7 +691,7 @@ upon startup so you must explicitly source the fil This function will search the current message for content signed or -encrypted with PGP the ``traditional'' way, that is, without proper +encrypted with PGP the traditional way, that is, without proper MIME tagging. Technically, this function will temporarily change the MIME content types of the body parts containing PGP data; this is similar to the <edit-type> function's @@ -742,7 +742,7 @@ to send. -<enter-command> (default: ``:'') +<enter-command> (default: :) @@ -916,14 +916,14 @@ The bindings shown in are available in the Bouncing a message sends the message as-is to the recipient you specify. Forwarding a message allows you to add comments or modify the message you are forwarding. These items are discussed -in greater detail in the next chapter ``Forwarding -and Bouncing Mail.'' +in greater detail in the next chapter Forwarding +and Bouncing Mail. Mutt will then enter the compose menu and prompt you for the -recipients to place on the ``To:'' header field. Next, it will ask -you for the ``Subject:'' field for the message, providing a default if +recipients to place on the To: header field. Next, it will ask +you for the Subject: field for the message, providing a default if you are replying to or forwarding a message. See also $askcc, $askbcc, @@ -977,7 +977,7 @@ message. y<send-message>send the message s<edit-subject>edit the Subject S<smime-menu>select S/MIME options -f<edit-fcc>specify an ``Fcc'' mailbox +f<edit-fcc>specify an Fcc mailbox p<pgp-menu>select PGP options P<postpone-message>postpone this message until later q<quit>quit (abort) sending the message @@ -998,7 +998,7 @@ will be attached to the message you are sending. Note that certain operations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that folder. The %r in $status_format will change to -a ``A'' to indicate that you are in attach-message mode. +a A to indicate that you are in attach-message mode. @@ -1053,8 +1053,8 @@ If you want to use PGP, you can specify -``E'' selects encryption, ``S'' selects signing and -``S<id>'' selects signing with the given key, setting +E selects encryption, S selects signing and +S<id> selects signing with the given key, setting $pgp_sign_as permanently. @@ -1131,25 +1131,25 @@ The flags sequence (%f) will expand to one of the flags in The capabilities field (%c) expands to a two-character sequence representing a key's capabilities. The first character gives -the key's encryption capabilities: A minus sign (``-'') means -that the key cannot be used for encryption. A dot (``.'') means that +the key's encryption capabilities: A minus sign (-) means +that the key cannot be used for encryption. A dot (.) means that it's marked as a signature key in one of the user IDs, but may -also be used for encryption. The letter ``e'' indicates that +also be used for encryption. The letter e indicates that this key can be used for encryption. The second character indicates the key's signing capabilities. Once -again, a ``-'' implies ``not for signing'', ``.'' implies +again, a - implies not for signing, . implies that the key is marked as an encryption key in one of the user-ids, and -``s'' denotes a key which can be used for signing. +s denotes a key which can be used for signing. Finally, the validity field (%t) indicates how well-certified a user-id -is. A question mark (``?'') indicates undefined validity, a minus -character (``-'') marks an untrusted association, a space character -means a partially trusted association, and a plus character (``+'') +is. A question mark (?) indicates undefined validity, a minus +character (-) marks an untrusted association, a space character +means a partially trusted association, and a plus character (+) indicates complete validity. @@ -1196,7 +1196,7 @@ function. Finally, to abandon your changes, leave the menu, or Note that different remailers do have different capabilities, indicated in the %c entry of the remailer menu lines (see $mix_entry_format). Most important is -the ``middleman'' capability, indicated by a capital ``M'': This +the middleman capability, indicated by a capital M: This means that the remailer in question cannot be used as the final element of a chain, but will only forward messages to other mixmaster remailers. For details on the other capabilities, please @@ -1216,7 +1216,7 @@ have a look at the mixmaster documentation. for short) are text/plain messages that consist of paragraphs which a receiver's mail client may reformat to its own needs which mostly means to customize line lengths regardless of what the sender sent. Technically this is -achieved by letting lines of a ``flowable'' paragraph end in spaces +achieved by letting lines of a flowable paragraph end in spaces except for the last line. @@ -1248,9 +1248,9 @@ the compose menu, mutt properly space-stuffes the message. all lines starting with a space -lines starting with the word ``From'' +lines starting with the word From followed by space -all lines starting with ``>'' which +all lines starting with > which is not intended to be a quote character @@ -1309,7 +1309,7 @@ recipients specified in the Bcc header. Forwarding a message, on the other hand, allows you to modify the message before it is resent (for example, by adding your own comments). Bouncing is done using the <bounce> function and forwarding -using the <forward> function bound to ``b'' and ``f'' +using the <forward> function bound to b and f respectively. @@ -1320,7 +1320,7 @@ attachment, depending on the value of the $m like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, respectively. The desired forwarding format may depend on the content, therefore $mime_forward is a quadoption which, for -example, can be set to ``ask-no''. +example, can be set to ask-no. @@ -1348,7 +1348,7 @@ message even if you exit Mutt and then restart it at a later time. Once a message is postponed, there are several ways to resume it. From the -command line you can use the ``-p'' option, or if you compose a new +command line you can use the -p option, or if you compose a new message from the index or pager you will be prompted if postponed messages exist. If multiple messages are currently postponed, the postponed menu will pop up and you can select which message you would @@ -1377,11 +1377,11 @@ See also the $postpone quad-option. Location of initialization files -While the default configuration (or ``preferences'') make Mutt +While the default configuration (or preferences) make Mutt usable right out of the box, it is often desirable to tailor Mutt to suit your own tastes. When Mutt is first invoked, it will attempt to -read the ``system'' configuration file (defaults set by your local -system administrator), unless the ``-n'' command line option is specified. This file is typically +read the system configuration file (defaults set by your local +system administrator), unless the -n command line option is specified. This file is typically /usr/local/share/mutt/Muttrc or /etc/Muttrc. Mutt will next look for a file named .muttrc in your home directory. If this file does not exist and your home directory has @@ -1402,7 +1402,7 @@ sourced instead of the Muttrc file. The same is true of the configuration file, if you have a file .muttrc-0.88.6 in your home directory, when you run mutt version 0.88.6, it will source this file instead of the default .muttrc file. The version number is the -same which is visible using the ``-v'' command line switch or using the show-version key (default: +same which is visible using the -v command line switch or using the show-version key (default: V) from the index menu. @@ -1420,7 +1420,7 @@ set realname='Mutt user' ; ignore x- The hash mark, or pound sign -(``#''), is used as a ``comment'' character. You can use it to +(#), is used as a comment character. You can use it to annotate your initialization file. All text after the comment character to the end of the line is ignored. For example, @@ -1446,8 +1446,8 @@ quotes, but not for single quotes. \ quotes the next character, just as in shells such as bash and zsh. -For example, if want to put quotes ``"'' inside of a string, you can use -``\'' to force the next character to be a literal instead of interpreted +For example, if want to put quotes " inside of a string, you can use +\ to force the next character to be a literal instead of interpreted character. @@ -1457,8 +1457,8 @@ set realname="Michael \"MuttDude\" Elkins" -``\\'' means to insert a literal ``\'' into the line. -``\n'' and ``\r'' have their usual C meanings of linefeed and +\\ means to insert a literal \ into the line. +\n and \r have their usual C meanings of linefeed and carriage-return, respectively. @@ -1477,14 +1477,14 @@ backquotes (``). For example, my_hdr X-Operating-System: `uname -a` -The output of the Unix command ``uname -a'' will be substituted before the +The output of the Unix command uname -a will be substituted before the line is parsed. Note that since initialization files are line oriented, only the first line of output from the Unix command will be substituted. Both environment variables and mutt variables can be accessed by -prepending ``$'' to the name of the variable. For example, +prepending $ to the name of the variable. For example, @@ -1493,8 +1493,8 @@ set record=+sent_on_$HOSTNAME will cause mutt to save outgoing messages to a folder named -``sent_on_kremvax'' if the environment variable HOSTNAME is set to -``kremvax.'' (See $record for +sent_on_kremvax if the environment variable HOSTNAME is set to +kremvax. (See $record for details.) @@ -1601,13 +1601,13 @@ Usage: alias [ -group name< It's usually very cumbersome to remember or type out the address of someone -you are communicating with. Mutt allows you to create ``aliases'' which map +you are communicating with. Mutt allows you to create aliases which map a short string to a full address. Note: if you want to create an alias for more than -one address, you must separate the addresses with a comma (``,''). +one address, you must separate the addresses with a comma (,). @@ -1617,7 +1617,7 @@ the named group. -To remove an alias or aliases (``*'' means all aliases): +To remove an alias or aliases (* means all aliases): @@ -1805,10 +1805,10 @@ recalling a message the user was composing, but saved until later. key is the key (or key sequence) you wish to bind. To specify a control character, use the sequence \Cx, where x is the letter of the control character (for example, to specify control-A use -``\Ca''). Note that the case of x as well as \C is +\Ca). Note that the case of x as well as \C is ignored, so that \CA, \Ca, \cA and \ca are all equivalent. An alternative form is to specify the key as a three digit -octal number prefixed with a ``\'' (for example \177 is +octal number prefixed with a \ (for example \177 is equivalent to \c?). In addition, key may be a symbolic name as shown in . @@ -1853,7 +1853,7 @@ be a symbolic name as shown in . key does not need to be enclosed in quotes unless it contains a -space (`` '') or semi-colon (``;''). +space ( ) or semi-colon (;). @@ -1906,7 +1906,7 @@ muttrc. -Note: if you use the ``!'' shortcut for $spoolfile at the beginning of the pattern, you must place it +Note: if you use the ! shortcut for $spoolfile at the beginning of the pattern, you must place it inside of double or single quotes in order to distinguish it from the logical not operator for the expression. @@ -1928,11 +1928,11 @@ folder-hook mutt set sort=threads However, the sorting method is not restored to its previous value when reading a different mailbox. To specify a default command, use the -pattern ``.'' before other folder-hooks adjusting a value on a per-folder basis +pattern . before other folder-hooks adjusting a value on a per-folder basis because folder-hooks are evaluated in the order given in the configuration file. The following example will set the sort variable to date-sent for all folders but to threads -for all folders containing ``mutt'' in their name. +for all folders containing mutt in their name. @@ -1970,7 +1970,7 @@ commas separating them. key and sequence are expanded by the same rules as the key bindings with some additions. The first is that control characters in sequence can also be specified -as ˆx. In order to get a caret (`ˆ'') you need to use +as ˆx. In order to get a caret (ˆ) you need to use ˆˆ. Secondly, to specify a certain key such as up or to invoke a function directly, you can use the format <key name> and <function name>. For a listing of key @@ -2034,14 +2034,14 @@ in the header/body of a message, index matches pa error (error messages printed by Mutt) hdrdefault (default color of the message header in the pager) indicator (arrow or bar used to indicate the current item in a menu) -markers (the ``+'' markers at the beginning of wrapped lines in the pager) +markers (the + markers at the beginning of wrapped lines in the pager) message (informational messages) normal quoted (text matching $quote_regexp in the body of a message) quoted1, quoted2, ..., quotedN (higher levels of quoting) search (hiliting of words in the pager) signaturestatus (mode lines used to display info about the mailbox or message) -tilde (the ``˜'' used to pad blank lines in the pager) +tilde (the ˜ used to pad blank lines in the pager) tree (thread tree drawn in the message index and attachment menu) underline (hiliting underlined patterns in the body of messages) @@ -2098,7 +2098,7 @@ setting this variable. Note: The uncolor command can be applied to the index object only. It removes entries from the list. You must specify the same pattern -specified in the color command for it to be removed. The pattern ``*'' is +specified in the color command for it to be removed. The pattern * is a special token which means to clear the color index list of all entries. @@ -2112,7 +2112,7 @@ for your xterm), since color names may then lose their normal meaning. If your terminal does not support color, it is still possible change the video -attributes through the use of the ``mono'' command: +attributes through the use of the mono command: @@ -2158,18 +2158,18 @@ you to specify header fields which you don't normally want to see in the pager. You do not need to specify the full header field name. For example, -``ignore content-'' will ignore all header fields that begin with the pattern -``content-''. ``ignore *'' will ignore all headers. +ignore content- will ignore all header fields that begin with the pattern +content-. ignore * will ignore all headers. -To remove a previously added token from the list, use the ``unignore'' command. -The ``unignore'' command will make Mutt display headers with the given pattern. -For example, if you do ``ignore x-'' it is possible to ``unignore x-mailer''. +To remove a previously added token from the list, use the unignore command. +The unignore command will make Mutt display headers with the given pattern. +For example, if you do ignore x- it is possible to unignore x-mailer. -``unignore *'' will remove all tokens from the ignore list. +unignore * will remove all tokens from the ignore list. @@ -2197,7 +2197,7 @@ which mutt will attempt to present these headers to you when viewing messages. -``unhdr_order *'' will clear all previous headers from the order list, +unhdr_order * will clear all previous headers from the order list, thus removing the header order effects set by the system-wide startup file. @@ -2245,7 +2245,7 @@ alternates user@example -mutt will consider ``some-user@example'' as +mutt will consider some-user@example as being your address, too which may not be desired. As a solution, in such cases addresses should be specified as: @@ -2273,7 +2273,7 @@ To remove a regular expression from the alternates list, use Likewise, if the regexp for an alternates command matches an entry on the unalternates list, that unalternates entry will be removed. If the regexp for unalternates -is ``*'', all entries on alternates will be removed. +is *, all entries on alternates will be removed. @@ -2305,15 +2305,15 @@ of the Mail-Followup-To header is controlled by the More precisely, Mutt maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing -list is known. To mark a mailing list as known, use the ``lists'' -command. To mark it as subscribed, use ``subscribe''. +list is known. To mark a mailing list as known, use the lists +command. To mark it as subscribed, use subscribe. You can use regular expressions with both commands. To mark all messages sent to a specific bug report's address on mutt's bug tracking system as list mail, for instance, you could say -``subscribe [0-9]*@bugs.guug.de''. Often, it's sufficient to just +subscribe [0-9]*@bugs.guug.de. Often, it's sufficient to just give a portion of the list's e-mail address. @@ -2321,13 +2321,13 @@ give a portion of the list's e-mail address. Specify as much of the address as you need to to remove ambiguity. For example, if you've subscribed to the Mutt mailing list, you will receive mail addressed to mutt-users@mutt.org. So, to tell Mutt -that this is a mailing list, you could add ``lists mutt-users@'' to your +that this is a mailing list, you could add lists mutt-users@ to your initialization file. To tell mutt that you are subscribed to it, -add ``subscribe mutt-users'' to your initialization file instead. +add subscribe mutt-users to your initialization file instead. If you also happen to get mail from someone whose address is mutt-users@example.com, you could use -``lists ^mutt-users@mutt\\.org$'' -or ``subscribe ^mutt-users@mutt\\.org$'' to +lists ^mutt-users@mutt\\.org$ +or subscribe ^mutt-users@mutt\\.org$ to match only mail from the actual list. @@ -2337,14 +2337,14 @@ to the named group. -The ``unlists'' command is used to remove a token from the list of -known and subscribed mailing-lists. Use ``unlists *'' to remove all +The unlists command is used to remove a token from the list of +known and subscribed mailing-lists. Use unlists * to remove all tokens. To remove a mailing list from the list of subscribed mailing lists, -but keep it on the list of known mailing lists, use ``unsubscribe''. +but keep it on the list of known mailing lists, use unsubscribe. @@ -2360,7 +2360,7 @@ Usage: mbox-hook [!]pattern pattern is a regular expression specifying the mailbox to treat as a -``spool'' mailbox and mailbox specifies where mail should be saved when +spool mailbox and mailbox specifies where mail should be saved when read. @@ -2401,14 +2401,14 @@ situations and how often Mutt checks for new mail). -The ``unmailboxes'' command is used to remove a token from the list -of folders which receive mail. Use ``unmailboxes *'' to remove all +The unmailboxes command is used to remove a token from the list +of folders which receive mail. Use unmailboxes * to remove all tokens. Note: the folders in the mailboxes command are resolved when -the command is executed, so if these names contain shortcut characters (such as ``='' and ``!''), any variable +the command is executed, so if these names contain shortcut characters (such as = and !), any variable definition that affects these characters (like $folder and $spoolfile) should be set before the mailboxes command. If none of these shorcuts are used, a local path should be absolute as @@ -2453,7 +2453,7 @@ fields which will be added to every message you send. -For example, if you would like to add an ``Organization:'' header field to +For example, if you would like to add an Organization: header field to all of your outgoing messages, you can put the command @@ -2469,22 +2469,22 @@ in your .muttrc. Note: space characters are not allowed between the keyword and -the colon (``:''). The standard for electronic mail (RFC2822) says that +the colon (:). The standard for electronic mail (RFC2822) says that space is illegal there, so Mutt enforces the rule. If you would like to add a header field to a single message, you should either set the $edit_headers variable, -or use the <edit-headers> function (default: ``E'') in the compose menu so +or use the <edit-headers> function (default: E) in the compose menu so that you can edit the header of your message along with the body. To remove user defined header fields, use the unmy_hdr -command. You may specify an asterisk (``*'') to remove all header -fields, or the fields to remove. For example, to remove all ``To'' and -``Cc'' header fields, you could use: +command. You may specify an asterisk (*) to remove all header +fields, or the fields to remove. For example, to remove all To and +Cc header fields, you could use: @@ -2741,7 +2741,7 @@ Usage: exec function [ fu This command can be used to execute any function. Functions are listed in the function reference. -``exec function'' is equivalent to ``push <function>''. +exec function is equivalent to push <function>. @@ -2770,7 +2770,7 @@ a match. Negative final scores are rounded up to 0. The unscore command removes score entries from the list. You must specify the same pattern specified in the score command for it to be -removed. The pattern ``*'' is a special token which means to clear the list +removed. The pattern * is a special token which means to clear the list of all score entries. @@ -2800,12 +2800,12 @@ to display spam tags only when they are defined for a given message.) Your first step is to define your external filter's spam patterns using the spam command. pattern should be a regular expression that matches a header in a mail message. If any message in the mailbox -matches this regular expression, it will receive a ``spam tag'' or -``spam attribute'' (unless it also matches a nospam pattern -- see +matches this regular expression, it will receive a spam tag or +spam attribute (unless it also matches a nospam pattern -- see below.) The appearance of this attribute is entirely up to you, and is governed by the format parameter. format can be any static text, but it also can include back-references from the pattern -expression. (A regular expression ``back-reference'' refers to a +expression. (A regular expression back-reference refers to a sub-expression contained within parentheses.) %1 is replaced with the first back-reference in the regex, %2 with the second, etc. @@ -2834,11 +2834,11 @@ set spam_separator=", " -If I then received a message that DCC registered with ``many'' hits -under the ``Fuz2'' checksum, and that PureMessage registered with a +If I then received a message that DCC registered with many hits +under the Fuz2 checksum, and that PureMessage registered with a 97% probability of being spam, that message's spam tag would read -90+/DCC-Fuz2, 97/PM. (The four characters before ``=many'' in a -DCC report indicate the checksum used -- in this case, ``Fuz2''.) +90+/DCC-Fuz2, 97/PM. (The four characters before =many in a +DCC report indicate the checksum used -- in this case, Fuz2.) @@ -2870,8 +2870,8 @@ only when two numbers are equal in value. (This is like UNIX's sort -n.) A message with no spam attributes at all -- that is, one that didn't match any of your spam patterns -- is sorted at lowest priority. Numbers are sorted next, beginning with 0 and ranging -upward. Finally, non-numeric strings are sorted, with ``a'' taking lower -priority than ``z''. Clearly, in general, sorting by spam tags is most +upward. Finally, non-numeric strings are sorted, with a taking lower +priority than z. Clearly, in general, sorting by spam tags is most effective when you can coerce your filter to give you a raw number. But in case you can't, mutt can still do something useful. @@ -2889,7 +2889,7 @@ If the pattern given to nospam is exactl remove the entry from the spam list, instead of adding an exception. Likewise, if the pattern for a spam command matches an entry on the nospam list, that nospam entry will be removed. If the -pattern for nospam is ``*'', all entries on both lists +pattern for nospam is *, all entries on both lists will be removed. This might be the default action if you use spam and nospam in conjunction with a folder-hook. @@ -2937,18 +2937,18 @@ boolean, number, string and quadoption. boolean variables assigned a positive integer value. string variables consist of any number of printable characters and must be enclosed in quotes if they contain spaces or tabs. You -may also use the escape sequences ``\n'' and ``\t'' for newline and tab, respectively. +may also use the escape sequences \n and \t for newline and tab, respectively. quadoption variables are used to control whether or not to be prompted for certain actions, or to specify a default action. A value of yes will cause the action to be carried out automatically as if you had answered yes to the question. Similarly, a value of no will cause the -action to be carried out as if you had answered ``no.'' A value of -ask-yes will cause a prompt with a default answer of ``yes'' and -ask-no will provide a default answer of ``no.'' +action to be carried out as if you had answered no. A value of +ask-yes will cause a prompt with a default answer of yes and +ask-no will provide a default answer of no. -Prefixing a variable with ``no'' will unset it. Example: set noaskbcc. +Prefixing a variable with no will unset it. Example: set noaskbcc. @@ -2989,12 +2989,12 @@ variables. The reset command resets all given variables to the compile time defaults (hopefully mentioned in this manual). If you use the command -set and prefix the variable with ``&'' this has the same +set and prefix the variable with & this has the same behavior as the reset command. -With the reset command there exists the special variable ``all'', +With the reset command there exists the special variable all, which allows you to reset all variables to their system defaults. @@ -3118,7 +3118,7 @@ from other files. For example, I place all of my aliases in -If the filename begins with a tilde (``˜''), it will be expanded to the +If the filename begins with a tilde (˜), it will be expanded to the path of your home directory. @@ -3139,7 +3139,7 @@ Usage: unhook [ * | hook-type This command permits you to flush hooks you have previously defined. -You can either remove all hooks by giving the ``*'' character as an +You can either remove all hooks by giving the * character as an argument, or you can remove all hooks of a specific type by saying something like unhook send-hook. @@ -3158,7 +3158,7 @@ through the mutt configuration, especially in the $index_format, $pager_format, $status_format, -and other ``*_format'' variables. These can be very straightforward, +and other *_format variables. These can be very straightforward, and it's quite possible you already know how to use them. @@ -3167,7 +3167,7 @@ The most basic format string element is a percent symbol followed by another character. For example, %s represents a message's Subject: header in the $index_format variable. The -``expandos'' available are documented with each format variable, but +expandos available are documented with each format variable, but there are general modifiers available with all formatting expandos, too. Those are our concern here. @@ -3178,7 +3178,7 @@ know them from Perl, Python, shell, or another langugage). These are the [-]m.n modifiers, as in %-12.12s. As with such programming languages, these modifiers allow you to specify the minumum and maximum size of the resulting string, as well as its -justification. If the ``-'' sign follows the percent, the string will +justification. If the - sign follows the percent, the string will be left-justified instead of right-justified. If there's a number immediately following that, it's the minimum amount of space the formatted string will occupy -- if it's naturally smaller than that, it @@ -3202,14 +3202,14 @@ characters for the %y expansion -- that's the X-Label: header, in $index_format. If the expansion results in a string less than 14 characters, it will be centered in a 14-character space. If the X-Label for a message were "test", that -expansion would look like `` test ''. +expansion would look like test . There are two very little-known modifiers that affect the way that an -expando is replaced. If there is an underline (``_'') character +expando is replaced. If there is an underline (_) character between any format modifiers (as above) and the expando letter, it will -expands in all lower case. And if you use a colon (``:''), it will +expands in all lower case. And if you use a colon (:), it will replace all decimal points with underlines. @@ -3219,7 +3219,7 @@ replace all decimal points with underlines. Filters -Any format string ending in a vertical bar (``|'') will be +Any format string ending in a vertical bar (|) will be expanded and piped through the first word in the string, using spaces as separator. The string returned will be used for display. If the returned string ends in %, it will be passed through @@ -3267,16 +3267,16 @@ terminal's title, if supported. All string patterns in Mutt including those in more complex patterns must be specified -using regular expressions (regexp) in the ``POSIX extended'' syntax (which +using regular expressions (regexp) in the POSIX extended syntax (which is more or less the syntax used by egrep and GNU awk). For your convenience, we have included below a brief description of this syntax. The search is case sensitive if the pattern contains at least one upper -case letter, and case insensitive otherwise. Note that ``\'' +case letter, and case insensitive otherwise. Note that \ must be quoted if used for a regular expression in an initialization -command: ``\\''. +command: \\. @@ -3301,27 +3301,27 @@ special meaning may be quoted by preceding it with a backslash. -The period ``.'' matches any single character. The caret ``ˆ'' and -the dollar sign ``$'' are metacharacters that respectively match +The period . matches any single character. The caret ˆ and +the dollar sign $ are metacharacters that respectively match the empty string at the beginning and end of a line. -A list of characters enclosed by ``['' and ``]'' matches any +A list of characters enclosed by [ and ] matches any single character in that list; if the first character of the list -is a caret ``ˆ'' then it matches any character not in the +is a caret ˆ then it matches any character not in the list. For example, the regular expression [0123456789] matches any single digit. A range of ASCII characters may be specified by giving the first and last characters, separated by a hyphen -``-''. Most metacharacters lose their special meaning inside -lists. To include a literal ``]'' place it first in the list. -Similarly, to include a literal ``ˆ'' place it anywhere but first. -Finally, to include a literal hyphen ``-'' place it last. +-. Most metacharacters lose their special meaning inside +lists. To include a literal ] place it first in the list. +Similarly, to include a literal ˆ place it anywhere but first. +Finally, to include a literal hyphen - place it last. Certain named classes of characters are predefined. Character classes -consist of ``[:'', a keyword denoting the class, and ``:]''. +consist of [:, a keyword denoting the class, and :]. The following classes are defined by the POSIX standard in @@ -3339,7 +3339,7 @@ The following classes are defined by the POSIX standard in [:blank:]Space or tab characters [:cntrl:]Control characters [:digit:]Numeric characters -[:graph:]Characters that are both printable and visible. (A space is printable, but not visible, while an ``a'' is both) +[:graph:]Characters that are both printable and visible. (A space is printable, but not visible, while an a is both) [:lower:]Lower-case alphabetic characters [:print:]Printable characters (characters that are not control characters) [:punct:]Punctuation characters (characters that are not letter, digits, control characters, or space characters) @@ -3376,10 +3376,10 @@ sorting purposes: A collating symbol is a multi-character collating element enclosed in -``[.'' and ``.]''. For example, if ``ch'' is a collating +[. and .]. For example, if ch is a collating element, then [[.ch.]] is a regexp that matches this collating element, while [ch] is a regexp that -matches either ``c'' or ``h''. +matches either c or h. @@ -3388,11 +3388,11 @@ matches either ``c'' or ``h''. An equivalence class is a locale-specific name for a list of -characters that are equivalent. The name is enclosed in ``[='' -and ``=]''. For example, the name ``e'' might be used to -represent all of ``è'' ``é'' and ``e''. In this case, +characters that are equivalent. The name is enclosed in [= +and =]. For example, the name e might be used to +represent all of è é and e. In this case, [[=e=]] is a regexp that matches any of -``è'', ``é'' and ``e''. +è, é and e. @@ -3431,7 +3431,7 @@ that respectively match the concatenated subexpressions. -Two regular expressions may be joined by the infix operator ``|''; +Two regular expressions may be joined by the infix operator |; the resulting regular expression matches any string matching either subexpression. @@ -3502,10 +3502,10 @@ shows several ways to select messages. %c GROUPmessages carbon-copied to any member of GROUP ~C EXPRmessages either to: or cc: EXPR %C GROUPmessages either to: or cc: to any member of GROUP -~d [MIN]-[MAX]messages with ``date-sent'' in a Date range +~d [MIN]-[MAX]messages with date-sent in a Date range ~Ddeleted messages -~e EXPRmessages which contains EXPR in the ``Sender'' field -%e GROUPmessages which contain a member of GROUP in the ``Sender'' field +~e EXPRmessages which contains EXPR in the Sender field +%e GROUPmessages which contain a member of GROUP in the Sender field ~Eexpired messages ~Fflagged messages ~f EXPRmessages originating from EXPR @@ -3514,7 +3514,7 @@ shows several ways to select messages. ~Gcryptographically encrypted messages ~h EXPRmessages which contain EXPR in the message header ~H EXPRmessages with a spam attribute matching EXPR -~i EXPRmessages which match EXPR in the ``Message-ID'' field +~i EXPRmessages which match EXPR in the Message-ID field ~kmessages which contain PGP key material ~L EXPRmessages either originated or received by EXPR %L GROUPmessage either originated or received by any member of GROUP @@ -3526,9 +3526,9 @@ shows several ways to select messages. ~pmessages addressed to you (consults alternates) ~Pmessages from you (consults alternates) ~Qmessages which have been replied to -~r [MIN]-[MAX]messages with ``date-received'' in a Date range +~r [MIN]-[MAX]messages with date-received in a Date range ~Rread messages -~s EXPRmessages having EXPR in the ``Subject'' field. +~s EXPRmessages having EXPR in the Subject field. ~Ssuperseded messages ~t EXPRmessages addressed to EXPR ~Ttagged messages @@ -3536,9 +3536,9 @@ shows several ways to select messages. ~Uunread messages ~vmessages part of a collapsed thread. ~Vcryptographically verified messages -~x EXPRmessages which contain EXPR in the ``References'' field +~x EXPRmessages which contain EXPR in the References field ~X [MIN]-[MAX]messages with MIN to MAX attachments *) -~y EXPRmessages which contain EXPR in the ``X-Label'' field +~y EXPRmessages which contain EXPR in the X-Label field ~z [MIN]-[MAX]messages with a size in the range MIN to MAX *) ~=duplicated messages (see $duplicate_threads) ~$unreferenced messages (requires threaded view) @@ -3555,13 +3555,13 @@ threads containing messages from you: ~(~P) Where EXPR is a regular expression. Special attention has to be made when using regular expressions inside of patterns. Specifically, -Mutt's parser for these patterns will strip one level of backslash (``\''), +Mutt's parser for these patterns will strip one level of backslash (\), which is normally used for quoting. If it is your intention to use a backslash in the regular expression, you will need to use two backslashes -instead (``\\''). You can force mutt to treat EXPR as a simple string +instead (\\). You can force mutt to treat EXPR as a simple string instead of a regular expression by using = instead of ˜ in the pattern name. For example, =b *.* will find all messages that contain -the literal string ``*.*''. Simple string matches are less powerful than +the literal string *.*. Simple string matches are less powerful than regular expressions but can be considerably faster. This is especially true for IMAP folders, because string matches can be performed on the server instead of by fetching every message. IMAP treats =h specially: @@ -3572,8 +3572,8 @@ its value. -*) The forms ``<[MAX]'', ``>[MIN]'', -``[MIN]-'' and ``-[MAX]'' +*) The forms <[MAX], >[MIN], +[MIN]- and -[MAX] are allowed, too. @@ -3584,7 +3584,7 @@ are allowed, too. Note that patterns matching 'lists' of addresses (notably c, C, p, P and t) match if there is at least one match in the whole list. If you want to make sure that all elements of that list match, you need to prefix your -pattern with ``ˆ''. +pattern with ˆ. This example matches all mails which only has recipients from Germany. @@ -3602,12 +3602,12 @@ This example matches all mails which only has recipients from Germany. Simple Patterns -Mutt supports two versions of so called ``simple searches'' which are +Mutt supports two versions of so called simple searches which are issued if the query entered for searching, limiting and similar operations does not seem to be a valid pattern (i.e. it does not contain -one of these characters: ``˜'', ``='' or ``%''). If the query is +one of these characters: ˜, = or %). If the query is supposed to contain one of these special characters, they must be escaped -by prepending a backslash (``\''). +by prepending a backslash (\). @@ -3616,10 +3616,10 @@ a keyword case-insensitively from : If that is the case, Mutt will use the shown pattern modifier instead. If a keyword would conflict with your search keyword, you need to turn it into a regular expression to avoid matching the keyword table. For -example, if you want to find all messages matching ``flag'' +example, if you want to find all messages matching flag (using $simple_search, see below but not meaning flagged messages) simply search for -``[f]lag''. +[f]lag. @@ -3670,8 +3670,8 @@ example: -would select messages which contain the word ``mutt'' in the list of -recipients and that have the word ``elkins'' in the ``From'' header +would select messages which contain the word mutt in the list of +recipients and that have the word elkins in the From header field. @@ -3708,8 +3708,8 @@ patterns: Here is an example illustrating a complex search pattern. This pattern will -select all messages which do not contain ``mutt'' in the ``To'' or ``Cc'' -field and which are from ``elkins''. +select all messages which do not contain mutt in the To or Cc +field and which are from elkins. @@ -3723,8 +3723,8 @@ field and which are from ``elkins''. Here is an example using white space in the regular expression (note the ' and " delimiters). For this to match, the mail's subject must -match the ``ˆJunk +From +Me$'' and it must be from either ``Jim +Somebody'' -or ``Ed +SomeoneElse'': +match the ˆJunk +From +Me$ and it must be from either Jim +Somebody +or Ed +SomeoneElse: @@ -3780,10 +3780,10 @@ Limit to messages matching: ~d 20/1/95-31/10 -If you omit the minimum (first) date, and just specify ``-DD/MM/YY'', all +If you omit the minimum (first) date, and just specify -DD/MM/YY, all messages before the given date will be selected. If you omit the maximum -(second) date, and specify ``DD/MM/YY-'', all messages after the given -date will be selected. If you specify a single date with no dash (``-''), +(second) date, and specify DD/MM/YY-, all messages after the given +date will be selected. If you specify a single date with no dash (-), only messages sent on the given date will be selected. @@ -3791,7 +3791,7 @@ only messages sent on the given date will be selected. Error Margins. You can add error margins to absolute dates. An error margin is a sign (+ or -), followed by a digit, followed by one of the units in . As a special case, you can replace the -sign by a ``*'' character, which is equivalent to giving identical plus and minus error margins. +sign by a * character, which is equivalent to giving identical plus and minus error margins.
@@ -3881,27 +3881,27 @@ messages all at once rather than one at a time. An example might be to save messages to a mailing list to a separate folder, or to delete all messages with a given subject. To tag all messages matching a pattern, use the <tag-pattern> function, which is bound to -``shift-T'' by default. Or you can select individual messages by -hand using the <tag-message> function, which is bound to ``t'' by +shift-T by default. Or you can select individual messages by +hand using the <tag-message> function, which is bound to t by default. See patterns for Mutt's pattern matching syntax. Once you have tagged the desired messages, you can use the -``tag-prefix'' operator, which is the ``;'' (semicolon) key by default. -When the ``tag-prefix'' operator is used, the next operation will +tag-prefix operator, which is the ; (semicolon) key by default. +When the tag-prefix operator is used, the next operation will be applied to all tagged messages if that operation can be used in that manner. If the $auto_tag variable is set, the next operation applies to the tagged messages -automatically, without requiring the ``tag-prefix''. +automatically, without requiring the tag-prefix. In macros or push commands, -you can use the ``tag-prefix-cond'' operator. If there are no tagged +you can use the tag-prefix-cond operator. If there are no tagged messages, mutt will "eat" the rest of the macro to abort it's execution. -Mutt will stop "eating" the macro when it encounters the ``end-cond'' +Mutt will stop "eating" the macro when it encounters the end-cond operator; after this operator the rest of the macro will be executed as normal. @@ -4122,12 +4122,12 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST to denote the start of a new message (this is often referred to as the -``From_'' line). +From_ line). MMDF. This is a variant of the mbox format. Each message is -surrounded by lines containing ``ˆAˆAˆAˆA'' (four control-A's). +surrounded by lines containing ˆAˆAˆAˆA (four control-A's). @@ -4236,18 +4236,18 @@ Now that Mutt knows what your mailing lists are, it can do several things, the first of which is the ability to show the name of a list through which you received a message (i.e., of a subscribed list) in the index menu display. This is useful to distinguish between -personal and list mail in the same mailbox. In the $index_format variable, the escape ``%L'' -will return the string ``To <list>'' when ``list'' appears in the -``To'' field, and ``Cc <list>'' when it appears in the ``Cc'' +personal and list mail in the same mailbox. In the $index_format variable, the escape %L +will return the string To <list> when list appears in the +To field, and Cc <list> when it appears in the Cc field (otherwise it returns the name of the author). -Often times the ``To'' and ``Cc'' fields in mailing list messages +Often times the To and Cc fields in mailing list messages tend to get quite large. Most people do not bother to remove the author of the message they are reply to from the list, resulting in two or more copies being sent to that person. The <list-reply> -function, which by default is bound to ``L'' in the index menu +function, which by default is bound to L in the index menu and pager, helps reduce the clutter by only replying to the known mailing list addresses instead of all recipients (except as specified by Mail-Followup-To, see below). @@ -4259,7 +4259,7 @@ a message to a list of recipients which includes one or several subscribed mailing lists, and if the $followup_to option is set, mutt will generate a Mail-Followup-To header which contains all the recipients to whom you send this message, but not your address. This indicates that -group-replies or list-replies (also known as ``followups'') to this +group-replies or list-replies (also known as followups) to this message should only be sent to the original recipients of the message, and not separately to you - you'll receive your copy through one of the mailing lists you are subscribed to. @@ -4282,26 +4282,26 @@ this header if it doesn't exist when you send the message. The other method some mailing list admins use is to generate a -``Reply-To'' field which points back to the mailing list address rather +Reply-To field which points back to the mailing list address rather than the author of the message. This can create problems when trying to reply directly to the author in private, since most mail clients -will automatically reply to the address given in the ``Reply-To'' +will automatically reply to the address given in the Reply-To field. Mutt uses the $reply_to variable to help decide which address to use. If set to ask-yes or ask-no, you will be prompted as to whether or not you would like to use the address given in -the ``Reply-To'' field, or reply directly to the address given in the -``From'' field. When set to yes, the ``Reply-To'' field will be used when +the Reply-To field, or reply directly to the address given in the +From field. When set to yes, the Reply-To field will be used when present. -The ``X-Label:'' header field can be used to further identify mailing +The X-Label: header field can be used to further identify mailing lists or list subject matter (or just to annotate messages -individually). The $index_format variable's ``%y'' and -``%Y'' escapes can be used to expand ``X-Label:'' fields in the +individually). The $index_format variable's %y and +%Y escapes can be used to expand X-Label: fields in the index, and Mutt's pattern-matcher can match regular expressions to -``X-Label:'' fields with the ``˜y'' selector. ``X-Label:'' is not a +X-Label: fields with the ˜y selector. X-Label: is not a standard message header field, but it can easily be inserted by procmail and other mail filtering agents. @@ -4348,7 +4348,7 @@ mode when invoked from the command line with the -y option. For the pager, index and directory browser menus, Mutt contains the -<buffy-list> function (bound to ``.'' by default) +<buffy-list> function (bound to . by default) which will print a list of folders with new mail in the command line at the bottom of the screen. @@ -4420,7 +4420,7 @@ current message into a whole different thread. RFC1894 defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of as -``return receipts.'' +return receipts. @@ -4541,7 +4541,7 @@ attachment menu for a message. The attachment menu displays a list of the attachments in a message. From the attachment menu, you can save, print, pipe, delete, and view attachments. You can apply these operations to a group of attachments at once, by tagging the attachments -and by using the ``tag-prefix'' operator. You can also reply to the +and by using the tag-prefix operator. You can also reply to the current message from this menu, and only the current attachment (or the attachments tagged) will be quoted in your reply. You can view attachments as text, or view them using the mailcap viewer definition. @@ -5202,9 +5202,9 @@ application/postscript; ps2ascii %s; copiousoutput -``unauto_view'' can be used to remove previous entries from the autoview list. +unauto_view can be used to remove previous entries from the autoview list. This can be used with message-hook to autoview messages based on size, etc. -``unauto_view *'' will remove all previous entries. +unauto_view * will remove all previous entries. @@ -5403,14 +5403,14 @@ muttrc. Mutt supports several of optional features which can be enabled or disabled at compile-time by giving the configure script -certain arguments. These are listed in the ``Optional features'' section of +certain arguments. These are listed in the Optional features section of the configure --help output. Which features are enabled or disabled can later be determined from the output of mutt -v. If a compile option starts with -``+'' it is enabled and disabled if prefixed with ``-''. For example, if ++ it is enabled and disabled if prefixed with -. For example, if mutt was compiled using GnuTLS for encrypted communication instead of OpenSSL, mutt -v would contain: @@ -5437,7 +5437,7 @@ proto[s]://[username[:password]@]server[:port]/[path] proto is the communication protocol: imap for IMAP, pop for POP3 and -smtp for SMTP. If ``s'' for ``secure communication'' +smtp for SMTP. If s for secure communication is appended, mutt will attempt to establish an encrypted communication using SSL or TLS. If no explicit port is given, mutt will use the system's default for the given protocol. @@ -5446,7 +5446,7 @@ system's default for the given protocol. Since all protocols by mutt support authentication, the username may be given directly in the URL instead of using the pop_user or -imap_user variables. It may contain the ``@'' symbol +imap_user variables. It may contain the @ symbol being used by many mail systems as part of the login name. A password can be given, too but is not recommended if the URL is specified in a configuration file on disk. @@ -5480,7 +5480,7 @@ by running the configure script with the --enable-ssl=... option for OpenSSL or --enable-gnutls=... for GnuTLS). Mutt can then attempt to encrypt communication with remote servers if these protocols -are suffixed with ``s'' for ``secure communication''. +are suffixed with s for secure communication. @@ -5543,7 +5543,7 @@ Alternatively, a pine-compatible notation is also supported, ie -Note that not all servers use ``/'' as the hierarchy separator. Mutt should +Note that not all servers use / as the hierarchy separator. Mutt should correctly notice which separator is being used by the server and convert paths accordingly. @@ -5761,8 +5761,8 @@ account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"' Mutt contains two types of local caching: (1) -the so-called ``header caching'' and (2) the -so-called ``body caching'' which are both described in this section. +the so-called header caching and (2) the +so-called body caching which are both described in this section. @@ -5843,7 +5843,7 @@ For configuration, the variable $message_cachedir must point to a directory. There, mutt will create a hierarchy of subdirectories named like: proto:user@hostname where -proto is either ``pop'' or ``imap.'' Within +proto is either pop or imap. Within there for each folder, mutt stores messages in single files (just like Maildir) so that with manual symlink creation these cache directories can be examined with mutt as read-only Maildir folders. @@ -5886,8 +5886,8 @@ it should not be set in general but only occasionally. Exact address generation -Mutt supports the ``Name <user@host>'' address syntax for reading and -writing messages, the older ``user@host (Name)'' syntax is only supported when +Mutt supports the Name <user@host> address syntax for reading and +writing messages, the older user@host (Name) syntax is only supported when reading messages. The --enable-exact-address switch can be given to configure to build it with write-support for the latter syntax. EXACT_ADDRESS in the output of @@ -5980,7 +5980,7 @@ please refer to mutt's so-called When searching mailboxes either via a search or a limit action, for some patterns mutt distinguishes between regular expression and string searches. For regular expressions, patterns are prefixed with -``˜'' and with ``='' for string searches. +˜ and with = for string searches. @@ -6076,7 +6076,7 @@ To compose a new message -Mutt also supports a ``batch'' mode to send prepared messages. Simply redirect +Mutt also supports a batch mode to send prepared messages. Simply redirect input from the file you wish to send. For example, @@ -6086,14 +6086,14 @@ input from the file you wish to send. For example, -This command will send a message to ``professor@bigschool.edu'' with a subject -of ``data set for run #2''. In the body of the message will be the contents -of the file ``˜/run2.dat''. +This command will send a message to professor@bigschool.edu with a subject +of data set for run #2. In the body of the message will be the contents +of the file ˜/run2.dat. All files passed with -a file will be attached as a MIME -part to the message. To attach several files, use ``--'' to separate files and +part to the message. To attach several files, use -- to separate files and recipient addresses: mutt -a *.png -- some@one.org diff --git a/doc/manual.xml.tail b/doc/manual.xml.tail index 6d10820c2..7e9f3570e 100644 --- a/doc/manual.xml.tail +++ b/doc/manual.xml.tail @@ -67,11 +67,11 @@ The following people have been very helpful to the development of Mutt: David Jeske jeske@igcom.net Christophe Kalt kalt@hugo.int-evry.fr Tommi Komulainen Tommi.Komulainen@iki.fi -Felix von Leitner (a.k.a ``Fefe'') leitner@math.fu-berlin.de +Felix von Leitner (a.k.a Fefe) leitner@math.fu-berlin.de Brandon Long blong@fiction.net Jimmy Mäkelä jmy@flashback.net Lars Marowsky-Bree lmb@pointer.in-minden.de -Thomas ``Mike'' Michlmayr mike@cosy.sbg.ac.at +Thomas Mike Michlmayr mike@cosy.sbg.ac.at Andrew W. Nosenko awn@bcs.zp.ua David O'Brien obrien@Nuxi.cs.ucdavis.edu Clint Olsen olsenc@ichips.intel.com diff --git a/init.h b/init.h index fd454679b..427eac305 100644 --- a/init.h +++ b/init.h @@ -116,12 +116,12 @@ struct option_t MuttVars[] = { { "alias_format", DT_STR, R_NONE, UL &AliasFmt, UL "%4n %2f %t %-10a %r" }, /* ** .pp - ** Specifies the format of the data displayed for the `alias' menu. The + ** Specifies the format of the data displayed for the ``$alias'' menu. The ** following printf(3)-style sequences are available: ** .pp ** .dl ** .dt %a .dd alias name - ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion + ** .dt %f .dd flags - currently, a ``d'' for an alias marked for deletion ** .dt %n .dd index number ** .dt %r .dd address which alias expands to ** .dt %t .dd character which indicates if the alias is tagged for inclusion @@ -204,7 +204,7 @@ struct option_t MuttVars[] = { { "attach_format", DT_STR, R_NONE, UL &AttachFormat, UL "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] " }, /* ** .pp - ** This variable describes the format of the `attachment' menu. The + ** This variable describes the format of the ``attachment'' menu. The ** following printf-style sequences are understood: ** .pp ** .dl @@ -225,12 +225,12 @@ struct option_t MuttVars[] = { ** .dt %u .dd unlink (=to delete) flag ** .dt %X .dd number of qualifying MIME parts in this part and its children ** (please see the ``$attachments'' section for possible speed effects) - ** .dt %>X .dd right justify the rest of the string and pad with character "X" - ** .dt %|X .dd pad to the end of the line with character "X" - ** .dt %*X .dd soft-fill with character "X" as pad + ** .dt %>X .dd right justify the rest of the string and pad with character ``X'' + ** .dt %|X .dd pad to the end of the line with character ``X'' + ** .dt %*X .dd soft-fill with character ``X'' as pad ** .de ** .pp - ** For an explanation of `soft-fill', see the $$index_format documentation. + ** For an explanation of ``soft-fill'', see the $$index_format documentation. */ { "attach_sep", DT_STR, R_NONE, UL &AttachSep, UL "\n" }, /* @@ -316,7 +316,7 @@ struct option_t MuttVars[] = { ** This variable is \fIunset\fP by default and should only be enabled when ** new mail detection for these folder types is unreliable or doesn't work. ** .pp - ** Note that enabling this variable should happen before any ``mailboxes'' + ** Note that enabling this variable should happen before any ``$mailboxes'' ** directives occur in configuration files regarding mbox or mmdf folders ** because mutt needs to determine the initial new mail status of such a ** mailbox by performing a fast mailbox scan when it is defined. @@ -438,7 +438,7 @@ struct option_t MuttVars[] = { ** This variable controls whether or not mutt may automatically enable ** PGP encryption/signing for messages. See also $$crypt_autoencrypt, ** $$crypt_replyencrypt, - ** $$crypt_autosign, $$crypt_replysign'' and $$smime_is_default. + ** $$crypt_autosign, $$crypt_replysign and $$smime_is_default. */ { "crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, 1 }, /* @@ -474,7 +474,7 @@ struct option_t MuttVars[] = { ** variable at the time the hook is declared. The default value matches ** if the message is either from a user matching the regular expression ** given, or if it is from you (if the from address matches - ** ``alternates'') and is to or cc'ed to a user matching the given + ** ``$alternates'') and is to or cc'ed to a user matching the given ** regular expression. */ { "delete", DT_QUAD, R_NONE, OPT_DELETE, M_ASKYES }, @@ -619,12 +619,12 @@ struct option_t MuttVars[] = { { "folder", DT_PATH, R_NONE, UL &Maildir, UL "~/Mail" }, /* ** .pp - ** Specifies the default location of your mailboxes. A `+' or `=' at the + ** Specifies the default location of your mailboxes. A ``+'' or ``='' at the ** beginning of a pathname will be expanded to the value of this ** variable. Note that if you change this variable from the default ** value you need to make sure that the assignment occurs \fIbefore\fP - ** you use `+' or `=' for any other variables since expansion takes place - ** during the `set' command. + ** you use ``+'' or ``='' for any other variables since expansion takes place + ** during the ``$set'' command. */ { "folder_format", DT_STR, R_INDEX, UL &FolderFormat, UL "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f" }, /* @@ -1050,9 +1050,9 @@ struct option_t MuttVars[] = { ** .dt %c .dd number of characters (bytes) in the message ** .dt %C .dd current message number ** .dt %d .dd date and time of the message in the format specified by - ** ``date_format'' converted to sender's time zone + ** ``$$date_format'' converted to sender's time zone ** .dt %D .dd date and time of the message in the format specified by - ** ``date_format'' converted to the local time zone + ** ``$$date_format'' converted to the local time zone ** .dt %e .dd current message number in thread ** .dt %E .dd number of messages in current thread ** .dt %f .dd sender (address + real name), either From: or Return-Path: @@ -1062,7 +1062,7 @@ struct option_t MuttVars[] = { ** .dt %l .dd number of lines in the message (does not work with maildir, ** mh, and possibly IMAP folders) ** .dt %L .dd If an address in the To or CC header field matches an address - ** defined by the users ``subscribe'' command, this displays + ** defined by the users ``$subscribe'' command, this displays ** "To ", otherwise the same as %F. ** .dt %m .dd total number of message in the mailbox ** .dt %M .dd number of hidden messages if the thread is collapsed. @@ -1238,7 +1238,7 @@ struct option_t MuttVars[] = { { "metoo", DT_BOOL, R_NONE, OPTMETOO, 0 }, /* ** .pp - ** If unset, Mutt will remove your address (see the ``alternates'' + ** If unset, Mutt will remove your address (see the ``$alternates'' ** command) from the list of recipients when replying to a message. */ { "menu_context", DT_NUM, R_NONE, UL &MenuContext, 0 }, @@ -2358,7 +2358,7 @@ struct option_t MuttVars[] = { ** When set to 0, only a single message will appear before the reading ** the mailbox. ** .pp - ** Also see the $$write_inc variable and the ``Tuning'' section of the + ** Also see the $$write_inc variable and the ``$tuning'' section of the ** manual for performance considerations. */ { "read_only", DT_BOOL, R_NONE, OPTREADONLY, 0 }, -- 2.40.0