From cd7ffd1d3c1f20e726884c99fec9a3b19f88266f Mon Sep 17 00:00:00 2001 From: Richard Russon Date: Sat, 9 Sep 2017 17:08:56 +0100 Subject: [PATCH] docs: replace mutt refs with neomutt --- doc/manual.xml.head | 1136 +++++++++++++++++++++---------------------- init.h | 562 ++++++++++----------- opcodes.h | 6 +- 3 files changed, 852 insertions(+), 852 deletions(-) mode change 100755 => 100644 doc/manual.xml.head diff --git a/doc/manual.xml.head b/doc/manual.xml.head old mode 100755 new mode 100644 index 8ac3d6a87..1c75d5d09 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -3,7 +3,7 @@ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> - The Mutt E-Mail Client + The NeoMutt E-Mail Client Michael Elkins @@ -20,8 +20,8 @@ Introduction - Mutt is a small but very powerful - text-based MIME mail client. Mutt is highly configurable, and is well + NeoMutt is a small but very powerful + text-based MIME mail client. NeoMutt is highly configurable, and is well suited to the mail power user with advanced features like key bindings, keyboard macros, mail threading, regular expression searches and a powerful pattern matching language for selecting groups of messages. @@ -76,13 +76,13 @@ - Contributing to Mutt - There are various ways to contribute to the Mutt project. + Contributing to NeoMutt + There are various ways to contribute to the NeoMutt project. Especially for new users it may be helpful to meet other new and - experienced users to chat about Mutt, talk about problems and share + experienced users to chat about NeoMutt, talk about problems and share tricks. - Since translations of Mutt into other languages are highly - appreciated, the Mutt developers always look for skilled translators that + Since translations of NeoMutt into other languages are highly + appreciated, the NeoMutt developers always look for skilled translators that help improve and continue to maintain stale translations. For contributing code patches for new features and bug fixes, please refer to the developer pages at @@ -124,7 +124,7 @@ <create-alias> - named Mutt function + named NeoMutt function @@ -134,7 +134,7 @@ $mail_check - Mutt configuration option + NeoMutt configuration option @@ -146,7 +146,7 @@ Examples are presented as: - mutt -v + neomutt -v Within command synopsis, curly brackets ( {}) denote a set of options of which one is mandatory, square brackets ( @@ -156,8 +156,8 @@ Copyright - Mutt is Copyright © 1996-2016 Michael R. Elkins - me@mutt.org and others. + NeoMutt is Copyright © 1996-2016 Michael R. Elkins + me@neomutt.org and others. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at @@ -174,24 +174,24 @@ Getting Started - This section is intended as a brief overview of how to use Mutt. + This section is intended as a brief overview of how to use NeoMutt. There are many other features which are described elsewhere in the manual. - There is even more information available in the Mutt FAQ and various web + There is even more information available in the NeoMutt FAQ and various web pages. See the - Mutt homepage for more + NeoMutt homepage for more details. 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. - The first thing you need to do is invoke Mutt, simply by typing - mutt at the command line. There are various command-line - options, see either the Mutt man page or the + The first thing you need to do is invoke NeoMutt, simply by typing + neomutt at the command line. There are various command-line + options, see either the NeoMutt man page or the reference. Core Concepts - Mutt is a text-based application which interacts with users through + NeoMutt 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 @@ -205,11 +205,11 @@ finally the command line. The command line is used to display informational and error messages as well as for prompts and for entering interactive commands. - Mutt is configured through variables which, if the user wants to + NeoMutt is configured through variables which, if the user wants to permanently use a non-default value, are written to configuration files. - Mutt supports a rich config file syntax to make even complex + NeoMutt supports a rich config file syntax to make even complex configuration files readable and commentable. - Because Mutt allows for customizing almost all key bindings, there + Because NeoMutt allows for customizing almost all key bindings, there are 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 @@ -218,7 +218,7 @@ 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 + tagged messages). To help selecting messages, NeoMutt 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 @@ -226,15 +226,15 @@ or operations as well as negating. These patterns can also be used to (for example) search for messages or to limit the index to show only matching messages. - Mutt supports a + NeoMutt 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 behavior including + These hooks can be used to highly customize NeoMutt's behavior including managing multiple identities, customizing the display for a folder or even implementing auto-archiving based on a per-folder basis and much more. - Besides an interactive mode, Mutt can also be used as a + Besides an interactive mode, NeoMutt can also be used as a command-line tool only send messages. It also supports a mailx(1)-compatible interface, see for a complete list of @@ -247,7 +247,7 @@ Index The index is the screen that you usually see first when you start - Mutt. It gives an overview over your emails in the currently opened + NeoMutt. It gives an overview over your emails in the currently opened mailbox. By default, this is your system mailbox. The information you see in the index is a list of emails, each with its number on the left, its flags (new email, important email, email that has been forwarded or @@ -271,7 +271,7 @@ information about them below the email body, or, if the attachments are text files, you can view them directly in the pager. To give the user a good overview, it is possible to configure - Mutt to show different things in the pager with different colors. + NeoMutt to show different things in the pager with different colors. Virtually everything that can be described with a regular expression can be colored, e.g. URLs, email addresses or smileys. @@ -293,14 +293,14 @@ turned on and off, it can be themed and the list style can be configured. This part of the manual is suitable for beginners. If you already - know Mutt you could skip ahead to the main + know NeoMutt you could skip ahead to the main Sidebar guide. If you just want to get started, you could use the sample Sidebar muttrc. - To check if Mutt supports + To check if NeoMutt supports Sidebar, look for the string - +sidebar in the mutt version. - mutt -v + +sidebar in the neomutt version. + neomutt -v Let's turn on the Sidebar: @@ -337,7 +337,7 @@ Seas 1/7| 4 ! Feb 28 Summer Jackson (264) Lemon Navigation The Sidebar adds some new - functions to Mutt. + functions to NeoMutt. The user pressed the c key to <change-folder>to the @@ -998,7 +998,7 @@ color sidebar_divider color8 default lists the current configuration of key bindings and their associated commands including a short description, and currently unbound functions that still need to be associated with a key binding (or alternatively, - they can be called via the Mutt command prompt). + they can be called via the NeoMutt command prompt). @@ -1024,7 +1024,7 @@ color sidebar_divider color8 default Attachment Menu - As will be later discussed in detail, Mutt features a good and + As will be later discussed in detail, NeoMutt features a good and stable MIME implementation, that is, it supports sending and receiving messages of arbitrary MIME types. The attachment menu displays a message's structure in detail: what content parts are attached to which @@ -1175,7 +1175,7 @@ color sidebar_divider color8 default Introduction - Mutt has a built-in line editor for inputting text, e.g. email + NeoMutt has a built-in line editor for inputting text, e.g. email addresses or filenames. The keys used to manipulate text input are very similar to those of Emacs. See for a full reference of available @@ -1357,7 +1357,7 @@ color sidebar_divider color8 default History - Mutt maintains a history for the built-in editor. The number of + NeoMutt maintains a history for the built-in editor. The number of items is controlled by the $history variable and can be made persistent using an external file specified using @@ -1365,10 +1365,10 @@ color sidebar_divider color8 default $save_history. You may cycle through them at an editor prompt by using the <history-up>and/or - <history-down>commands. Mutt will remember the + <history-down>commands. NeoMutt will remember the currently entered text as you cycle through history, and will wrap around to the initial entry line. - Mutt maintains several distinct history lists, one for each of + NeoMutt maintains several distinct history lists, one for each of the following categories: @@ -1391,7 +1391,7 @@ color sidebar_divider color8 default everything else - Mutt automatically filters out consecutively repeated items from + NeoMutt automatically filters out consecutively repeated items from the history. If $history_remove_dups is set, all repeated items are removed from the history. It also mimics the @@ -1404,9 +1404,9 @@ color sidebar_divider color8 default Reading Mail Similar to many other mail clients, there are two modes in which - mail is read in Mutt. The first is a list of messages in the mailbox, + mail is read in NeoMutt. The first is a list of messages in the mailbox, which is called the - index menu in Mutt. The second mode is the display of the + index menu in NeoMutt. The second mode is the display of the message contents. This is called the pager. The next few sections describe the functions provided in each of @@ -1669,7 +1669,7 @@ color sidebar_divider color8 default The Pager - By default, Mutt uses its built-in pager to display the contents + By default, NeoMutt uses its built-in pager to display the contents of messages (an external pager such as less(1)can be configured, see $pager variable). The pager is very similar @@ -1745,14 +1745,14 @@ color sidebar_divider color8 default 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 + _ for denoting underline. NeoMutt 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. Additionally, the internal pager supports the ANSI escape - sequences for character attributes. Mutt translates them into the - correct color and character settings. The sequences Mutt supports + sequences for character attributes. NeoMutt translates them into the + correct color and character settings. The sequences NeoMutt supports are: \e[ Ps; @@ -1855,7 +1855,7 @@ color sidebar_divider color8 default - Mutt uses these attributes for handling + NeoMutt uses these attributes for handling text/enriched messages, and they can also be used by an external autoview script for highlighting @@ -1881,8 +1881,8 @@ color sidebar_divider color8 default threads provide a hierarchy of messages where replies are linked to their parent message(s). This organizational form is extremely useful in mailing lists where different parts of the - discussion diverge. Mutt displays threads as a tree structure. - In Mutt, when a mailbox is + discussion diverge. NeoMutt displays threads as a tree structure. + In NeoMutt, when a mailbox is sorted by threads, there are a few additional functions available in the @@ -2017,7 +2017,7 @@ color sidebar_divider color8 default format string conditionals. Technically, every reply should contain a list of its parent - messages in the thread tree, but not all do. In these cases, Mutt + messages in the thread tree, but not all do. In these cases, NeoMutt groups them by subject which can be controlled using the $strict_threads variable. @@ -2042,7 +2042,7 @@ color sidebar_divider color8 default $alias_file variable for future use - Mutt does not read the + NeoMutt does not read the $alias_file upon startup so you must explicitly @@ -2172,7 +2172,7 @@ color sidebar_divider color8 default <resend-message> (default: Esc e) - Mutt takes the current message as a template for a new + NeoMutt takes the current message as a template for a new message. This function is best described as "recall from arbitrary folders". It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that @@ -2191,7 +2191,7 @@ color sidebar_divider color8 default Asks for an external Unix command and executes it. The $wait_key can be used to control - whether Mutt will wait for a key to be pressed when the command + whether NeoMutt will wait for a key to be pressed when the command returns (presumably to let the user read the output of the command), based on the return status of the named command. If no command is given, an interactive shell is executed. @@ -2307,7 +2307,7 @@ color sidebar_divider color8 default Forwarding and Bouncing Mail. - Mutt will then enter the + NeoMutt will then enter the compose menu and prompt you for the recipients to place on the To:header field when you hit @@ -2322,9 +2322,9 @@ color sidebar_divider color8 default $autoedit, $bounce, $fast_reply, and - $include for changing how and if Mutt + $include for changing how and if NeoMutt asks these questions. - When replying, Mutt fills these fields with proper values + When replying, NeoMutt fills these fields with proper values depending on the reply type. The types of replying supported are: @@ -2354,7 +2354,7 @@ color sidebar_divider color8 default After getting recipients for new messages, forwards or replies, - Mutt will then automatically start your + NeoMutt will then automatically start your $editor on the message body. If the $edit_headers variable is set, the headers will be at the top of the message in your editor; the message @@ -2550,7 +2550,7 @@ color sidebar_divider color8 default When editing the header because of $edit_headers being set, there are a several pseudo headers available which will not be included in sent - messages but trigger special Mutt behavior. + messages but trigger special NeoMutt behavior. Fcc: Pseudo Header @@ -2559,7 +2559,7 @@ color sidebar_divider color8 default Fcc: filename - as a header, Mutt will pick up + as a header, NeoMutt will pick up filename just as if you had used the <edit-fcc>function in the compose menu. It can later be changed from the @@ -2603,7 +2603,7 @@ color sidebar_divider color8 default In-Reply-To: Header When replying to messages, the In-Reply-To:header contains the Message-Id of - the message(s) you reply to. If you remove or modify its value, Mutt + the message(s) you reply to. If you remove or modify its value, NeoMutt will not generate a References:field, which allows you to create a new message thread, for example to create a new message to a mailing @@ -2619,18 +2619,18 @@ color sidebar_divider color8 default Sending Cryptographically Signed/Encrypted Messages - If you have told Mutt to PGP or S/MIME encrypt a message, it will + If you have told NeoMutt to PGP or S/MIME encrypt a message, it will guide you through a key selection process when you try to send the - message. Mutt will not ask you any questions about keys which have a + message. NeoMutt will not ask you any questions about keys which have a certified user ID matching one of the message recipients' mail addresses. However, there may be situations in which there are several keys, weakly certified user ID fields, or where no matching keys can be found. In these cases, you are dropped into a menu with a list of keys - from which you can select one. When you quit this menu, or Mutt can't + from which you can select one. When you quit this menu, or NeoMutt can't find any matching keys, you are prompted for a user ID. You can, as usually, abort this prompt using - ^G. When you do so, Mutt will return to the compose + ^G. When you do so, NeoMutt will return to the compose screen. Once you have successfully finished the key selection, the message will be encrypted using the selected public keys when sent @@ -2713,21 +2713,21 @@ color sidebar_divider color8 default sent. Technically this is achieved by letting lines of a flowable paragraph end in spaces except for the last line. - While for text-mode clients like Mutt it's the best way to + While for text-mode clients like NeoMutt it's the best way to assume only a standard 80x25 character cell terminal, it may be desired to let the receiver decide completely how to view a message. - Mutt Support - Mutt only supports setting the required + NeoMutt Support + NeoMutt only supports setting the required format=flowed MIME parameter on outgoing messages if the $text_flowed variable is set, specifically it does not add the trailing spaces. After editing the initial message text and before entering the - compose menu, Mutt properly space-stuffs the message. + compose menu, NeoMutt properly space-stuffs the message. Space-stuffing is required by RfC3676 defining format=flowed and means to prepend a space to: @@ -2749,11 +2749,11 @@ color sidebar_divider color8 default - Mutt only supports space-stuffing for the first two types of + NeoMutt only supports space-stuffing for the first two types of lines but not for the third: It is impossible to safely detect whether a leading >character starts a quote or not. - Furthermore, Mutt only applies space-stuffing + Furthermore, NeoMutt only applies space-stuffing once after the initial edit is finished. All leading spaces are to be removed by receiving clients to @@ -2762,7 +2762,7 @@ color sidebar_divider color8 default Editor Considerations - As Mutt provides no additional features to compose + As NeoMutt provides no additional features to compose f=f messages, it's completely up to the user and his editor to produce proper messages. Please consider your editor's documentation if you intend to send @@ -2780,7 +2780,7 @@ color sidebar_divider color8 default Reformatting - Mutt has some support for reformatting when viewing and + NeoMutt has some support for reformatting when viewing and replying to format=flowed messages. In order to take advantage of these, @@ -2804,7 +2804,7 @@ color sidebar_divider color8 default If $reflow_space_quotes is - unset, mutt will still add one trailing space after all the + unset, NeoMutt will still add one trailing space after all the quotes in the pager (but not when replying). @@ -2860,7 +2860,7 @@ color sidebar_divider color8 default compose menu, the body of your message and attachments are stored in the mailbox specified by the $postponed variable. This means that you - can recall the message even if you exit Mutt and then restart it at a + can recall the message even if you exit NeoMutt 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 @@ -2886,15 +2886,15 @@ color sidebar_divider color8 default Location of Initialization Files - When Mutt starts up it looks for two configuration files -- one + When NeoMutt starts up it looks for two configuration files -- one system file and one user file. - Mutt searches for several different file names when looking for - config. It looks for NeoMutt config files before Mutt config files and + NeoMutt searches for several different file names when looking for + config. It looks for NeoMutt config files before NeoMutt config files and versioned config before plain config. For example: - Mutt config file search order + NeoMutt config file search order @@ -2909,13 +2909,13 @@ color sidebar_divider color8 default
- This allows the user to create separate Mutt and NeoMutt config + This allows the user to create separate NeoMutt and NeoMutt config files on the same system. Location of system config files - Mutt will search for a system config file in a - mutt directory in several places. First it searches + NeoMutt will search for a system config file in a + neomutt directory in several places. First it searches the locations specified in the XDG_CONFIG_DIRS environment variable, which defaults to @@ -2925,11 +2925,11 @@ color sidebar_divider color8 default The system config file will not be read if the -n option is used on the command line. - Mutt will read just one file, the first file it finds, from the + NeoMutt will read just one file, the first file it finds, from the list below. - Mutt system config file locations + NeoMutt system config file locations @@ -2939,36 +2939,36 @@ color sidebar_divider color8 default - /etc/xdg/mutt/neomuttrc-20170912 + /etc/xdg/neomutt/neomuttrc-20170912 NeoMutt release version - /etc/xdg/mutt/neomuttrc + /etc/xdg/neomutt/neomuttrc - /etc/xdg/mutt/Muttrc + /etc/xdg/neomutt/Muttrc Note the case of the filename - /etc/mutt/neomuttrc-20170912 + /etc/neomutt/neomuttrc-20170912 NeoMutt release version - /etc/mutt/neomuttrc + /etc/neomutt/neomuttrc - /etc/mutt/Muttrc + /etc/neomutt/Muttrc Note the case of the filename - /usr/share/mutt/neomuttrc-20170912 + /usr/share/neomutt/neomuttrc-20170912 NeoMutt release version - /usr/share/mutt/neomuttrc + /usr/share/neomutt/neomuttrc - /usr/share/mutt/Muttrc + /usr/share/neomutt/Muttrc Note the case of the filename @@ -2978,22 +2978,22 @@ color sidebar_divider color8 default Location of user config files - Mutt will search for a user config file in several places. First + NeoMutt will search for a user config file in several places. First it looks in the directory specified in the XDG_CONFIG_HOME environment variable, which defaults to - ~/.config/mutt. Next, it looks in + ~/.config/neomutt. Next, it looks in ~(your home directory). Finally, it tries - ~/.mutt. + ~/.neomutt. You may specify your own location for the user config file using the -F option on the command line. - Mutt will read just one file, the first file it finds, from the + NeoMutt will read just one file, the first file it finds, from the list below.
- Mutt user config file locations + NeoMutt user config file locations @@ -3003,14 +3003,14 @@ color sidebar_divider color8 default - ~/.config/mutt/neomuttrc-20170912 + ~/.config/neomutt/neomuttrc-20170912 NeoMutt release version - ~/.config/mutt/neomuttrc + ~/.config/neomutt/neomuttrc - ~/.config/mutt/muttrc + ~/.config/neomutt/muttrc ~/.neomuttrc-20170912 @@ -3023,14 +3023,14 @@ color sidebar_divider color8 default ~/.muttrc - ~/.mutt/neomuttrc-20170912 + ~/.neomutt/neomuttrc-20170912 NeoMutt release version - ~/.mutt/neomuttrc + ~/.neomutt/neomuttrc - ~/.mutt/muttrc + ~/.neomutt/muttrc @@ -3047,7 +3047,7 @@ color sidebar_divider color8 default ;). Multiple configuration commands per line - set realname='Mutt user' ; ignore x- + set realname='John Smith' ; ignore x- The hash mark, or pound sign ( #), is used as a @@ -3111,29 +3111,29 @@ over several lines" Using external command's output in configuration files my_hdr X-Operating-System: `uname -a` - Both environment variables and Mutt variables can be accessed by + Both environment variables and NeoMutt variables can be accessed by prepending $to the name of the variable. For example, Using environment variables in configuration files set record=+sent_on_$HOSTNAME - will cause Mutt to save outgoing messages to a folder named + will cause NeoMutt to save outgoing messages to a folder named sent_on_kremvax if the environment variable $HOSTNAME is set to kremvax.(See $record for details.) - Mutt expands the variable when it is assigned, not when it is used. + NeoMutt expands the variable when it is assigned, not when it is used. If the value of a variable on the right-hand side of an assignment changes after the assignment, the variable on the left-hand side will not be affected. - The commands understood by Mutt are explained in the next + The commands understood by NeoMutt are explained in the next paragraphs. For a complete list, see the command reference. All configuration files are expected to be in the current locale as specified by the $charset variable which doesn't have a - default value since it's determined by Mutt at startup. If a + default value since it's determined by NeoMutt at startup. If a configuration file is not encoded in the same character set the $config_charset variable should be used: all lines starting with the next are recoded from @@ -3146,7 +3146,7 @@ over several lines" These variables should be set early in a configuration file with $charset preceding - $config_charset so Mutt knows + $config_charset so NeoMutt knows what character set to convert to. @@ -3157,7 +3157,7 @@ over several lines" not per configuration file. - Because Mutt first recodes a line before it attempts to parse + Because NeoMutt first recodes a line before it attempts to parse it, a conversion introducing question marks or other characters as part of errors (unconvertable characters, transliteration) may introduce syntax errors or silently change the meaning of certain @@ -3205,21 +3205,21 @@ over several lines" - Mutt supports grouping addresses logically into named groups. An + NeoMutt supports grouping addresses logically into named groups. An address or address pattern can appear in several groups at the same time. These groups can be used in patterns(for searching, limiting and tagging) and in hooks by using group patterns. This can be useful to classify mail and take certain actions depending on in what groups the - message is. For example, the mutt user's mailing list would fit into the + message is. For example, the NeoMutt user's mailing list would fit into the categories mailing list and - mutt-related. Using + NeoMutt-related. Using send-hook , the sender can be set to a dedicated one for writing mailing - list messages, and the signature could be set to a mutt-related one for - writing to a mutt list — for other lists, the list sender setting still + list messages, and the signature could be set to a NeoMutt-related one for + writing to a NeoMutt list — for other lists, the list sender setting still applies but a different signature can be selected. Or, given a group only containing recipients known to accept encrypted mail, auto-encryption can be achieved easily. @@ -3304,7 +3304,7 @@ alternates -group me -group work address3 It's usually very cumbersome to remember or type out the address of - someone you are communicating with. Mutt allows you to create + someone you are communicating with. NeoMutt allows you to create aliases which map a short string to a full address. If you want to create an alias for more than one address, you @@ -3322,7 +3322,7 @@ alternates -group me -group work address3 alias muttdude me@cs.hmc.edu (Michael Elkins) alias theguys manny, moe, jack - Unlike other mailers, Mutt doesn't require aliases to be defined in + Unlike other mailers, NeoMutt doesn't require aliases to be defined in a special file. The alias command can appear anywhere in a configuration file, as long as this file is @@ -3336,7 +3336,7 @@ alias theguys manny, moe, jack function can use only one file, the one pointed to by the $alias_file variable (which is ~/.muttrc by default). This file is not special either, - in the sense that Mutt will happily append aliases to any file, but in + in the sense that NeoMutt will happily append aliases to any file, but in order for the new aliases to take effect you need to explicitly source @@ -3344,20 +3344,20 @@ alias theguys manny, moe, jack Configuring external alias files -source /usr/local/share/Mutt.aliases +source /usr/local/share/NeoMutt.aliases source ~/.mail_aliases set alias_file=~/.mail_aliases - To use aliases, you merely use the alias at any place in Mutt where - Mutt prompts for addresses, such as the + To use aliases, you merely use the alias at any place in NeoMutt where + NeoMutt prompts for addresses, such as the To:or Cc:prompt. You can also enter aliases in your editor at the appropriate headers if you have the $edit_headers variable set. In addition, at the various address prompts, you can use the tab character to expand a partial alias to the full alias. If there are - multiple matches, Mutt will bring up a menu with the matching aliases. In + multiple matches, NeoMutt will bring up a menu with the matching aliases. In order to be presented with the full list of aliases, you must hit tab without a partial alias, such as at the beginning of the prompt or after a comma denoting multiple addresses. @@ -3396,7 +3396,7 @@ set alias_file=~/.mail_aliases This is not a real menu, but is used as a fallback for all of the other menus except for the pager and editor modes. If a key is - not defined in another menu, Mutt will look for a binding to use in + not defined in another menu, NeoMutt will look for a binding to use in this menu. This allows you to bind a key to a certain function in multiple menus instead of having multiple bind statements to accomplish the same @@ -3490,7 +3490,7 @@ set alias_file=~/.mail_aliases mix The mixmaster screen is used to select remailer options for - outgoing messages (if Mutt is compiled with Mixmaster + outgoing messages (if NeoMutt is compiled with Mixmaster support). @@ -3644,13 +3644,13 @@ set alias_file=~/.mail_aliases Warnings about Duplicated Bindings - Due to a limitation of Mutt, creating key bindings, or macros, + Due to a limitation of NeoMutt, creating key bindings, or macros, will overwrite existing mappings with similar, shorter, names. bind index g group-reply bind index gg first-entry In this example, the g binding will be - overwritten and cannot be used. Newer versions of Mutt will warn the + overwritten and cannot be used. Newer versions of NeoMutt will warn the user about this. To avoid warnings on startup, first set the shorter binding to noop (no operation). @@ -3683,7 +3683,7 @@ bind index gg first-entry The charset-hook command defines an alias for a character set. This is useful to properly display messages which are tagged with a - character set name not known to Mutt. + character set name not known to NeoMutt. The iconv-hook command defines a system-specific name for a character set. This is helpful when your systems character conversion @@ -3730,7 +3730,7 @@ bind index gg first-entry not restored when you leave the mailbox. For example, a command action to perform is to change the sorting method based upon the mailbox being read: - folder-hook mutt "set sort=threads" + folder-hook work "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 @@ -3751,12 +3751,12 @@ bind index gg first-entry sort variable to date-sent for all folders but to threads for all folders containing - mutt in their name. + work in their name. Setting sort method based on mailbox name folder-hook . "set sort=date-sent" -folder-hook mutt "set sort=threads" +folder-hook work "set sort=threads" @@ -3782,7 +3782,7 @@ folder-hook mutt "set sort=threads" Macros are useful when you would like a single key to perform a series of actions. When you press key in menu - menu, Mutt will behave as if you had typed + menu, NeoMutt will behave as if you had typed sequence. So if you have a common sequence of commands you type, you can create a macro to execute those commands with a single key or fewer keys. @@ -3901,7 +3901,7 @@ folder-hook mutt "set sort=threads" - If your terminal supports color, you can spice up Mutt by creating + If your terminal supports color, you can spice up NeoMutt by creating your own color scheme. To define the color of an object (type of information), you must specify both a foreground color and a background color (it is not possible to only @@ -3933,7 +3933,7 @@ folder-hook mutt "set sort=threads" messages) - error (error messages printed by Mutt) + error (error messages printed by NeoMutt) hdrdefault (default color of the message header in the @@ -4126,7 +4126,7 @@ folder-hook mutt "set sort=threads" brightred). If your terminal supports it, the special keyword default can be used as a transparent color. The value - brightdefault is also valid. If Mutt is linked + brightdefault is also valid. If NeoMutt is linked against the S-Lang library, you also need to set the $COLORFGBG environment variable to the default colors @@ -4153,7 +4153,7 @@ export COLORFGBG *is a special token which means to clear the color list of all entries. - Mutt also recognizes the keywords + NeoMutt also recognizes the keywords color0, color1, ..., color @@ -4249,11 +4249,11 @@ export COLORFGBG Header Display - When displaying a message in the pager, Mutt folds long header + When displaying a message in the pager, NeoMutt folds long header lines at $wrap columns. Though there're precise rules - about where to break and how, Mutt always folds headers using a tab for - readability. (Note that the sending side is not affected by this, Mutt + about where to break and how, NeoMutt always folds headers using a tab for + readability. (Note that the sending side is not affected by this, NeoMutt tries to implement standards compliant folding.) @@ -4290,7 +4290,7 @@ export COLORFGBG 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 + unignore command will make NeoMutt display headers with the given pattern. For example, if you do ignore x-it is possible to unignore x-mailer. @@ -4332,7 +4332,7 @@ unignore posted-to: With the hdr_order command you can specify an order in which - Mutt will attempt to present these headers to you when viewing + NeoMutt will attempt to present these headers to you when viewing messages. @@ -4375,15 +4375,15 @@ unignore posted-to: - With various functions, Mutt will treat messages differently, + With various functions, NeoMutt will treat messages differently, depending on whether you sent them or whether you received them from someone else. For instance, when replying to a message that you sent to a - different party, Mutt will automatically suggest to send the response to + different party, NeoMutt will automatically suggest to send the response to the original message's recipients — responding to yourself won't make much sense in many cases. (See $reply_to.) Many users receive e-mail under a number of different addresses. To - fully use Mutt's features here, the program must be able to recognize + fully use NeoMutt's features here, the program must be able to recognize what e-mail addresses you receive mail under. That's the purpose of the alternates command: It takes a list of regular expressions, each of which can identify an address under which you @@ -4393,7 +4393,7 @@ unignore posted-to: precise as possible to avoid mismatches. For example, if you specify: alternates user@example - Mutt will consider + NeoMutt will consider some-user@example as being your address, too which may not be desired. As a @@ -4470,10 +4470,10 @@ unignore posted-to: - Mutt has a few nice features for + NeoMutt has a few nice features for handling mailing lists. In order to take advantage of them, you must specify which addresses belong to - mailing lists, and which mailing lists you are subscribed to. Mutt also + mailing lists, and which mailing lists you are subscribed to. NeoMutt also has limited support for auto-detecting mailing lists: it supports parsing mailto:links in the common List-Post:header which has the same effect as @@ -4483,7 +4483,7 @@ unignore posted-to: <list-reply> function will work for all known lists. Additionally, when you - send a message to a subscribed list, Mutt will add a Mail-Followup-To + send a message to a subscribed list, NeoMutt will add a Mail-Followup-To header to tell other users' mail user agents not to send copies of replies to your personal address. @@ -4495,7 +4495,7 @@ unignore posted-to: since it's common practice on some mailing lists to send Cc upon replies (which is more a group- than a list-reply). - More precisely, Mutt maintains lists of patterns for the addresses + More precisely, NeoMutt 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 list command. To mark it as subscribed, use @@ -4507,21 +4507,21 @@ unignore posted-to: as it's often sufficient to just 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 + For example, if you've subscribed to the NeoMutt mailing list, you will receive mail addressed to - mutt-users@mutt.org. So, to tell Mutt that this is a + neomutt-users@neomutt.org. So, to tell NeoMutt 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 + lists neomutt-users@to your initialization file. To tell + NeoMutt that you are subscribed to it, add - subscribe mutt-users to your initialization + subscribe neomutt-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 + neomutt-users@example.com, you could use - lists^mutt-users@mutt\\.org$or + lists ^neomutt-users@neomutt\\.org$or - subscribe^mutt-users@mutt\\.org$to match + subscribe ^neomutt-users@neomutt\\.org$to match only mail from the actual list. The -group flag adds all of the subsequent regular @@ -4594,17 +4594,17 @@ unignore posted-to: will be checked for new messages periodically. folder can either be a local file or directory - (Mbox/Mmdf or Maildir/Mh). If Mutt was built with POP and/or IMAP + (Mbox/Mmdf or Maildir/Mh). If NeoMutt was built with POP and/or IMAP support, folder can also be a POP/IMAP folder URL. The URL syntax is described in , POP and IMAP are described in and respectively. - Mutt provides a number of advanced features for handling (possibly + NeoMutt provides a number of advanced features for handling (possibly many) folders and new mail within them, please refer to for details (including in what situations and - how often Mutt checks for new mail). + how often NeoMutt checks for new mail). The unmailboxes command is used to remove a token from the list of folders which receive mail. Use @@ -4620,8 +4620,8 @@ unignore posted-to: $folder and $spoolfile) should be set before the mailboxes command. If none of these shortcuts are - used, a local path should be absolute as otherwise Mutt tries to find - it relative to the directory from where Mutt was started which may not + used, a local path should be absolute as otherwise NeoMutt tries to find + it relative to the directory from where NeoMutt was started which may not always be desired. @@ -4662,7 +4662,7 @@ unignore posted-to: Space characters are not allowed between the keyword and the colon ( :). The standard for electronic mail (RFC2822) says that - space is illegal there, so Mutt enforces the rule. + space is illegal there, so NeoMutt enforces the rule. If you would like to add a header field to a single message, you should either set the @@ -4698,7 +4698,7 @@ unignore posted-to: pattern, see for information on the exact format. - To provide more flexibility and good defaults, Mutt applies the + To provide more flexibility and good defaults, NeoMutt applies the expandos of $index_format to mailbox after it was expanded. @@ -4733,13 +4733,13 @@ save-hook aol\\.com$ +spam This command is used to save outgoing mail in a mailbox other than - $record. Mutt searches the initial list of + $record. NeoMutt searches the initial list of message recipients for the first matching pattern and uses mailbox as the default Fcc: mailbox. If no match is found the message will be saved to $record mailbox. - To provide more flexibility and good defaults, Mutt applies the + To provide more flexibility and good defaults, NeoMutt applies the expandos of $index_format to mailbox after it was expanded. @@ -4849,7 +4849,7 @@ save-hook aol\\.com$ +spam .muttrc(for that type of hook). Example: - send-hook mutt " + send-hook work " set mime_forward signature=''" Another typical use for this command is to change the values of the $attribution, @@ -4919,16 +4919,16 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a certain key with a given e-mail address automatically, either because the recipient's public key can't be deduced from the destination - address, or because, for some reasons, you need to override the key Mutt + address, or because, for some reasons, you need to override the key NeoMutt would normally use. The crypt-hook command provides a method by which you can specify the ID of the public key to be used when encrypting messages to a certain recipient. You may use multiple crypt-hooks with the same regexp; multiple matching crypt-hooks result in the use of multiple keyids for a - recipient. During key selection, Mutt will confirm whether each + recipient. During key selection, NeoMutt will confirm whether each crypt-hook is to be used (unless the $crypt_confirmhook option is - unset). If all crypt-hooks for a recipient are declined, Mutt will use + unset). If all crypt-hooks for a recipient are declined, NeoMutt will use the original recipient address for key selection instead. The meaning of keyid is to be taken broadly in this context: You can @@ -4962,7 +4962,7 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' For using functions like shown in the example, it's important to use angle brackets ( <and - >) to make Mutt recognize the input as a function name. + >) to make NeoMutt recognize the input as a function name. Otherwise it will simulate individual just keystrokes, i.e. push collapse-all @@ -5084,7 +5084,7 @@ folder-hook . 'push "<enter-command>score ~= 10<enter>"' - Mutt has generalized support for external spam-scoring filters. By + NeoMutt has generalized support for external spam-scoring filters. By defining your spam patterns with the spam and nospam commands, you can @@ -5116,7 +5116,7 @@ folder-hook . 'push "<enter-command>score ~= 10<enter>"' %1 is replaced with the first back-reference in the regex, %2 with the second, etc. - To match spam tags, mutt needs the corresponding header information + To match spam tags, NeoMutt needs the corresponding header information which is always the case for local and POP folders but not for IMAP in the default configuration. Depending on the spam header to be analyzed, $imap_headers may need to be @@ -5166,11 +5166,11 @@ set spam_separator=", " attribute will use as a sort key. That's a pretty complicated example, and most people's actual environments will have only one spam filter. The simpler your - configuration, the more effective Mutt can be, especially when it comes + configuration, the more effective NeoMutt can be, especially when it comes to sorting. - Generally, when you sort by spam tag, Mutt will sort + Generally, when you sort by spam tag, NeoMutt will sort lexically— that is, by ordering strings - alphanumerically. However, if a spam tag begins with a number, Mutt will + alphanumerically. However, if a spam tag begins with a number, NeoMutt will sort numerically first, and lexically only when two numbers are equal in value. (This is like UNIX's sort -n.) A message with no spam attributes at all — @@ -5182,7 +5182,7 @@ set spam_separator=", " 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. + in case you can't, NeoMutt can still do something useful. The nospam command can be used to write exceptions to spam patterns. If a header pattern matches something in @@ -5211,7 +5211,7 @@ set spam_separator=", " spam or nospam commands as you like. You can even do your own primitive - spam detection within Mutt — for example, if you + spam detection within NeoMutt — for example, if you consider all mail from MAILER-DAEMON to be spam, you can use a spam command like this: @@ -5223,7 +5223,7 @@ set spam_separator=", " Variable Types - Mutt supports these types of configuration variables: + NeoMutt supports these types of configuration variables: boolean @@ -5426,7 +5426,7 @@ set spam_separator=", " Introduction Along with the variables listed in the - Configuration variables section, Mutt + Configuration variables section, NeoMutt supports user-defined variables with names starting with my_ as in, for example, my_cfgdir. @@ -5454,7 +5454,7 @@ set spam_separator=", " Using user-defined variables for config file readability -set my_cfgdir = $HOME/mutt/config +set my_cfgdir = $HOME/neomutt/config source $my_cfgdir/hooks $my_cfgdir/macros # more source commands... @@ -5478,7 +5478,7 @@ macro pager ,x '\ <enter-command>set delete=$my_delete<enter>' - Since Mutt expands such values already when parsing the + Since NeoMutt expands such values already when parsing the configuration file(s), the value of $my_delete in the last example would be the value of @@ -5502,7 +5502,7 @@ macro pager <PageDown> "\ Note that there is a space between <enter-command>and the - set configuration command, preventing Mutt from + set configuration command, preventing NeoMutt from recording the macro's commands into its history. @@ -5510,14 +5510,14 @@ macro pager <PageDown> "\ Type Conversions - Variables are always assigned string values which Mutt parses + Variables are always assigned string values which NeoMutt parses into its internal representation according to the type of the variable, for example an integer number for numeric types. For all queries (including $-expansion) the value is converted from its internal type back into string. As a result, any variable can be assigned any value given that its content is valid for the target. This also counts for custom variables which are of type string. In case of parsing errors, - Mutt will print error messages. + NeoMutt will print error messages. demonstrates type conversions. Type conversions using variables @@ -5609,7 +5609,7 @@ mailboxes $my_mx +mailbox3 Basic usage Format strings are a general concept you'll find in several - locations through the Mutt configuration, especially in the + locations through the NeoMutt configuration, especially in the $index_format, $pager_format, $status_format, and other related @@ -5642,7 +5642,7 @@ mailboxes $my_mx +mailbox3 %4c, %.15F and %-12.15L. - Mutt adds some other modifiers to format strings. If you use an + NeoMutt adds some other modifiers to format strings. If you use an equals symbol ( =) as a numeric prefix (like the minus above), it will force the string to be centered within its minimum space range. @@ -5715,7 +5715,7 @@ mailboxes $my_mx +mailbox3 Using external filters in format strings set status_format="script.sh '%r %f (%L)'|" - will make Mutt expand + will make NeoMutt expand %r, %f and %L before calling the script. The example also shows @@ -5723,7 +5723,7 @@ mailboxes $my_mx +mailbox3 string between the single quotes as the only argument. A practical example is the mutt_xtitle script installed in the - samples subdirectory of the Mutt documentation: it + samples subdirectory of the NeoMutt documentation: it can be used as filter for $status_format to set the current terminal's title, if supported. @@ -5731,7 +5731,7 @@ mailboxes $my_mx +mailbox3 Padding - In most format strings, Mutt supports different types of padding + In most format strings, NeoMutt supports different types of padding using special %-expandos: @@ -5739,7 +5739,7 @@ mailboxes $my_mx +mailbox3 %|X - When this occurs, Mutt will fill the rest of the line with + When this occurs, NeoMutt will fill the rest of the line with the character X. For example, filling the rest of the line with dashes is done by setting: @@ -5827,15 +5827,15 @@ mailboxes $my_mx +mailbox3 - As a security measure, Mutt will only add user-approved header + As a security measure, NeoMutt will only add user-approved header fields from a - mailto:URL. This is necessary since Mutt will handle + mailto:URL. This is necessary since NeoMutt will handle certain header fields, such as Attach:, in a special way. The mailto_allow and unmailto_allow commands allow the user to modify the list of approved headers. - Mutt initializes the default list to contain only the + NeoMutt initializes the default list to contain only the Subject and Body header fields, which are the only requirement specified by the @@ -5858,7 +5858,7 @@ mailboxes $my_mx +mailbox3 is used. For the Unicode character set, different character encodings may be used, UTF-8 being the most popular. In UTF-8, a character is represented using a variable number of bytes ranging from 1 to 4. - Since Mutt is a command-line tool run from a shell, and delegates + Since NeoMutt is a command-line tool run from a shell, and delegates certain tasks to external tools (such as an editor for composing/editing messages), all of these tools need to agree on a character set and encoding. There exists no way to reliably deduce the character set a @@ -5866,13 +5866,13 @@ mailboxes $my_mx +mailbox3 well-defined environment variables. The full set can be printed by issuing locale on the command line. - Upon startup, Mutt determines the character set on its own using + Upon startup, NeoMutt determines the character set on its own using routines that inspect locale-specific environment variables. Therefore, it is generally not necessary to set the - $charset variable in Mutt. It may even be - counter-productive as Mutt uses system and library functions that derive - the character set themselves and on which Mutt has no influence. It's - safest to let Mutt work out the locale setup itself. + $charset variable in NeoMutt. It may even be + counter-productive as NeoMutt uses system and library functions that derive + the character set themselves and on which NeoMutt has no influence. It's + safest to let NeoMutt work out the locale setup itself. If you happen to work with several character sets on a regular basis, it's highly advisable to use Unicode and an UTF-8 locale. Unicode can represent nearly all characters in a message at the same time. When @@ -5884,27 +5884,27 @@ mailboxes $my_mx +mailbox3 be guessed). A Unicode locale makes all conversions superfluous which eliminates the risk of conversion errors. It also eliminates potentially wrong - expectations about the character set between Mutt and external + expectations about the character set between NeoMutt and external programs. The terminal emulator used also must be properly configured for the current locale. Terminal emulators usually do not derive the locale from environment variables, they need to be configured separately. If the terminal is incorrectly - configured, Mutt may display random and unexpected characters (question + configured, NeoMutt may display random and unexpected characters (question marks, octal codes, or just random glyphs), format strings may not work as expected, you may not be abled to enter non-ascii characters, and possible more. Data is always represented using bytes and so a correct setup is very important as to the machine, all character sets look the same. Warning: A mismatch between what system and library functions think - the locale is and what Mutt was told what the locale is may make it + the locale is and what NeoMutt was told what the locale is may make it behave badly with non-ascii input: it will fail at seemingly random places. This warning is to be taken seriously since not only local mail handling may suffer: sent messages may carry wrong character set information the receiver has too deal with. The need to set $charset directly in most cases points at terminal and - environment variable setup problems, not Mutt problems. + environment variable setup problems, not NeoMutt problems. A list of officially assigned and known character sets can be found at IANA, @@ -5914,7 +5914,7 @@ mailboxes $my_mx +mailbox3 Regular Expressions - All string patterns in Mutt including those in more complex + All string patterns in NeoMutt including those in more complex patterns must be specified using regular expressions (regexp) in the POSIX extended syntax (which is more or less the syntax @@ -6154,7 +6154,7 @@ mailboxes $my_mx +mailbox3 precedence over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules. - If you compile Mutt with the included regular expression engine, + If you compile NeoMutt with the included regular expression engine, the following operators may also be used in regular expressions as described in . @@ -6219,7 +6219,7 @@ mailboxes $my_mx +mailbox3 Pattern Modifier - Many of Mutt's commands allow you to specify a pattern to match ( + Many of NeoMutt's commands allow you to specify a pattern to match ( limit, tag-pattern, delete-pattern, etc.). @@ -6611,12 +6611,12 @@ mailboxes $my_mx +mailbox3 other types of ranges. Read on and see below. Special attention has to be paid when using regular expressions - inside of patterns. Specifically, Mutt's parser for these patterns will + inside of patterns. Specifically, NeoMutt'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 + \\). You can force NeoMutt to treat EXPR as a simple substring instead of a regular expression by using = instead of ~ in the pattern name. For example, =b *.*will find all messages that contain the @@ -6813,7 +6813,7 @@ mailboxes $my_mx +mailbox3 Simple Searches - Mutt supports two versions of so called + NeoMutt supports two versions of so called simple searches. These are issued if the query entered for searching, limiting and similar operations does not seem to contain a valid pattern modifier (i.e. it does not contain one of these @@ -6825,7 +6825,7 @@ mailboxes $my_mx +mailbox3 \). The first type is by checking whether the query string equals a keyword case-insensitively from - : If that is the case, Mutt + : If that is the case, NeoMutt 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 @@ -6896,7 +6896,7 @@ mailboxes $my_mx +mailbox3
The second type of simple search is to build a complex search pattern using - $simple_search as a template. Mutt + $simple_search as a template. NeoMutt will insert your query properly quoted and search for the composed complex query. @@ -6905,13 +6905,13 @@ mailboxes $my_mx +mailbox3 Nesting and Boolean Operators Logical AND is performed by specifying more than one criterion. For example: - ~t mutt ~f elkins + ~t work ~f elkins would select messages which contain the word - mutt in the list of recipients + work in the list of recipients and that have the word elkins in the From header field. - Mutt also recognizes the following operators to create more + NeoMutt also recognizes the following operators to create more complex search patterns: @@ -6926,13 +6926,13 @@ mailboxes $my_mx +mailbox3 Here is an example illustrating a complex search pattern. This pattern will select all messages which do not contain - mutt in the + work in the To or Cc field and which are from elkins. Using boolean operators in patterns - !(~t mutt|~c mutt) ~f elkins + !(~t work|~c work) ~f elkins Here is an example using white space in the regular expression (note the @@ -6948,19 +6948,19 @@ mailboxes $my_mx +mailbox3 ("|"), you must enclose the expression in double or single quotes since those characters are also used to separate different - parts of Mutt's pattern language. For example: - ~f "me@(mutt\.org|cs\.hmc\.edu)"Without the + parts of NeoMutt's pattern language. For example: + ~f "user@(home\.org|work\.com)"Without the quotes, the parenthesis wouldn't end. This would be separated to two OR'd patterns: - ~f me@(mutt\.org and - cs\.hmc\.edu). They are never what you + ~f user@(home\.org and + work\.com). They are never what you want. Searching by Date - Mutt supports two types of dates, + NeoMutt supports two types of dates, absolute and relative. @@ -7074,7 +7074,7 @@ mailboxes $my_mx +mailbox3 GMail's Support Page. You will need to (once) use a web-browser to visit Settings/Labels and enable "Show in IMAP" for "All Mail". When searching, visit that - folder in mutt to most closely match Gmail search semantics. + folder in NeoMutt to most closely match Gmail search semantics. GMail Example Patterns @@ -7109,7 +7109,7 @@ mailboxes $my_mx +mailbox3 Marking Messages - There are times that it's useful to ask Mutt to "remember" which + There are times that it's useful to ask NeoMutt to "remember" which message you're currently looking at, while you move elsewhere in your mailbox. You can do this with the mark-message operator, which is bound to the @@ -7135,7 +7135,7 @@ mailboxes $my_mx +mailbox3 by hand using the <tag-message>function, which is bound to t by default. See - patterns for Mutt's pattern matching + patterns for NeoMutt's pattern matching syntax. Once you have tagged the desired messages, you can use the tag-prefix operator, which is the @@ -7154,8 +7154,8 @@ mailboxes $my_mx +mailbox3 push commands, 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 + tagged messages, NeoMutt will + eat the rest of the macro to abort it's execution. NeoMutt will stop eating the macro when it encounters the <end-cond>operator; after this operator the rest @@ -7169,7 +7169,7 @@ mailboxes $my_mx +mailbox3 allows you to execute arbitrary commands before performing some operation. For example, you may wish to tailor your configuration based upon which mailbox you are reading, or to whom you are sending mail. In - the Mutt world, a + the NeoMutt world, a hook consists of a regular expression or pattern along with a configuration @@ -7291,7 +7291,7 @@ mailboxes $my_mx +mailbox3 hook available. If a hook changes configuration settings, these changes remain - effective until the end of the current Mutt session. As this is + effective until the end of the current NeoMutt session. As this is generally not desired, a default hook needs to be added before all other hooks of that type to restore configuration defaults. @@ -7326,24 +7326,24 @@ send-hook ~C'^b@b\.b$' my_hdr from: c@c.c dealing with messages a finer grain of control is needed for matching since for different purposes you want to match different criteria. - Mutt allows the use of the + NeoMutt allows the use of the search pattern language for matching messages in hook commands. This works in exactly the same way as it would when limiting or searching the mailbox, except that you are - restricted to those operators which match information Mutt extracts + restricted to those operators which match information NeoMutt extracts from the header of the message (i.e., from, to, cc, date, subject, etc.). For example, if you wanted to set your return address based upon sending mail to a specific address, you could do something like: - send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>' + send-hook '~t ^user@work\.com$' 'my_hdr From: John Smith <user@host>' which would execute the given command when sending mail to - me@cs.hmc.edu. + user@work.com. However, it is not required that you write the pattern to match using the full searching language. You can still specify a simple regular expression like the other hooks, in which - case Mutt will translate your pattern into the full language, using the + case NeoMutt will translate your pattern into the full language, using the translation specified by the $default_hook variable. The pattern is translated at the time the hook is declared, so the value of @@ -7375,26 +7375,26 @@ folder-hook '\@imap.example.com' "set sort=threads" Keep in mind that mailbox shortcut expansion on the regexp parameter takes place when the hook is initially parsed, not when the - hook is matching against a mailbox. When Mutt starts up and is reading + hook is matching against a mailbox. When NeoMutt starts up and is reading the .muttrc, some mailbox shortcuts may not be usable. For example, the "current mailbox" shortcut, ^, will expand to an empty string because - no mailbox has been opened yet. Mutt will issue an error for this case + no mailbox has been opened yet. NeoMutt will issue an error for this case or if the mailbox shortcut results in an empty regexp. Managing the Environment - You can alter the environment that Mutt passes on to its child + You can alter the environment that NeoMutt passes on to its child processes using the setenv and - unsetenv operators. (N.B. These follow Mutt-style syntax, + unsetenv operators. (N.B. These follow NeoMutt-style syntax, not shell-style!) You can also query current environment values by prefixing a ?character. setenv TERM vt100 -setenv ORGANIZATION "The Mutt Development Team" +setenv ORGANIZATION "The NeoMutt Development Team" unsetenv DISPLAY setenv ?LESS @@ -7402,8 +7402,8 @@ setenv ?LESS External Address Queries - Mutt supports connecting to external directory databases such as - LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to Mutt + NeoMutt supports connecting to external directory databases such as + LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to NeoMutt using a simple interface. Using the $query_command variable, you specify the wrapper command to use. For example: @@ -7421,7 +7421,7 @@ me@cs.hmc.edu Michael Elkins mutt dude blong@fiction.net Brandon Long mutt and more roessler@does-not-exist.org Thomas Roessler mutt pgp - There are two mechanisms for accessing the query function of Mutt. + There are two mechanisms for accessing the query function of NeoMutt. One is to do a query from the index menu using the <query>function (default: Q). This will prompt for a query, then bring up the query menu which will list the matching @@ -7432,20 +7432,20 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp completion, similar to the alias completion. In any prompt for address entry, you can use the <complete-query>function (default: ^T) to run a - query based on the current address you have typed. Like aliases, Mutt + query based on the current address you have typed. Like aliases, NeoMutt will look for what you have typed back to the last space or comma. If - there is a single response for that query, Mutt will expand the address - in place. If there are multiple responses, Mutt will activate the query + there is a single response for that query, NeoMutt will expand the address + in place. If there are multiple responses, NeoMutt will activate the query menu. At the query menu, you can select one or more addresses to be added to the prompt. Mailbox Formats - Mutt supports reading and writing of four different local mailbox + NeoMutt supports reading and writing of four different local mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is auto detected, so there is no need to use a flag for different mailbox types. When - creating new mailboxes, Mutt uses the default specified with the + creating new mailboxes, NeoMutt uses the default specified with the $mbox_type variable. A short description of the formats follows. @@ -7472,9 +7472,9 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp mbox and MMDF, a mailbox consists of a directory and each message is stored in a separate file. The filename indicates the message - number (however, this is may not correspond to the message number Mutt + number (however, this is may not correspond to the message number NeoMutt displays). Deleted messages are renamed with a comma ( - ,) prepended to the filename. Mutt detects this type of + ,) prepended to the filename. NeoMutt detects this type of mailbox by looking for either .mh_sequences or .xmhcache files (needed to distinguish normal @@ -7482,7 +7482,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp writing the mailbox, but still may suffer from lost flags; message corruption is less likely to occur than with mbox/mmdf. It's usually slower to open compared to mbox/mmdf since many small files have to be - read (Mutt provides + read (NeoMutt provides to greatly speed this process up). Depending on the environment, MH is not very disk-space efficient. @@ -7495,7 +7495,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp cur. Filenames for the messages are chosen in such a way they are unique, even when two programs are writing the mailbox over NFS, which means that no file locking is needed and corruption is very - unlikely. Maildir maybe slower to open without caching in Mutt, it too is + unlikely. Maildir maybe slower to open without caching in NeoMutt, it too is not very disk-space efficient depending on the environment. Since no additional files are used for metadata (which is embedded in the message filenames) and Maildir is locking-free, it's easy to sync across @@ -7588,8 +7588,8 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp Handling Mailing Lists - Mutt has a few configuration options that make dealing with large - amounts of mail easier. The first thing you must do is to let Mutt know + NeoMutt has a few configuration options that make dealing with large + amounts of mail easier. The first thing you must do is to let NeoMutt know what addresses you consider to be mailing lists (technically this does not have to be a mailing list, but that is what it is most often used for), and what lists you are subscribed to. This is accomplished through @@ -7598,7 +7598,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp lists and subscribecommands in your .muttrc. - Now that Mutt knows what your mailing lists are, it can do several + Now that NeoMutt 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 @@ -7625,11 +7625,11 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp the known mailing list addresses instead of all recipients (except as specified by Mail-Followup-To, see below). - Mutt also supports the + NeoMutt also supports the Mail-Followup-To header. When you send 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 + $followup_to option is set, NeoMutt 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 @@ -7639,7 +7639,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp to. Conversely, when group-replying or list-replying to a message which has a - Mail-Followup-To header, Mutt will respect this header + Mail-Followup-To header, NeoMutt will respect this header if the $honor_followup_to configuration variable is set. Using @@ -7649,7 +7649,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp Mail-Followup-To. When header editing is enabled, you can create a - Mail-Followup-To header manually. Mutt will only + Mail-Followup-To header manually. NeoMutt will only auto-generate this header if it doesn't exist when you send the message. @@ -7658,7 +7658,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp 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 field. Mutt uses the + Reply-To field. NeoMutt uses the $reply_to variable to help decide which address to use. If set to ask-yes or @@ -7670,13 +7670,13 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp yes, the Reply-To field will be used when present. You can change or delete the - X-Label:field within Mutt using the + X-Label:field within NeoMutt using the edit-label command, bound to the y key by default. This works for tagged messages, too. While in the edit-label function, pressing the <complete> binding (TAB, by default) will perform completion against all labels currently in use. - Lastly, Mutt has the ability to + Lastly, NeoMutt has the ability to sort the mailbox into threads. A thread is a group of messages which all relate to the same subject. This is usually organized into a @@ -7689,13 +7689,13 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp Keyword Management - Mutt has supported textual labels (usually known as X-Labels after + NeoMutt has supported textual labels (usually known as X-Labels after the header that we use to store them) for many years. Since we initially added support for X-Labels, however, the larger community has evolved more common ways of using and managing such labels, often known as keywords or tags. - If you are new to Mutt or to using keywords in Mutt, you only need + If you are new to NeoMutt or to using keywords in NeoMutt, you only need to know that the <edit-label> binding will edit keywords, and that you can search for keywords using the ~y pattern, and use the @@ -7704,7 +7704,7 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp that you set will be stored to the X-Label:header by default. If you've been using X-Labels for a while, things have grown - slightly. Mutt still supports X-Labels much as it has since 2000, but the + slightly. NeoMutt still supports X-Labels much as it has since 2000, but the scope of this support has expanded to support three additional header-based techniques for storing keyword metadata on messages: @@ -7731,12 +7731,12 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp X-Label - Mutt-specific design; freeform text (but see + NeoMutt-specific design; freeform text (but see $xlabel_delimiter) - With X-Label, mutt's only notion of a message keyword was the + With X-Label, NeoMutt's only notion of a message keyword was the literal string value of the X-Label header. Under the new, integrated support, each message may have a list of distinct message keywords. When reading keywords from one of the headers in the list above, the header @@ -7746,10 +7746,10 @@ roessler@does-not-exist.org Thomas Roessler mutt pgp splitting of X-Label: as well. Two boolean variables control how keywords are saved when writing messages to a mailbox. The default settings preserve backward - compatibility within mutt completely, but by changing these values you + compatibility within NeoMutt completely, but by changing these values you can transition to more standard keyword storage. $keywords_legacy, if set, will - tell mutt to use only "legacy" headers -- i.e., + tell NeoMutt to use only "legacy" headers -- i.e., X-Keywords:, X-Mozilla-Keys, Keywords, or @@ -7839,26 +7839,26 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' New Mail Detection - Mutt supports setups with multiple folders, allowing all of them to + NeoMutt supports setups with multiple folders, allowing all of them to be monitored for new mail (see for details). How New Mail Detection Works For Mbox and Mmdf folders, new mail is detected by comparing - access and/or modification times of files: Mutt assumes a folder has + access and/or modification times of files: NeoMutt assumes a folder has new mail if it wasn't accessed after it was last modified. Utilities like biff or frm or any other program which accesses the mailbox - might cause Mutt to never detect new mail for that mailbox if they do - not properly reset the access time. Other possible causes of Mutt not + might cause NeoMutt to never detect new mail for that mailbox if they do + not properly reset the access time. Other possible causes of NeoMutt not detecting new mail in these folders are backup tools (updating access times) or filesystems mounted without access time update support (for Linux systems, see the relatime option). - Contrary to older Mutt releases, it now maintains the new mail + Contrary to older NeoMutt releases, it now maintains the new mail status of a folder by properly resetting the access time if the folder contains at least one message which is neither read, nor deleted, nor marked as old. @@ -7866,7 +7866,7 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' In cases where new mail detection for Mbox or Mmdf folders appears to be unreliable, the $check_mbox_size option can be - used to make Mutt track and consult file sizes for new mail detection + used to make NeoMutt track and consult file sizes for new mail detection instead which won't work for size-neutral changes. New mail for Maildir is assumed if there is one message in the new/subdirectory which is not marked deleted (see @@ -7878,25 +7878,25 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' $new_mail_command can be configured to execute an external program every time new mail is detected in the current inbox. - Mutt does not poll POP3 folders for new mail, it only + NeoMutt does not poll POP3 folders for new mail, it only periodically checks the currently opened folder (if it's a POP3 folder). - For IMAP, by default Mutt uses recent message counts provided by + For IMAP, by default NeoMutt uses recent message counts provided by the server to detect new mail. If the $imap_idle option is set, it'll use the IMAP IDLE extension if advertised by the server. The $mail_check_recent option - changes whether Mutt will notify you of new mail in an already visited + changes whether NeoMutt will notify you of new mail in an already visited mailbox. When set (the default) it will only notify you of new mail - received since the last time you opened the mailbox. When unset, Mutt + received since the last time you opened the mailbox. When unset, NeoMutt will notify you of any new mail in the mailbox. Polling For New Mail When in the index menu and being idle (also see - $timeout), Mutt periodically checks for + $timeout), NeoMutt periodically checks for new mail in all folders which have been configured via the mailboxes command. The interval depends on the folder type: for local/IMAP folders it consults @@ -7909,19 +7909,19 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' default. Pressing TAB will bring up a menu showing the files specified by the mailboxes command, and indicate which contain new - messages. Mutt will automatically enter this mode when invoked from the + messages. NeoMutt will automatically enter this mode when invoked from the command line with the -y option. - For the pager, index and directory browser menus, Mutt contains + For the pager, index and directory browser menus, NeoMutt contains the <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. - For the index, by default Mutt displays the number of mailboxes + For the index, by default NeoMutt displays the number of mailboxes with new mail in the status bar, please refer to the $status_format variable for details. - When changing folders, Mutt fills the prompt with the first + When changing folders, NeoMutt fills the prompt with the first folder from the mailboxes list containing new mail (if any), pressing <Space>will cycle through folders with new mail. The (by default unbound) function @@ -7932,7 +7932,7 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' Calculating Mailbox Message Counts If - $mail_check_stats is set, Mutt + $mail_check_stats is set, NeoMutt will periodically calculate the unread, flagged, and total message counts for each mailbox watched by the mailboxes command. This calculation takes place at @@ -7947,7 +7947,7 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' Editing Threads - Mutt has the ability to dynamically restructure threads that are + NeoMutt has the ability to dynamically restructure threads that are broken either by misconfigured software or bad behavior from some correspondents. This allows to clean your mailboxes from these annoyances which make it hard to follow a discussion. @@ -7958,7 +7958,7 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' forget to correctly set the In-Reply-To:and References:headers when replying to a message. This - results in broken discussions because Mutt has not enough information + results in broken discussions because NeoMutt has not enough information to guess the correct threading. You can fix this by tagging the reply, then moving to the parent message and using the <link-threads>function (bound to & by @@ -8005,7 +8005,7 @@ subjectrx '\[[^\]]*\]:? *' '%L%R' whether DSN is supported. For SMTP delivery using $smtp_url, it depends on the capabilities - announced by the server whether Mutt will attempt to request DSN or + announced by the server whether NeoMutt will attempt to request DSN or not. @@ -8031,24 +8031,24 @@ macro pager \cb |urlview\n Address normalization - Mutt normalizes all e-mail addresses to the simplest form + NeoMutt normalizes all e-mail addresses to the simplest form possible. If an address contains a realname, the form Joe User <joe@example.com>is used and the pure e-mail address without angle brackets otherwise, i.e. just joe@example.com. - This normalization affects all headers Mutt generates + This normalization affects all headers NeoMutt generates including aliases. Initial folder selection - The folder Mutt opens at startup is determined as follows: + The folder NeoMutt opens at startup is determined as follows: the folder specified in the $MAIL environment variable if present. Otherwise, the value of $MAILDIR is taken into account. If that isn't - present either, Mutt takes the user's mailbox in the mailspool as + present either, NeoMutt takes the user's mailbox in the mailspool as determined at compile-time (which may also reside in the home directory). The $spoolfile setting overrides this @@ -8061,19 +8061,19 @@ macro pager \cb |urlview\n - Mutt's MIME Support - Quite a bit of effort has been made to make Mutt the premier + NeoMutt's MIME Support + Quite a bit of effort has been made to make NeoMutt the premier text-mode MIME MUA. Every effort has been made to provide the functionality that the discerning MIME user requires, and the conformance to the - standards wherever possible. When configuring Mutt for MIME, there are two - extra types of configuration files which Mutt uses. One is the + standards wherever possible. When configuring NeoMutt for MIME, there are two + extra types of configuration files which NeoMutt uses. One is the mime.types file, which contains the mapping of file extensions to IANA MIME types. The other is the mailcap file, which specifies the external commands to use for handling specific MIME types. - Using MIME in Mutt + Using MIME in NeoMutt MIME Overview @@ -8086,11 +8086,11 @@ macro pager \cb |urlview\n thus form a tree structure), nearly arbitrary characters can be used for sender names, recipients and subjects. Besides the handling of non-ascii characters in message headers, - to Mutt the most important aspect of MIME are so-called MIME types. + to NeoMutt the most important aspect of MIME are so-called MIME types. These are constructed using a major and minor type separated by a forward slash. These - specify details about the content that follows. Based upon these, Mutt + specify details about the content that follows. Based upon these, NeoMutt decides how to handle this part. The most popular major type is text @@ -8109,9 +8109,9 @@ macro pager \cb |urlview\n quoted-printable, base64 and binary. There're some rules when to choose what for - encoding headers and/or body (if needed), and Mutt will in general make + encoding headers and/or body (if needed), and NeoMutt will in general make a good choice. - Mutt does most of MIME encoding/decoding behind the scenes to + NeoMutt does most of MIME encoding/decoding behind the scenes to form messages conforming to MIME on the sending side. On reception, it can be flexibly configured as to how what MIME structure is displayed (and if it's displayed): these decisions are based on the content's @@ -8123,15 +8123,15 @@ macro pager \cb |urlview\n Viewing MIME Messages in the Pager When you select a message from the index and view it in the - pager, Mutt decodes as much of a message as possible to a text - representation. Mutt internally supports a number of MIME types, + pager, NeoMutt decodes as much of a message as possible to a text + representation. NeoMutt internally supports a number of MIME types, including the text major type (with all minor types), the message/rfc822(mail messages) type and some multipart types. In addition, it recognizes a variety of PGP MIME types, including PGP/MIME and application/pgp. - Mutt will denote attachments with a couple lines describing them. + NeoMutt will denote attachments with a couple lines describing them. These lines are of the form: [-- Attachment #1: Description --] @@ -8142,7 +8142,7 @@ macro pager \cb |urlview\n for the attachment, and the Encoding is one of the already mentioned content encodings. - If Mutt cannot deal with a MIME type, it will display a message + If NeoMutt cannot deal with a MIME type, it will display a message like: [-- image/gif is unsupported (use 'v' to view this part) --] @@ -8184,11 +8184,11 @@ macro pager \cb |urlview\n information, notably the type, encoding and description. Attachments appear as follows by default: -- 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 <no description> - 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz <no description> +- 1 [text/plain, 7bit, 1K] /tmp/neomutt-euler-8082-0 <no description> + 2 [applica/x-gunzip, base64, 422K] ~/src/neomutt-0.85.tar.gz <no description> The - -denotes that Mutt will delete the file after sending + -denotes that NeoMutt will delete the file after sending (or postponing, or canceling) the message. It can be toggled with the <toggle-unlink>command (default: u). The next field is the MIME content-type, and can be changed with the @@ -8213,17 +8213,17 @@ macro pager \cb |urlview\n To get most out of MIME, it's important that a MIME part's content type matches the content as closely as possible so that the recipient's client can automatically select the right viewer for the content. - However, there's no reliable for Mutt to know how to detect every + However, there's no reliable for NeoMutt to know how to detect every possible file type. Instead, it uses a simple plain text mapping file that specifies what file extension corresponds to what MIME type. This file is called mime.types. - When you add an attachment to your mail message, Mutt searches your + When you add an attachment to your mail message, NeoMutt searches your personal mime.types file at $HOME/.mime.types, and then the system mime.types file at - /usr/local/share/mutt/mime.types or + /usr/local/share/neomutt/mime.types or /etc/mime.types Each line starts with the full MIME type, followed by a space and space-separated list of file extensions. For example you could @@ -8239,21 +8239,21 @@ audio/x-aiff aif aifc aiff A sample - mime.types file comes with the Mutt distribution, and + mime.types file comes with the NeoMutt distribution, and should contain most of the MIME types you are likely to use. - If Mutt can not determine the MIME type by the extension of the + If NeoMutt can not determine the MIME type by the extension of the file you attach, it will run the command specified in $mime_type_query_command. - If that command is not specified, Mutt will look at the file. If the file - is free of binary information, Mutt will assume that the file is plain + If that command is not specified, NeoMutt will look at the file. If the file + is free of binary information, NeoMutt will assume that the file is plain text, and mark it as text/plain. If the file contains binary information, - then Mutt will mark it as + then NeoMutt will mark it as application/octet-stream. You can change the MIME type - that Mutt assigns to an attachment by using the + that NeoMutt assigns to an attachment by using the <edit-type>command from the compose menu (default: ^T), see - for supported major types. Mutt + for supported major types. NeoMutt recognizes all of these if the appropriate entry is found in the mime.types file. Non-recognized mime types should only be used if the recipient of the message is likely to be expecting such @@ -8343,14 +8343,14 @@ audio/x-aiff aif aifc aiff MIME Viewer Configuration with Mailcap - Mutt supports RFC 1524 MIME Configuration, in particular the Unix + NeoMutt supports RFC 1524 MIME Configuration, in particular the Unix specific format specified in Appendix A of RFC 1524. This file format is commonly referred to as the mailcap format. Many MIME compliant programs utilize the mailcap format, allowing you to specify handling for all MIME types in one place for all programs. Programs known to use this format include Firefox, lynx and metamail. - In order to handle various MIME types that Mutt doesn't have + In order to handle various MIME types that NeoMutt doesn't have built-in support for, it parses a series of external configuration files to find an external handler. The default search string for these files is a colon delimited list containing the following files: @@ -8389,12 +8389,12 @@ audio/x-aiff aif aifc aiff where $HOME is your home directory. The $PKGDATADIR and the - $SYSCONFDIR directories depend on where Mutt is + $SYSCONFDIR directories depend on where NeoMutt is installed: the former is the default for shared data, the latter for system configuration files. The default search path can be obtained by running the following command: - mutt -nF /dev/null -Q mailcap_path + neomutt -nF /dev/null -Q mailcap_path In particular, the metamail distribution will install a mailcap file, usually as /usr/local/etc/mailcap, which contains some baseline @@ -8427,11 +8427,11 @@ audio/x-aiff aif aifc aiff default is to send the body of the MIME message to the command on stdin. You can change this behavior by using %s as a parameter to your view command. This will - cause Mutt to save the body of the MIME message to a temporary file, + cause NeoMutt to save the body of the MIME message to a temporary file, and then call the view command with the %s replaced by the name of the temporary file. In - both cases, Mutt will turn over the terminal to the view program until - the program quits, at which time Mutt will remove the temporary file if + both cases, NeoMutt will turn over the terminal to the view program until + the program quits, at which time NeoMutt will remove the temporary file if it exists. This means that mailcap does not work out of the box with programs which detach themselves from the terminal right after starting, like @@ -8475,19 +8475,19 @@ text/*; more Secure Use of Mailcap The interpretation of shell meta-characters embedded in MIME - parameters can lead to security problems in general. Mutt tries to + parameters can lead to security problems in general. NeoMutt tries to quote parameters in expansion of %s syntaxes properly, and avoids risky characters by substituting them, see the $mailcap_sanitize variable. - Although Mutt's procedures to invoke programs with mailcap seem + Although NeoMutt's procedures to invoke programs with mailcap seem to be safe, there are other applications parsing mailcap, maybe taking less care of it. Therefore you should pay attention to the following rules: Keep the %-expandos away from shell quoting.Don't - quote them with single or double quotes. Mutt does this for you, the + quote them with single or double quotes. NeoMutt does this for you, the right way, as should any other program which interprets mailcap. Don't put them into backtick expansions. Be highly careful with evil statements, and avoid them if possible at all. Trying to fix broken @@ -8512,17 +8512,17 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ Optional Fields In addition to the required content-type and view command fields, you can add semi-colon - ;separated fields to set flags and other options. Mutt + ;separated fields to set flags and other options. NeoMutt recognizes the following optional fields: copiousoutput - This flag tells Mutt that the command passes possibly - large amounts of text on standard output. This causes Mutt to + This flag tells NeoMutt that the command passes possibly + large amounts of text on standard output. This causes NeoMutt to invoke a pager (either the internal pager or the external pager defined by the pager variable) on the output of the view - command. Without this flag, Mutt assumes that the command is + command. Without this flag, NeoMutt assumes that the command is interactive. One could use this to replace the pipe to more in the lynx -dump example in the Basic @@ -8530,9 +8530,9 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ text/html; lynx -dump %s ; copiousoutput This will cause lynx to format the text/html output as - text/plain and Mutt will use your standard + text/plain and NeoMutt will use your standard pager to display the results. - Mutt will set the + NeoMutt will set the COLUMNS environment variable to the width of the pager. Some programs make use of this environment variable automatically. Others provide a command line argument that can @@ -8547,7 +8547,7 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ needsterminal - Mutt uses this flag when viewing attachments with + NeoMutt uses this flag when viewing attachments with auto_view , in order to decide whether it should honor the setting @@ -8555,7 +8555,7 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ $wait_key variable or not. When an attachment is viewed using an interactive program, and the corresponding mailcap entry has a - needsterminal flag, Mutt will use + needsterminal flag, NeoMutt will use $wait_key and the exit status of the program to decide if it will ask you to press a key after the external program has exited. In all other situations it @@ -8566,7 +8566,7 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ compose=<command> This flag specifies the command to use to create a new - attachment of a specific MIME type. Mutt supports this from the + attachment of a specific MIME type. NeoMutt supports this from the compose menu. @@ -8575,9 +8575,9 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ This flag specifies the command to use to create a new attachment of a specific MIME type. This command differs from - the compose command in that Mutt will expect standard MIME + the compose command in that NeoMutt will expect standard MIME headers on the data. This can be used to specify parameters, - filename, description, etc. for a new attachment. Mutt supports + filename, description, etc. for a new attachment. NeoMutt supports this from the compose menu. @@ -8585,7 +8585,7 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ print=<command> This flag specifies the command to use to print a - specific MIME type. Mutt supports this from the attachment and + specific MIME type. NeoMutt supports this from the attachment and compose menus. @@ -8593,8 +8593,8 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ edit=<command> This flag specifies the command to use to edit a specific - MIME type. Mutt supports this from the compose menu, and also - uses it to compose new attachments. Mutt will default to the + MIME type. NeoMutt supports this from the compose menu, and also + uses it to compose new attachments. NeoMutt will default to the defined $editor for text attachments. @@ -8621,22 +8621,22 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ This field specifies a command to run to test whether this mailcap entry should be used. The command is defined with the command expansion rules defined in the next section. If the - command returns 0, then the test passed, and Mutt uses this + command returns 0, then the test passed, and NeoMutt uses this entry. If the command returns non-zero, then the test failed, - and Mutt continues searching for the right entry. Note that the - content-type must match before Mutt performs the test. For + and NeoMutt continues searching for the right entry. Note that the + content-type must match before NeoMutt performs the test. For example: text/html; firefox -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s - In this example, Mutt will run the program + In this example, NeoMutt will run the program RunningX which will return 0 if the X Window manager is running, and non-zero if it isn't. If - RunningX returns 0, then Mutt will run + RunningX returns 0, then NeoMutt will run firefox to display the text/html object. If RunningX doesn't return - 0, then Mutt will go on to the next entry and use lynx to + 0, then NeoMutt will go on to the next entry and use lynx to display the text/html object. @@ -8646,18 +8646,18 @@ text/html; lynx %s Search Order - When searching for an entry in the mailcap file, Mutt will + When searching for an entry in the mailcap file, NeoMutt will search for the most useful entry for its purpose. For instance, if you are attempting to print an image/gif, and you have the following entries in - your mailcap file, Mutt will search for an entry with the print + your mailcap file, NeoMutt will search for an entry with the print command: image/*; xv %s image/gif; ; print= anytopnm %s | pnmtops | lpr; \ nametemplate=%s.gif - Mutt will skip the + NeoMutt will skip the image/*entry and use the image/gif entry with the print command. In addition, you can use this with @@ -8678,11 +8678,11 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput For auto_view - , Mutt will choose the third entry because of the - copiousoutput tag. For interactive viewing, Mutt + , NeoMutt will choose the third entry because of the + copiousoutput tag. For interactive viewing, NeoMutt will run the program RunningX to determine if it should use the first - entry. If the program returns non-zero, Mutt will use the second + entry. If the program returns non-zero, NeoMutt will use the second entry for interactive viewing. The last entry is for inline display in the pager and the <view-attach>function in the attachment @@ -8693,7 +8693,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput actually be the first matching one with the tag set. For non-interactive use, only copiousoutput-tagged entries are considered. For - interactive use, Mutt ignores this tag and treats all entries + interactive use, NeoMutt ignores this tag and treats all entries equally. Therefore, if not specified last, all following entries without this tag would never be considered for <view-attach>because the @@ -8707,7 +8707,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput /bin/sh shell using the system(3)function. Before the command is passed to /bin/sh -c, it is parsed to expand various special - parameters with information from Mutt. The keywords Mutt expands + parameters with information from NeoMutt. The keywords NeoMutt expands are: @@ -8717,7 +8717,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput expanded to a filename specified by the calling program. This file contains the body of the message to view/print/edit or where the composing program should place the results of - composition. In addition, the use of this keyword causes Mutt + composition. In addition, the use of this keyword causes NeoMutt to not pass the body of the message to the view/print/edit program on stdin. @@ -8725,7 +8725,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput %t - Mutt will expand + NeoMutt will expand %t to the text representation of the content type of the message in the same form as the first parameter of the mailcap definition line, i.e. @@ -8736,11 +8736,11 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput %{<parameter>} - Mutt will expand this to the value of the specified + NeoMutt will expand this to the value of the specified parameter from the Content-Type: line of the mail message. For instance, if your mail message contains: Content-Type: text/plain; charset=iso-8859-1 - then Mutt will expand + then NeoMutt will expand %{charset}to iso-8859-1. The default metamail mailcap file uses this feature to test the charset to spawn an xterm using @@ -8755,11 +8755,11 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - Mutt does not currently support the + NeoMutt does not currently support the %F and %n keywords specified in RFC 1524. The main purpose of these parameters is for multipart messages, which is handled - internally by Mutt. + internally by NeoMutt. @@ -8826,9 +8826,9 @@ application/ms-excel; open.pl %s - In addition to explicitly telling Mutt to view an attachment with + In addition to explicitly telling NeoMutt to view an attachment with the MIME viewer defined in the mailcap file from the attachments menu, - Mutt has support for automatically viewing MIME attachments while in the + NeoMutt has support for automatically viewing MIME attachments while in the pager. For this to work, you must define a viewer in the mailcap file which uses the @@ -8844,7 +8844,7 @@ application/ms-excel; open.pl %s auto_view text/html application/x-gunzip \ application/postscript image/gif application/x-tar-gz - ...Mutt would try to find corresponding entries for rendering + ...NeoMutt would try to find corresponding entries for rendering attachments of these types as text. A corresponding mailcap could look like: @@ -8874,11 +8874,11 @@ application/postscript; ps2ascii %s; copiousoutput MIME parts which represent the same content in an alternative way. This is often used to send HTML messages which contain an alternative plain text representation. - Mutt has some heuristics for determining which attachment of a + NeoMutt has some heuristics for determining which attachment of a multipart/alternative type to display: - First, Mutt will check the + First, NeoMutt will check the alternative_order list to determine if one of the available types is preferred. It consists of a number of MIME types in order, including support for implicit and explicit wildcards. For @@ -8889,16 +8889,16 @@ alternative_order text/enriched text/plain text \ - Next, Mutt will check if any of the types have a defined + Next, NeoMutt will check if any of the types have a defined auto_view , and use that. - Failing that, Mutt will look for any text type. + Failing that, NeoMutt will look for any text type. - As a last attempt, Mutt will look for any type it knows how to + As a last attempt, NeoMutt will look for any type it knows how to handle. @@ -8909,14 +8909,14 @@ alternative_order text/enriched text/plain text \ Attachment Searching and Counting - If you ever lose track of attachments in your mailboxes, Mutt's + If you ever lose track of attachments in your mailboxes, NeoMutt's attachment-counting and -searching support might be for you. You can make your message index display the number of qualifying attachments in each message, or search for messages by attachment count. You also can configure what kinds of attachments qualify for this feature with the attachments and unattachments commands. - In order to provide this information, Mutt needs to fully + In order to provide this information, NeoMutt needs to fully MIME-parse all messages affected first. This can slow down operation especially for remote mail folders such as IMAP because all messages have to be downloaded first regardless whether the user really wants to view @@ -9008,11 +9008,11 @@ alternative_order text/enriched text/plain text \ # Qualify any MIME part with an "attachment" disposition, EXCEPT for # text/x-vcard and application/pgp parts. (PGP parts are already known -# to mutt, and can be searched for with ~g, ~G, and ~k.) +# to NeoMutt, and can be searched for with ~g, ~G, and ~k.) # # I've added x-pkcs7 to this, since it functions (for S/MIME) # analogously to PGP signature attachments. S/MIME isn't supported -# in a stock mutt build, but we can still treat it specially here. +# in a stock NeoMutt build, but we can still treat it specially here. # @@ -9026,7 +9026,7 @@ attachments -A application/x-pkcs7-.* attachments +I text/plain -# These two lines make Mutt qualify MIME containers. (So, for example, +# These two lines make NeoMutt qualify MIME containers. (So, for example, # a message/rfc822 forward will count as an attachment.) The first # line is unnecessary if you already have "attach-allow */.*", of # course. These are off by default! The MIME elements contained @@ -9069,7 +9069,7 @@ attachments -I message/external-body - Mutt's + NeoMutt's mime_lookup list specifies a list of MIME types that should not be treated according to their mailcap entry. This @@ -9100,7 +9100,7 @@ attachments -I message/external-body Enabling/Disabling Features - Mutt supports several of optional features which can be enabled + NeoMutt 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 @@ -9108,19 +9108,19 @@ attachments -I message/external-body 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 + neomutt -v. If a compile option starts with +it is enabled and disabled if prefixed with - -. For example, if Mutt was compiled using GnuTLS for + -. For example, if NeoMutt was compiled using GnuTLS for encrypted communication instead of OpenSSL, - mutt -v would contain: + neomutt -v would contain: -openssl +gnutls URL Syntax - Mutt optionally supports the IMAP, POP3 and SMTP protocols which + NeoMutt optionally supports the IMAP, POP3 and SMTP protocols which require to access servers using URLs. The canonical syntax for - specifying URLs in Mutt is (an item enclosed in + specifying URLs in NeoMutt is (an item enclosed in []means it is optional and may be omitted): proto[s]://[username[:password]@]server[:port][/path] @@ -9129,9 +9129,9 @@ attachments -I message/external-body pop for POP3 and smtp for SMTP. If s for - secure communication is appended, Mutt will attempt to + secure communication is appended, NeoMutt will attempt to establish an encrypted communication using SSL or TLS. - Since all protocols supported by Mutt support/require + Since all protocols supported by NeoMutt support/require authentication, login credentials may be specified in the URL. This has the advantage that multiple IMAP, POP3 or SMTP servers may be specified (which isn't possible using, for example, @@ -9148,7 +9148,7 @@ attachments -I message/external-body %-notation. A password can be given, too but is not recommended if the URL is specified in a configuration file on disk. - If no port number is given, Mutt will use the system's default + If no port number is given, NeoMutt will use the system's default for the given protocol (usually consulting /etc/services). The optional path is only relevant for IMAP and ignored @@ -9166,12 +9166,12 @@ smtp://user@host:587/ SSL/TLS Support - If Mutt is compiled with IMAP, POP3 and/or SMTP support, it can + If NeoMutt is compiled with IMAP, POP3 and/or SMTP support, it can also be compiled with support for SSL or TLS using either OpenSSL or GnuTLS ( by running the configure script with the --enable-ssl=...option for OpenSSL or - --enable-gnutls=...for GnuTLS). Mutt can then + --enable-gnutls=...for GnuTLS). NeoMutt can then attempt to encrypt communication with remote servers if these protocols are suffixed with s for @@ -9180,7 +9180,7 @@ smtp://user@host:587/ POP3 Support - Mutt has POP3 support and has the ability to work with mailboxes + NeoMutt has POP3 support and has the ability to work with mailboxes located on a remote POP3 server and fetch mail for local browsing. Remote POP3 servers can be accessed using URLs with the @@ -9188,17 +9188,17 @@ smtp://user@host:587/ pops for encrypted communication, see for details. Polling for new mail is more expensive over POP3 than locally. For - this reason the frequency at which Mutt will check for mail remotely can + this reason the frequency at which NeoMutt will check for mail remotely can be controlled by the $pop_checkinterval variable, which defaults to every 60 seconds. POP is read-only which doesn't allow for some features like editing messages or changing flags. However, using and - Mutt simulates the new/old/read flags as - well as flagged and replied. Mutt applies some logic on top of remote + NeoMutt simulates the new/old/read flags as + well as flagged and replied. NeoMutt applies some logic on top of remote messages but cannot change them so that modifications of flags are lost - when messages are downloaded from the POP server (either by Mutt or other + when messages are downloaded from the POP server (either by NeoMutt or other tools). Another way to access your POP3 mail is the @@ -9206,7 +9206,7 @@ smtp://user@host:587/ connect to $pop_host, fetch all your new mail and place it in the local - $spoolfile. After this point, Mutt runs + $spoolfile. After this point, NeoMutt runs exactly as if the mail had always been local. If you only need to fetch all messages to a local mailbox you @@ -9218,7 +9218,7 @@ smtp://user@host:587/ IMAP Support - Mutt has IMAP support and has the ability to work with folders + NeoMutt has IMAP support and has the ability to work with folders located on a remote IMAP server. You can access the remote inbox by selecting the folder by its URL (see @@ -9229,7 +9229,7 @@ smtp://user@host:587/ {[username@]imapserver[:port][/ssl]}path/to/folder Note that not all servers use - /as the hierarchy separator. Mutt should correctly notice + /as the hierarchy separator. NeoMutt should correctly notice which separator is being used by the server and convert paths accordingly. When browsing folders on an IMAP server, you can toggle whether to @@ -9255,12 +9255,12 @@ set timeout=15 The IMAP Folder Browser - As of version 1.2, Mutt supports browsing mailboxes on an IMAP + As of version 1.2, NeoMutt supports browsing mailboxes on an IMAP server. This is mostly the same as the local file browser, with the following differences: - In lieu of file permissions, Mutt displays the string + In lieu of file permissions, NeoMutt displays the string IMAP, possibly followed by the symbol +, indicating that the entry contains both messages and subfolders. On Cyrus-like servers folders will often contain @@ -9295,7 +9295,7 @@ set timeout=15 Authentication - Mutt supports four authentication methods with IMAP servers: + NeoMutt supports four authentication methods with IMAP servers: SASL, GSSAPI, CRAM-MD5, and LOGIN. There is also support for the pseudo-protocol ANONYMOUS, which allows you to log in to a public IMAP server without having an account. To use ANONYMOUS, simply make @@ -9308,9 +9308,9 @@ set timeout=15 GSSAPI), your entire session will be encrypted and invisible to those teeming network snoops. It is the best option if you have it. To use it, you must have the Cyrus SASL library installed on your system and - compile Mutt with the + compile NeoMutt with the --with-sasl flag. - Mutt will try whichever methods are compiled in and available on + NeoMutt will try whichever methods are compiled in and available on the server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN. There are a few variables which control authentication: @@ -9333,7 +9333,7 @@ set timeout=15 $imap_authenticators- a colon-delimited list of IMAP authentication methods to try, in the - order you wish to try them. If specified, this overrides Mutt's + order you wish to try them. If specified, this overrides NeoMutt's default (attempt everything, in the order listed above). @@ -9343,10 +9343,10 @@ set timeout=15 SMTP Support Besides supporting traditional mail delivery through a - sendmail-compatible program, Mutt supports delivery through SMTP. + sendmail-compatible program, NeoMutt supports delivery through SMTP. If the configuration variable - $smtp_url is set, Mutt will contact the - given SMTP server to deliver messages; if it is unset, Mutt will use the + $smtp_url is set, NeoMutt will contact the + given SMTP server to deliver messages; if it is unset, NeoMutt will use the program specified by $sendmail. For details on the URL syntax, please see @@ -9356,7 +9356,7 @@ set timeout=15 authentication using SASL. The authentication mechanisms for SASL are specified in $smtp_authenticators defaulting - to an empty list which makes Mutt try all available methods from + to an empty list which makes NeoMutt try all available methods from most-secure to least-secure. @@ -9380,7 +9380,7 @@ set timeout=15 command may help. This hook works like folder-hook - but is invoked whenever Mutt needs to access a remote mailbox + but is invoked whenever NeoMutt needs to access a remote mailbox (including inside the folder browser), not just when you open the mailbox. This includes (for example) polling for new mail, storing Fcc messages and saving messages to a folder. As a consequence, @@ -9420,7 +9420,7 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen the folders are defined using mailboxes - so Mutt polls them for new mail. Each + so NeoMutt polls them for new mail. Each folder-hook triggers when one mailbox below each IMAP account is opened and @@ -9442,20 +9442,20 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen Local Caching - Mutt contains two types of local caching: + NeoMutt 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. Header caching is optional as it depends on external libraries, - body caching is always enabled if Mutt is compiled with POP and/or IMAP + body caching is always enabled if NeoMutt is compiled with POP and/or IMAP support as these use it (body caching requires no external library). Header Caching - Mutt provides optional support for caching message headers for + NeoMutt provides optional support for caching message headers for the following types of folders: IMAP, POP, Maildir and MH. Header caching greatly speeds up opening large folders because for remote folders, headers usually only need to be downloaded once. For Maildir @@ -9484,13 +9484,13 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen Both cache methods can be combined using the same directory for storage (and for IMAP/POP even provide meaningful file names) which simplifies manual maintenance tasks. - In addition to caching message headers only, Mutt can also cache + In addition to caching message headers only, NeoMutt can also cache whole message bodies. This results in faster display of messages for POP and IMAP folders because messages usually have to be downloaded only once. For configuration, the variable $message_cachedir must point to - a directory. There, Mutt will create a hierarchy of subdirectories + a directory. There, NeoMutt will create a hierarchy of subdirectories named like the account and mailbox path the cache is for. @@ -9500,15 +9500,15 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen $header_cache and $message_cachedir can be safely set to the same value. - In a header or body cache directory, Mutt creates a directory + In a header or body cache directory, NeoMutt creates a directory hierarchy named like: proto:user@hostname where proto is either pop or - imap.Within there, for each folder, Mutt stores messages + imap.Within there, for each folder, NeoMutt stores messages in single files and header caches in files with the .hcache extension. All files can be removed as needed if - the consumed disk space becomes an issue as Mutt will silently fetch + the consumed disk space becomes an issue as NeoMutt will silently fetch missing items again. Pathnames are always stored in UTF-8 encoding. For Maildir and MH, the header cache files are named after the @@ -9517,17 +9517,17 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen Maintenance - Mutt does not (yet) support maintenance features for header cache + NeoMutt does not (yet) support maintenance features for header cache database files so that files have to be removed in case they grow too big. It depends on the database library used for header caching whether disk space freed by removing messages is re-used. - For body caches, Mutt can keep the local cache in sync with the + For body caches, NeoMutt can keep the local cache in sync with the remote mailbox if the $message_cache_clean variable is set. Cleaning means to remove messages from the cache which are no longer present in the mailbox which only happens when other mail - clients or instances of Mutt using a different body cache location - delete messages (Mutt itself removes deleted messages from the cache + clients or instances of NeoMutt using a different body cache location + delete messages (NeoMutt itself removes deleted messages from the cache when syncing a mailbox). As cleaning can take a noticeable amount of time, it should not be set in general but only occasionally. @@ -9535,14 +9535,14 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen Sending Anonymous Messages via Mixmaster - You may also have compiled Mutt to co-operate with Mixmaster, an + You may also have compiled NeoMutt to co-operate with Mixmaster, an anonymous remailer. Mixmaster permits you to send your messages - anonymously using a chain of remailers. Mixmaster support in Mutt is for + anonymously using a chain of remailers. Mixmaster support in NeoMutt is for mixmaster version 2.04 or later. To use it, you'll have to obey certain restrictions. Most important, you cannot use the Cc and - Bcc headers. To tell Mutt to use mixmaster, you have to + Bcc headers. To tell NeoMutt to use mixmaster, you have to select a remailer chain, using the mix function on the compose menu. The chain selection screen is divided into two parts. In the @@ -9690,7 +9690,7 @@ color attach_headers brightmagenta default "invalid node with pac Functions - compose-to-sender adds the following function to Mutt. By + compose-to-sender adds the following function to NeoMutt. By default, it is not bound to a key.
@@ -9765,12 +9765,12 @@ bind index,pager @ compose-to-sender Introduction - The Compressed Folder feature allows Mutt to read mailbox files + The Compressed Folder feature allows NeoMutt to read mailbox files that are compressed. But it isn't limited to compressed files. It works well with encrypted files, too. In fact, if you can create a - program/script to convert to and from your format, then Mutt can read + program/script to convert to and from your format, then NeoMutt can read it. - The feature adds three hooks to Mutt: + The feature adds three hooks to NeoMutt: open-hook, close-hook and append-hook. They define commands to: uncompress a @@ -9881,7 +9881,7 @@ bind index,pager @ compose-to-sender Read from compressed mailbox open-hook regexp shell-command - If Mutt is unable to open a file, it then looks for + If NeoMutt is unable to open a file, it then looks for open-hook that matches the filename. If your compression program doesn't have a well-defined extension, then you can use @@ -9893,16 +9893,16 @@ bind index,pager @ compose-to-sender open-hook '\.gz$' "gzip --stdout --decompress '%f' > '%t'" - Mutt finds a file, + NeoMutt finds a file, example.gz, that it can't read - Mutt has an + NeoMutt has an open-hook whose regexp matches the filename: \.gz$ - Mutt uses the command + NeoMutt uses the command gzip -cd to create a temporary file that it can read @@ -9913,7 +9913,7 @@ bind index,pager @ compose-to-sender Write to a compressed mailbox close-hook regexp shell-command - When Mutt has finished with a compressed mail folder, it will + When NeoMutt has finished with a compressed mail folder, it will look for a matching close-hook to recompress the file. This hook is optional. @@ -9928,7 +9928,7 @@ bind index,pager @ compose-to-sender close-hook '\.gz$' "gzip --stdout '%t' > '%f'" - Mutt has finished with a folder, + NeoMutt has finished with a folder, example.gz, that it opened with open-hook @@ -9936,12 +9936,12 @@ bind index,pager @ compose-to-sender The folder has been modified - Mutt has a + NeoMutt has a close-hook whose regexp matches the filename: \.gz$ - Mutt uses the command + NeoMutt uses the command gzip -c to create a new compressed file @@ -9958,19 +9958,19 @@ bind index,pager @ compose-to-sender Append to a compressed mailbox append-hook regexp shell-command - When Mutt wants to append an email to a compressed mail folder, + When NeoMutt wants to append an email to a compressed mail folder, it will look for a matching append-hook. This hook is optional. Using the - append-hook will save time, but Mutt won't be able + append-hook will save time, but NeoMutt won't be able to determine the type of the mail folder inside the compressed file. - Mutt will + NeoMutt will assume the type to be that of the - $mbox_type variable. Mutt also uses this type for + $mbox_type variable. NeoMutt also uses this type for temporary files. - Mutt will only use the + NeoMutt will only use the append-hook for existing files. The close-hook will be used for empty, or missing files. @@ -9986,22 +9986,22 @@ bind index,pager @ compose-to-sender append-hook '\.gz$' "gzip --stdout '%t' >> '%f'" - Mutt wants to append an email to a folder, + NeoMutt wants to append an email to a folder, example.gz, that it opened with open-hook - Mutt has an + NeoMutt has an append-hook whose regexp matches the filename: \.gz$ - Mutt knows the mailbox type from the + NeoMutt knows the mailbox type from the $mbox variable - Mutt uses the command + NeoMutt uses the command gzip -c to append to an existing compressed file @@ -10017,7 +10017,7 @@ bind index,pager @ compose-to-sender Empty Files - Mutt assumes that an empty file is not compressed. In this + NeoMutt assumes that an empty file is not compressed. In this situation, unset $save_empty, so that the compressed file will be removed if you delete all of the messages. @@ -10037,7 +10037,7 @@ bind index,pager @ compose-to-sender # Example NeoMutt config file for the compress feature. -# This feature adds three hooks to Mutt which allow it to +# This feature adds three hooks to NeoMutt which allow it to # work with compressed, or encrypted, mailboxes. # The hooks are of the form: @@ -10164,7 +10164,7 @@ close-hook '\.gpg$' "gpg --encrypt --recipient YourGpgUserIdOrKeyId < '%t' & Conditional Dates feature allows you to construct $index_format expressions based on the age of the email. - Mutt's default + NeoMutt's default $index_format displays email dates in the form: abbreviated-month day-of-month — Jan 14. @@ -10218,7 +10218,7 @@ close-hook '\.gpg$' "gpg --encrypt --recipient YourGpgUserIdOrKeyId < '%t' & strftime(3). By carefully picking your formats, the dates can remain unambiguous and compact. - Mutt's conditional format strings have the form: (whitespace + NeoMutt's conditional format strings have the form: (whitespace introduced for clarity) %? TEST ? TRUE & FALSE ? The examples below use the test @@ -10507,7 +10507,7 @@ set index_format='%4C %Z %<[y?%<[m?%<[d?%[%H:%M ]&%[%a %d]>& in the last 7 days, but this week. This doesn't match the normal - Mutt behavior: for example + NeoMutt behavior: for example ~d>1w means emails dated in the last 7 days. @@ -10687,7 +10687,7 @@ set pgp_self_encrypt = "no" IntroductionThe fmemopen feature speeds up some searches. - This feature changes a few places where Mutt creates temporary + This feature changes a few places where NeoMutt creates temporary files. It replaces them with in-memory buffers. This should improve the performance when searching the header or body using the $thorough_search option. @@ -10695,7 +10695,7 @@ set pgp_self_encrypt = "no" This feature depends on open_memstream()and fmemopen(). They are provided by glibc. Without - them, Mutt will simply create temporary files. + them, NeoMutt will simply create temporary files. @@ -10754,7 +10754,7 @@ set pgp_self_encrypt = "no" Introduction The forgotten-attachment feature provides a new - setting for Mutt that alerts the user if the message body contains a + setting for NeoMutt that alerts the user if the message body contains a certain keyword but there are no attachments added. This is meant to ensure that the user does not forget to attach a file after promising to do so in the mail. The attachment keyword will not be scanned in @@ -10804,7 +10804,7 @@ set pgp_self_encrypt = "no" # Example NeoMutt config file for the forgotten-attachment feature. -# The 'forgotten-attachment' feature provides a new setting for Mutt that +# The 'forgotten-attachment' feature provides a new setting for NeoMutt that # alerts the user if the message body contains a certain regular expression but there are # no attachments added. This is meant to ensure that the user does not forget # to attach a file after promising to do so in the mail. @@ -10876,12 +10876,12 @@ set attach_keyword = "\\<attach(|ed|ments?)\\>" Global Hooks - Define actions to run globally within Mutt + Define actions to run globally within NeoMutt Introduction These hooks are called when global events take place in - Mutt. + NeoMutt. Run a command... @@ -10890,12 +10890,12 @@ set attach_keyword = "\\<attach(|ed|ments?)\\>" - startup-hook- when mutt starts up, + startup-hook- when NeoMutt starts up, before opening the first mailbox - shutdown-hook- mutt shuts down, + shutdown-hook- NeoMutt shuts down, before closing the last mailbox @@ -10906,17 +10906,17 @@ set attach_keyword = "\\<attach(|ed|ments?)\\>" Since:NeoMutt 2016-08-08 This feature implements a new hook that is called periodically - when Mutt checks for new mail. This hook is called every + when NeoMutt checks for new mail. This hook is called every $timeout seconds. Startup Hook - Run a command when mutt starts up, before opening the first + Run a command when NeoMutt starts up, before opening the first mailbox Since:NeoMutt 2016-11-25 - This feature implements a new hook that is called when Mutt + This feature implements a new hook that is called when NeoMutt first starts up, but before opening the first mailbox. This is most likely to be useful to users of notmuch. @@ -10924,11 +10924,11 @@ set attach_keyword = "\\<attach(|ed|ments?)\\>" Shutdown Hook - Run a command when mutt shuts down, before closing the last + Run a command when NeoMutt shuts down, before closing the last mailbox Since:NeoMutt 2016-11-25 - This feature implements a hook that is called when Mutt shuts + This feature implements a hook that is called when NeoMutt shuts down, but before closing the first mailbox. This is most likely to be useful to users of notmuch. @@ -10940,19 +10940,19 @@ set attach_keyword = "\\<attach(|ed|ments?)\\>" timeout-hook - MUTT-COMMAND + NEOMUTT-COMMAND startup-hook - MUTT-COMMAND + NEOMUTT-COMMAND shutdown-hook - MUTT-COMMAND + NEOMUTT-COMMAND @@ -10965,11 +10965,11 @@ set attach_keyword = "\\<attach(|ed|ments?)\\>" # -------------------------------------------------------------------------- # COMMANDS - shown with an example argument # -------------------------------------------------------------------------- -# After $timeout seconds of inactivity, run this mutt command +# After $timeout seconds of inactivity, run this NeoMutt command timeout-hook 'exec sync-mailbox' -# When mutt first loads, run this mutt command +# When NeoMutt first loads, run this NeoMutt command startup-hook 'exec sync-mailbox' -# When mutt quits, run this mutt command +# When NeoMutt quits, run this NeoMutt command shutdown-hook 'exec sync-mailbox' # vim: syntax=muttrc @@ -11026,8 +11026,8 @@ shutdown-hook 'exec sync-mailbox' Introduction The - ifdef feature introduces three new commands to Mutt and - allow you to share one config file between versions of Mutt that may + ifdef feature introduces three new commands to NeoMutt and + allow you to share one config file between versions of NeoMutt that may have different features compiled in. ifdef symbol config-command [args...] # If a symbol is defined @@ -11040,7 +11040,7 @@ finish # Finish readin command or compile-time symbol, such as imap. A list of compile-time symbols can be seen in the output of the - command mutt -v (in the Compile options + command neomutt -v (in the Compile options section). finish is particularly useful when combined with @@ -11080,27 +11080,27 @@ ifndef sidebar finish # Example NeoMutt config file for the ifdef feature. # This feature introduces three useful commands which allow you to share -# one config file between versions of Mutt that may have different +# one config file between versions of NeoMutt that may have different # features compiled in. # ifdef symbol config-command [args...] # ifndef symbol config-command [args...] # finish -# The 'ifdef' command tests whether Mutt understands the name of +# The 'ifdef' command tests whether NeoMutt understands the name of # a variable, function, command or compile-time symbol. # If it does, then it executes a config command. # The 'ifndef' command tests whether a symbol does NOT exist. -# The 'finish' command tells Mutt to stop reading current config file. +# The 'finish' command tells NeoMutt to stop reading current config file. # If the 'trash' variable exists, set it. ifdef trash 'set trash=~/Mail/trash' # If the 'tag-pattern' function exists, bind a key to it. ifdef tag-pattern 'bind index <F6> tag-pattern' # If the 'imap-fetch-mail' command exists, read my IMAP config. -ifdef imap-fetch-mail 'source ~/.mutt/imap.rc' +ifdef imap-fetch-mail 'source ~/.neomutt/imap.rc' # If the compile-time symbol 'sidebar' does not exist, then # stop reading the current config file. ifndef sidebar finish @@ -11165,9 +11165,9 @@ ifndef sidebar finish if needed, pick a pattern to match. Note: The pattern does not have to refer to the object you wish to color. e.g. - color index_author red default "~smutt" + color index_author red default "~sneomutt" The author appears red when the subject (~s) contains - mutt. + neomutt. @@ -11482,40 +11482,40 @@ set index_format='%4C %Z %{%b %d} %I (%?l?%4l&%4c?) %s' Introduction Unify label/keyword handling. - Since x-labels were added to mutt in 2000, a number of other + Since x-labels were added to NeoMutt in 2000, a number of other approaches to what we now call tagging have also emerged. One of them was even made standard in RFC 2822. This update unifies the handling of all these strategies. - We start by changing mutt's internal keyword storage from a + We start by changing NeoMutt's internal keyword storage from a single string which may contain whitespace to a list of discrete keywords. This has advantages for keyword completion as well as for portability among varying "standards" for keyword storage. This may - represent a significant change for existing mutt users who have set + represent a significant change for existing NeoMutt users who have set x-labels containing spaces, and should be regarded with suspicion. The advantages are significant, though. - Next we allow mutt to parse keywords into this internal list from + Next we allow NeoMutt to parse keywords into this internal list from any of the following headers: X-Label (freeform), X-Keywords (space-delimited), X-Mozilla-Keys (space-delimited), and Keywords (RFC - 2822, comma-space-delimited). Mutt remembers which headers it sourced + 2822, comma-space-delimited). NeoMutt remembers which headers it sourced keywords from, and can rewrite those headers when saving messages for compatibility with the mailer of origin. - (X-Label was specified as freeform text by mutt, its only known + (X-Label was specified as freeform text by NeoMutt, its only known implementation. X-Labels have been used both as a tagging device, probably with space delimiting, and as a memo field, where space-delimited parsing would ruin the - semantics of the memo. By default mutt will not split X-Labels at all. + semantics of the memo. By default NeoMutt will not split X-Labels at all. Set $xlabel_delimiter if your needs vary.) Finally we add two booleans: $keywords_legacy=true and - $keywords_standard=FALSE. When $keywords_legacy is true, mutt will + $keywords_standard=FALSE. When $keywords_legacy is true, NeoMutt will always save keyword to whatever original header it came from. When - $keywords_standard=true, mutt will save to the Keywords: header. If - both are true mutt saves to both; if neither is true, mutt saves only + $keywords_standard=true, NeoMutt will save to the Keywords: header. If + both are true NeoMutt saves to both; if neither is true, NeoMutt saves only to legacy headers to avoid complete loss of keywords. Overall this represents convergence path for all competing labelling/tagging/keywording systems toward one that is specified by RFC. - You can change or delete the X-Label: field within Mutt using the + You can change or delete the X-Label: field within NeoMutt using the edit-label command. This works for tagged messages, too. @@ -11565,7 +11565,7 @@ set index_format='%4C %Z %{%b %d} %I (%?l?%4l&%4c?) %s' Functions - Keywords adds the following function to Mutt. By default, it is + Keywords adds the following function to NeoMutt. By default, it is not bound to a key.
@@ -11623,9 +11623,9 @@ set index_format='%4C %Z %{%b %d} %I (%?l?%4l&%4c?) %s' # -------------------------------------------------------------------------- # VARIABLES - shown with their default values # -------------------------------------------------------------------------- -# Should Mutt save the keywords to whatever keyword it came from? +# Should NeoMutt save the keywords to whatever keyword it came from? set keywords_legacy = yes -# Should Mutt use the "Keywords:" header? +# Should NeoMutt use the "Keywords:" header? set keywords_standard = no # How should the keywords be separated? set xlabel_delimiter = "" @@ -11701,11 +11701,11 @@ bind index,pager y edit-label - To check if Mutt supports Kyoto Cabinet, look for + To check if NeoMutt supports Kyoto Cabinet, look for - kyoto in the mutt version. + kyoto in the NeoMutt version. @@ -11713,7 +11713,7 @@ bind index,pager y edit-label - hcache backend: kyotocabinet in the mutt + hcache backend: kyotocabinet in the NeoMutt version @@ -11722,7 +11722,7 @@ bind index,pager y edit-label Introduction This feature adds support for using Kyoto Cabinet, the successor - to Tokyo Cabinet, as a storage backend for Mutt's header cache + to Tokyo Cabinet, as a storage backend for NeoMutt's header cache (hcache). It is enabled at configure time with the --with-kyotocabinet=<path>switch. @@ -11784,7 +11784,7 @@ bind index,pager y edit-label Functions - Limit-current-thread adds the following function to Mutt. By + Limit-current-thread adds the following function to NeoMutt. By default, it is not bound to a key.
@@ -11857,7 +11857,7 @@ bind index <esc>L limit-current-thread Introduction This feature adds support for using LMDB as a storage backend for - Mutt's header cache (hcache). It is enabled at configure time with the + NeoMutt's header cache (hcache). It is enabled at configure time with the --with-lmdb=<path>switch. It is not recommended to store the lmdb database on a shared @@ -11984,7 +11984,7 @@ bind index <esc>L limit-current-thread Introduction - Mutt's format strings can contain embedded if-then-else + NeoMutt's format strings can contain embedded if-then-else conditions. They are of the form: %?VAR?TRUE&FALSE? If the variable @@ -11995,13 +11995,13 @@ bind index <esc>L limit-current-thread %?S?Size: %S&Empty? Which can be read as: if (%S > 0) { print "Size: %S" } else { print "Empty" } - These conditions are useful, but in Mutt they cannot be nested + These conditions are useful, but in NeoMutt they cannot be nested within one another. This feature uses the notation %<VAR?TRUE&FALSE>and allows them to be nested. The %<...>notation was used to format the current - local time. but that's not really very useful since mutt has no means + local time. but that's not really very useful since NeoMutt has no means of refreshing the screen periodically. A simple nested condition might be: (Some whitespace has been introduced for clarity) @@ -12148,11 +12148,11 @@ set index_format='%4C %Z %{%b %d} %-25.25n %<M?[%M] %s&%s%* %<l?%l& $status_format. When the notification is sent, the folder of the new mail is no longer known. - This is a limitation of Mutt. The `%f` expando will show the open folder. + This is a limitation of NeoMutt. The `%f` expando will show the open folder. For example in Linux you can use (most distributions already provide notify-send): - set new_mail_command="notify-send --icon='/home/santiago/Pictures/mutt.png' 'New Email' '%n new messages, %u unread.' &" + set new_mail_command="notify-send --icon='/home/santiago/Pictures/neomutt.png' 'New Email' '%n new messages, %u unread.' &" And in OS X you will need to install a command line interface for Notification Center, for example @@ -12194,10 +12194,10 @@ set index_format='%4C %Z %{%b %d} %-25.25n %<M?[%M] %s&%s%* %<l?%l& # -------------------------------------------------------------------------- # VARIABLES - shown with their default values # -------------------------------------------------------------------------- -# Set the command you want mutt to execute upon the receipt of a new email +# Set the command you want NeoMutt to execute upon the receipt of a new email set new_mail_command = "" # Linux example: -# set new_command="notify-send --icon='/home/santiago/Pictures/mutt.png' 'New Email in %f' '%n new messages, %u unread.' &" +# set new_command="notify-send --icon='/home/santiago/Pictures/neomutt.png' 'New Email in %f' '%n new messages, %u unread.' &" # OS X example: # set new_mail_command="terminal-notifier -title '%v' -subtitle 'New Mail in %f' -message '%n new messages, %u unread.' -activate 'com.apple.Terminal'" # -------------------------------------------------------------------------- @@ -12255,7 +12255,7 @@ set new_mail_command = "" Introduction Reading news via NNTP - Mutt can read from a news server using NNTP. + NeoMutt can read from a news server using NNTP. The default news server can be obtained from the $NNTPSERVER environment variable or from the /etc/nntpserver file. Like in other news readers, @@ -12266,9 +12266,9 @@ set new_mail_command = "" <change-newsgroup> The variable $news_cache_dir can be used to - point to a directory. Mutt will create a hierarchy of subdirectories + point to a directory. NeoMutt will create a hierarchy of subdirectories named like the account and newsgroup the cache is for. The hierarchy is - also used to store header cache if Mutt was compiled with + also used to store header cache if NeoMutt was compiled with header cache support. @@ -12371,7 +12371,7 @@ set new_mail_command = "" string - ~/.mutt + ~/.neomutt @@ -12490,7 +12490,7 @@ set new_mail_command = "" Functions - NNTP adds the following functions to Mutt. By default, none of + NNTP adds the following functions to NeoMutt. By default, none of them are bound to keys.
@@ -12659,7 +12659,7 @@ set inews = '' set mime_subject = yes set newsgroups_charset = utf-8 set newsrc = '~/.newsrc' -set news_cache_dir = '~/.mutt' +set news_cache_dir = '~/.neomutt' set news_server = '' set nntp_authenticators = '' set nntp_context = 1000 @@ -12838,7 +12838,7 @@ virtual-mailboxes "My INBOX" "notmuch://?query=tag:inbox" tag:AAA and tag:BBB--encoding-> tag:AAA%20and%20tag:BBB - but mutt config file parser is smart enough to accept space in + but NeoMutt config file parser is smart enough to accept space in quoted strings. It means that you can use notmuch:///foo?query=tag:AAA and tag:BBB @@ -13035,7 +13035,7 @@ virtual-mailboxes "My INBOX" "notmuch://?query=tag:inbox" Functions - Notmuch adds the following functions to Mutt. By default, none of + Notmuch adds the following functions to NeoMutt. By default, none of them are bound to keys.
@@ -13234,7 +13234,7 @@ set nm_db_limit = 0 # notmuch://<absolute path> set nm_default_uri = "" # The messages tagged with these tags are excluded and not loaded -# from notmuch DB to mutt unless specified explicitly. +# from notmuch DB to NeoMutt unless specified explicitly. set nm_exclude_tags = "" # This variable specifies private notmuch tags which should not be printed # on screen (index, pager). @@ -13244,10 +13244,10 @@ set nm_open_timeout = 5 # This variable specifies notmuch query type, supported types: 'threads' and # 'messages'. set nm_query_type = messages -# Add messages stored to the mutt record (see $record in the mutt docs) also to notmuch DB. If you reply to an email then the new email inherits tags from the original email. +# Add messages stored to the NeoMutt record (see $record in the NeoMutt docs) also to notmuch DB. If you reply to an email then the new email inherits tags from the original email. set nm_record = no -# Tags that should be removed or added to the to the messages stored in the mutt record. +# Tags that should be removed or added to the to the messages stored in the NeoMutt record. example: set record = "~/sent-mails" @@ -13269,7 +13269,7 @@ set nm_unread_tag = unread # %*X soft-fill with character ``X'' as pad set vfolder_format = "%6n(%6N) %f" -# When set, mutt will use the first virtual mailbox (see virtual-mailboxes) +# When set, NeoMutt will use the first virtual mailbox (see virtual-mailboxes) # as a spoolfile. set virtual_spoolfile = no # setup time window preferences @@ -13616,7 +13616,7 @@ color progress white red <quasi-delete> - delete from mutt, don't touch on disk + delete from NeoMutt, don't touch on disk @@ -13681,7 +13681,7 @@ bind index,pager Q quasi-delete Introduction - Adds a reply_with_xorig for mutt configuration files. If enabled, + Adds a reply_with_xorig for NeoMutt configuration files. If enabled, allows to reply to an email using the email address in the first X-Original-To: header of a mail as the From: header of the answer. @@ -13845,7 +13845,7 @@ set sort_browser="reverse-size" Support - Since:NeoMutt 2016-09-10, Mutt + Since:NeoMutt 2016-09-10, NeoMutt 1.7.0 Dependencies:None @@ -13994,7 +13994,7 @@ set sort_browser="reverse-size" Functions - Sidebar adds the following functions to Mutt. By default, none of + Sidebar adds the following functions to NeoMutt. By default, none of them are bound to keys.
@@ -14142,7 +14142,7 @@ set sort_browser="reverse-size" sidebar_indicator - mutt + neomutt indicator The mailbox open in the Index panel @@ -14172,7 +14172,7 @@ set sort_browser="reverse-size"
If the sidebar_indicator color isn't set, then the default - Mutt indicator color will be used (the color used in the index + NeoMutt indicator color will be used (the color used in the index panel). @@ -14280,7 +14280,7 @@ sidebar_whitelist '/home/user/mailbox2' set sidebar_next_new_wrap = no # Show the Sidebar on the right-hand side of the screen set sidebar_on_right = no -# The character to use as the divider between the Sidebar and the other Mutt +# The character to use as the divider between the Sidebar and the other NeoMutt # panels. set sidebar_divider_char = '|' # Enable extended buffy mode to calculate total, new, and flagged @@ -14323,11 +14323,11 @@ bind index,pager B sidebar-toggle-visible # Note: All color operations are of the form: # color OBJECT FOREGROUND BACKGROUND # Color of the current, open, mailbox -# Note: This is a general Mutt option which colors all selected items. +# Note: This is a general NeoMutt option which colors all selected items. color indicator cyan black # Color of the highlighted, but not open, mailbox. color sidebar_highlight black color8 -# Color of the divider separating the Sidebar from Mutt panels +# Color of the divider separating the Sidebar from NeoMutt panels color sidebar_divider color8 black # Color to give mailboxes containing flagged mail color sidebar_flagged red black @@ -14553,11 +14553,11 @@ set skip_quoted_offset = 3 - With zero parameters, Mutt will set the default color for the + With zero parameters, NeoMutt will set the default color for the entire status bar. - With one parameter, Mutt will only color the parts matching the + With one parameter, NeoMutt will only color the parts matching the regex. - With two parameters, Mutt will only color the num'th sub-match of + With two parameters, NeoMutt will only color the num'th sub-match of the regex. @@ -14596,7 +14596,7 @@ set skip_quoted_offset = 3 # the status bar (also when it's used by the index). # For the examples below, set some defaults -set status_format='-%r-Mutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---' +set status_format='-%r-NeoMutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---' set index_format='%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s' set sort=threads set sort_aux=last-date-received @@ -14623,8 +14623,8 @@ color status red default '\[([^]]+)\]' 1 # The '1' refers to the first regex submatch, which is the inner # part in ()s # Highlight the mailbox -color status brightwhite default 'Mutt: ([^ ]+)' 1 -# Search for 'Mutt: ' but only highlight what comes after it +color status brightwhite default 'NeoMutt: ([^ ]+)' 1 +# Search for 'NeoMutt: ' but only highlight what comes after it # vim: syntax=muttrc @@ -14756,7 +14756,7 @@ color status brightwhite default 'Mutt: ([^ ]+)' 1 Support - Since:NeoMutt 2016-09-10, Mutt + Since:NeoMutt 2016-09-10, NeoMutt 1.7.0 @@ -14773,7 +14773,7 @@ color status brightwhite default 'Mutt: ([^ ]+)' 1 Introduction - In Mutt, when you + In NeoMutt, when you delete an email it is first marked deleted. The email isn't really gone until <sync-mailbox>is called. This @@ -14853,7 +14853,7 @@ color status brightwhite default 'Mutt: ([^ ]+)' 1 Muttrc -# Example Mutt config file for the 'trash' feature. +# Example NeoMutt config file for the 'trash' feature. # This feature defines a new 'trash' folder. @@ -14913,16 +14913,16 @@ bind index D purge-message Security Considerations - First of all, Mutt contains no security holes included by intention - but may contain unknown security holes. As a consequence, please run Mutt - only with as few permissions as possible. Especially, do not run Mutt as + First of all, NeoMutt contains no security holes included by intention + but may contain unknown security holes. As a consequence, please run NeoMutt + only with as few permissions as possible. Especially, do not run NeoMutt as the super user. - When configuring Mutt, there're some points to note about secure + When configuring NeoMutt, there're some points to note about secure setups so please read this chapter carefully. Passwords - Although Mutt can be told the various passwords for accounts, + Although NeoMutt can be told the various passwords for accounts, please never store passwords in configuration files. Besides the fact that the system's operator can always read them, you could forget to mask it out when reporting a bug or asking for help via a mailing list. Even @@ -14933,7 +14933,7 @@ bind index D purge-message Temporary Files - Mutt uses many temporary files for viewing messages, verifying + NeoMutt uses many temporary files for viewing messages, verifying digital signatures, etc. As long as being used, these files are visible by other users and maybe even readable in case of misconfiguration. Also, a different location for these files may be desired which can be changed @@ -14947,11 +14947,11 @@ bind index D purge-message Message-Id: headers Message-Id: headers contain a local part that is to be created in - a unique fashion. In order to do so, Mutt will + a unique fashion. In order to do so, NeoMutt will leak some information to the outside world when sending messages: the generation of this header includes a step counter which is increased (and rotated) with every message sent. In a longer running - mutt session, others can make assumptions about your mailing habits + NeoMutt session, others can make assumptions about your mailing habits depending on the number of messages sent. If this is not desired, the header can be manually provided using $edit_headers(though not @@ -14961,7 +14961,7 @@ bind index D purge-message <literal>mailto:</literal>-style Links - As Mutt be can be set up to be the mail client to handle + As NeoMutt be can be set up to be the mail client to handle mailto:style links in websites, there're security considerations, too. Arbitrary header fields can be embedded in these links which could override existing header fields or attach arbitrary @@ -14977,7 +14977,7 @@ bind index D purge-message will send out the user's private gnupg keyring to joe@host if the user doesn't follow the information on screen carefully enough. - To prevent these issues, Mutt by default only accepts the + To prevent these issues, NeoMutt by default only accepts the Subject and Body headers. Allowed headers can be adjusted with the @@ -14992,13 +14992,13 @@ bind index D purge-message External Applications - Mutt in many places has to rely on external applications or for + NeoMutt in many places has to rely on external applications or for convenience supports mechanisms involving external applications. One of these is the mailcap mechanism as defined by RfC1524. Details about a secure use of the mailcap mechanisms is given in . - Besides the mailcap mechanism, Mutt uses a number of other external + Besides the mailcap mechanism, NeoMutt uses a number of other external utilities for operation, for example to provide crypto support, in backtick expansion in configuration files or format string filters. The same security considerations apply for these as for tools involved via @@ -15011,22 +15011,22 @@ bind index D purge-message Reading and Writing Mailboxes - Mutt's performance when reading mailboxes can be improved in two + NeoMutt's performance when reading mailboxes can be improved in two ways: For remote folders (IMAP and POP) as well as folders using - one-file-per message storage (Maildir and MH), Mutt's performance can + one-file-per message storage (Maildir and MH), NeoMutt's performance can be greatly improved using header caching. using a single database per folder. - Mutt provides the + NeoMutt provides the $read_inc and $write_inc variables to specify at which rate to update progress counters. If these values are too low, - Mutt may spend more time on updating the progress counter than it + NeoMutt may spend more time on updating the progress counter than it spends on actually reading/writing folders. For example, when opening a maildir folder with a few thousand messages, the default value for @@ -15047,7 +15047,7 @@ folder-hook ^pop 'set read_inc=1' may greatly differ in size and certain operations are much faster than others, even per-folder settings of the increment variables may not be desirable as they produce either too few or too much progress updates. - Thus, Mutt allows to limit the number of progress updates per second + Thus, NeoMutt allows to limit the number of progress updates per second it'll actually send to the terminal using the $time_inc variable. @@ -15055,18 +15055,18 @@ folder-hook ^pop 'set read_inc=1' Reading Messages from Remote Folders Reading messages from remote folders such as IMAP an POP can be - slow especially for large mailboxes since Mutt only caches a very limited + slow especially for large mailboxes since NeoMutt only caches a very limited number of recently viewed messages (usually 10) per session (so that it will be gone for the next session.) To improve performance and permanently cache whole messages, please - refer to Mutt's so-called + refer to NeoMutt's so-called body caching for details. Searching and Limiting When searching mailboxes either via a search or a limit action, for - some patterns Mutt distinguishes between regular expression and string + some patterns NeoMutt distinguishes between regular expression and string searches. For regular expressions, patterns are prefixed with ~and with =for string searches. @@ -15082,8 +15082,8 @@ folder-hook ^pop 'set read_inc=1' ~Luser@. This is especially true for searching message bodies since a larger amount of input has to be searched. As for regular expressions, a lower case string search pattern - makes Mutt perform a case-insensitive search except for IMAP (because for - IMAP Mutt performs server-side searches which don't support + makes NeoMutt perform a case-insensitive search except for IMAP (because for + IMAP NeoMutt performs server-side searches which don't support case-insensitivity). @@ -15094,7 +15094,7 @@ folder-hook ^pop 'set read_inc=1' Command-Line Options Running - mutt with no arguments will make Mutt attempt to read + neomutt with no arguments will make NeoMutt attempt to read your spool mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. @@ -15126,13 +15126,13 @@ folder-hook ^pop 'set read_inc=1' -d - log debugging output to ~/.muttdebug0 if mutt was compiled + log debugging output to ~/.muttdebug0 if NeoMutt was compiled with +debug; it can range from 1-5 and affects verbosity (a value of 2 is recommended) -D - print the value of all Mutt variables to stdout + print the value of all NeoMutt variables to stdout -D -S @@ -15222,7 +15222,7 @@ folder-hook ^pop 'set read_inc=1' To read messages in a mailbox - mutt + neomutt @@ -15241,7 +15241,7 @@ folder-hook ^pop 'set read_inc=1' To compose a new message - mutt + neomutt @@ -15274,10 +15274,10 @@ folder-hook ^pop 'set read_inc=1' - Mutt also supports a + NeoMutt also supports a batch mode to send prepared messages. Simply redirect input from the file you wish to send. For example, - mutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat + neomutt -s "data set for run #2" professor@bigschool.edu < ~/run2.dat 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 @@ -15302,24 +15302,24 @@ folder-hook ^pop 'set read_inc=1' file will be attached as a MIME part to the message. To attach a single or several files, use --to separate files and recipient addresses: - mutt -a image.png -- some@one.org + neomutt -a image.png -- some@one.org or - mutt -a *.png -- some@one.org + neomutt -a *.png -- some@one.org The -a option must be last in the option list. - In addition to accepting a list of email addresses, Mutt also + In addition to accepting a list of email addresses, NeoMutt also accepts a URL with the mailto:schema as specified in RFC2368. This is useful - when configuring a web browser to launch Mutt when clicking on mailto + when configuring a web browser to launch NeoMutt when clicking on mailto links. - mutt mailto:some@one.org?subject=test&cc=other@one.org + neomutt mailto:some@one.org?subject=test&cc=other@one.org Configuration Commands - The following are the commands understood by Mutt: + The following are the commands understood by NeoMutt: diff --git a/init.h b/init.h index eb683f7be..44857d48d 100644 --- a/init.h +++ b/init.h @@ -120,7 +120,7 @@ struct Option MuttVars[] = { ** encoded in the character set specified by $$config_charset if it ** is \fIset\fP or the current character set otherwise. ** .pp - ** \fBNote:\fP Mutt will not automatically source this file; you must + ** \fBNote:\fP NeoMutt will not automatically source this file; you must ** explicitly use the ``$source'' command for it to be executed in case ** this option points to a dedicated alias file. ** .pp @@ -174,32 +174,32 @@ struct Option MuttVars[] = { { "ascii_chars", DT_BOOL, R_BOTH, OPT_ASCII_CHARS, 0 }, /* ** .pp - ** If \fIset\fP, Mutt will use plain ASCII characters when displaying thread + ** If \fIset\fP, NeoMutt will use plain ASCII characters when displaying thread ** and attachment trees, instead of the default \fIACS\fP characters. */ { "askbcc", DT_BOOL, R_NONE, OPT_ASKBCC, 0 }, /* ** .pp - ** If \fIset\fP, Mutt will prompt you for blind-carbon-copy (Bcc) recipients + ** If \fIset\fP, NeoMutt will prompt you for blind-carbon-copy (Bcc) recipients ** before editing an outgoing message. */ { "askcc", DT_BOOL, R_NONE, OPT_ASKCC, 0 }, /* ** .pp - ** If \fIset\fP, Mutt will prompt you for carbon-copy (Cc) recipients before + ** If \fIset\fP, NeoMutt will prompt you for carbon-copy (Cc) recipients before ** editing the body of an outgoing message. */ #ifdef USE_NNTP { "ask_follow_up", DT_BOOL, R_NONE, OPT_ASK_FOLLOW_UP, 0 }, /* ** .pp - ** If set, Mutt will prompt you for follow-up groups before editing + ** If set, NeoMutt will prompt you for follow-up groups before editing ** the body of an outgoing message. */ { "ask_x_comment_to", DT_BOOL, R_NONE, OPT_ASK_X_COMMENT_TO, 0 }, /* ** .pp - ** If set, Mutt will prompt you for x-comment-to field before editing + ** If set, NeoMutt will prompt you for x-comment-to field before editing ** the body of an outgoing message. */ #endif @@ -224,7 +224,7 @@ struct Option MuttVars[] = { /* ** .pp ** This variable is a colon-separated list of character encoding - ** schemes for text file attachments. Mutt uses this setting to guess + ** schemes for text file attachments. NeoMutt uses this setting to guess ** which encoding files being attached are encoded in to convert them to ** a proper character set given in $$send_charset. ** .pp @@ -286,10 +286,10 @@ struct Option MuttVars[] = { /* ** .pp ** If this variable is \fIunset\fP, when operating (saving, printing, piping, - ** etc) on a list of tagged attachments, Mutt will concatenate the + ** etc) on a list of tagged attachments, NeoMutt will concatenate the ** attachments and will operate on them as a single attachment. The ** $$attach_sep separator is added after each attachment. When \fIset\fP, - ** Mutt will operate on the attachments one by one. + ** NeoMutt will operate on the attachments one by one. */ { "attribution", DT_STRING, R_NONE, UL &Attribution, UL "On %d, %n wrote:" }, /* @@ -306,7 +306,7 @@ struct Option MuttVars[] = { ** accepts for the locale environment variable \fC$$$LC_TIME\fP. ** .pp ** This variable is to allow the attribution date format to be - ** customized by recipient or folder using hooks. By default, Mutt + ** customized by recipient or folder using hooks. By default, NeoMutt ** will use your locale environment, so there is no need to set ** this except to override that default. */ @@ -321,7 +321,7 @@ struct Option MuttVars[] = { { "autoedit", DT_BOOL, R_NONE, OPT_AUTOEDIT, 0 }, /* ** .pp - ** When \fIset\fP along with $$edit_headers, Mutt will skip the initial + ** When \fIset\fP along with $$edit_headers, NeoMutt will skip the initial ** send-menu (prompting for subject and recipients) and allow you to ** immediately begin editing the body of your ** message. The send-menu may still be accessed once you have finished @@ -336,12 +336,12 @@ struct Option MuttVars[] = { { "beep", DT_BOOL, R_NONE, OPT_BEEP, 1 }, /* ** .pp - ** When this variable is \fIset\fP, mutt will beep when an error occurs. + ** When this variable is \fIset\fP, NeoMutt will beep when an error occurs. */ { "beep_new", DT_BOOL, R_NONE, OPT_BEEP_NEW, 0 }, /* ** .pp - ** When this variable is \fIset\fP, mutt will beep whenever it prints a message + ** When this variable is \fIset\fP, NeoMutt will beep whenever it prints a message ** notifying you of new mail. This is independent of the setting of the ** $$beep variable. */ @@ -356,13 +356,13 @@ struct Option MuttVars[] = { { "bounce_delivered", DT_BOOL, R_NONE, OPT_BOUNCE_DELIVERED, 1 }, /* ** .pp - ** When this variable is \fIset\fP, mutt will include Delivered-To headers when + ** When this variable is \fIset\fP, NeoMutt will include Delivered-To headers when ** bouncing messages. Postfix users may wish to \fIunset\fP this variable. */ { "braille_friendly", DT_BOOL, R_NONE, OPT_BRAILLE_FRIENDLY, 0 }, /* ** .pp - ** When this variable is \fIset\fP, mutt will place the cursor at the beginning + ** When this variable is \fIset\fP, NeoMutt will place the cursor at the beginning ** of the current line in menus, even when the $$arrow_cursor variable ** is \fIunset\fP, making it easier for blind persons using Braille displays to ** follow these menus. The option is \fIunset\fP by default because many @@ -372,7 +372,7 @@ struct Option MuttVars[] = { { "catchup_newsgroup", DT_QUAD, R_NONE, OPT_CATCHUP_NEWSGROUP, MUTT_ASKYES }, /* ** .pp - ** If this variable is \fIset\fP, Mutt will mark all articles in newsgroup + ** If this variable is \fIset\fP, NeoMutt will mark all articles in newsgroup ** as read when you quit the newsgroup (catchup newsgroup). */ #endif @@ -403,16 +403,16 @@ struct Option MuttVars[] = { ** Character set your terminal uses to display and enter textual data. ** It is also the fallback for $$send_charset. ** .pp - ** Upon startup Mutt tries to derive this value from environment variables + ** Upon startup NeoMutt tries to derive this value from environment variables ** such as \fC$$$LC_CTYPE\fP or \fC$$$LANG\fP. ** .pp - ** \fBNote:\fP It should only be set in case Mutt isn't able to determine the + ** \fBNote:\fP It should only be set in case NeoMutt isn't able to determine the ** character set used correctly. */ { "check_mbox_size", DT_BOOL, R_NONE, OPT_CHECK_MBOX_SIZE, 0 }, /* ** .pp - ** When this variable is \fIset\fP, mutt will use file size attribute instead of + ** When this variable is \fIset\fP, NeoMutt will use file size attribute instead of ** access time when checking for new mail in mbox and mmdf folders. ** .pp ** This variable is \fIunset\fP by default and should only be enabled when @@ -420,7 +420,7 @@ struct Option MuttVars[] = { ** .pp ** 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 + ** because NeoMutt needs to determine the initial new mail status of such a ** mailbox by performing a fast mailbox scan when it is defined. ** Afterwards the new mail status is tracked by file size changes. */ @@ -430,7 +430,7 @@ struct Option MuttVars[] = { ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style ** mailboxes. ** .pp - ** When \fIset\fP, Mutt will check for new mail delivered while the + ** When \fIset\fP, NeoMutt will check for new mail delivered while the ** mailbox is open. Especially with MH mailboxes, this operation can ** take quite some time since it involves scanning the directory and ** checking each file to see if it has already been looked at. If @@ -440,13 +440,13 @@ struct Option MuttVars[] = { { "collapse_unread", DT_BOOL, R_NONE, OPT_COLLAPSE_UNREAD, 1 }, /* ** .pp - ** When \fIunset\fP, Mutt will not collapse a thread if it contains any + ** When \fIunset\fP, NeoMutt will not collapse a thread if it contains any ** unread messages. */ { "collapse_flagged", DT_BOOL, R_NONE, OPT_COLLAPSE_FLAGGED, 1 }, /* ** .pp - ** When \fIunset\fP, Mutt will not collapse a thread if it contains any + ** When \fIunset\fP, NeoMutt will not collapse a thread if it contains any ** flagged messages. */ { "compose_format", DT_STRING, R_MENU, UL &ComposeFormat, UL "-- NeoMutt: Compose [Approx. msg size: %l Atts: %a]%>-" }, @@ -459,7 +459,7 @@ struct Option MuttVars[] = { ** .dt %a .dd total number of attachments ** .dt %h .dd local hostname ** .dt %l .dd approximate size (in bytes) of the current message - ** .dt %v .dd Mutt version string + ** .dt %v .dd NeoMutt version string ** .de ** .pp ** See the text describing the $$status_format option for more @@ -468,7 +468,7 @@ struct Option MuttVars[] = { { "config_charset", DT_STRING, R_NONE, UL &ConfigCharset, UL 0 }, /* ** .pp - ** When defined, Mutt will recode commands in rc files from this + ** When defined, NeoMutt will recode commands in rc files from this ** encoding to the current character set as specified by $$charset ** and aliases written to $$alias_file from the current character set. ** .pp @@ -482,21 +482,21 @@ struct Option MuttVars[] = { { "confirmappend", DT_BOOL, R_NONE, OPT_CONFIRMAPPEND, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will prompt for confirmation when appending messages to + ** When \fIset\fP, NeoMutt will prompt for confirmation when appending messages to ** an existing mailbox. */ { "confirmcreate", DT_BOOL, R_NONE, OPT_CONFIRMCREATE, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will prompt for confirmation when saving messages to a + ** When \fIset\fP, NeoMutt will prompt for confirmation when saving messages to a ** mailbox which does not yet exist before creating it. */ { "connect_timeout", DT_NUMBER, R_NONE, UL &ConnectTimeout, 30 }, /* ** .pp - ** Causes Mutt to timeout a network connection (for IMAP, POP or SMTP) after this + ** Causes NeoMutt to timeout a network connection (for IMAP, POP or SMTP) after this ** many seconds if the connection is not able to be established. A negative - ** value causes Mutt to wait indefinitely for the connection attempt to succeed. + ** value causes NeoMutt to wait indefinitely for the connection attempt to succeed. */ { "content_type", DT_STRING, R_NONE, UL &ContentType, UL "text/plain" }, /* @@ -514,7 +514,7 @@ struct Option MuttVars[] = { { "crypt_autoencrypt", DT_BOOL, R_NONE, OPT_CRYPT_AUTOENCRYPT, 0 }, /* ** .pp - ** Setting this variable will cause Mutt to always attempt to PGP + ** Setting this variable will cause NeoMutt to always attempt to PGP ** encrypt outgoing messages. This is probably only useful in ** connection to the ``$send-hook'' command. It can be overridden ** by use of the pgp menu, when encryption is not required or @@ -526,7 +526,7 @@ struct Option MuttVars[] = { { "crypt_autopgp", DT_BOOL, R_NONE, OPT_CRYPT_AUTOPGP, 1 }, /* ** .pp - ** This variable controls whether or not mutt may automatically enable + ** This variable controls whether or not NeoMutt may automatically enable ** PGP encryption/signing for messages. See also $$crypt_autoencrypt, ** $$crypt_replyencrypt, ** $$crypt_autosign, $$crypt_replysign and $$smime_is_default. @@ -535,7 +535,7 @@ struct Option MuttVars[] = { { "crypt_autosign", DT_BOOL, R_NONE, OPT_CRYPT_AUTOSIGN, 0 }, /* ** .pp - ** Setting this variable will cause Mutt to always attempt to + ** Setting this variable will cause NeoMutt to always attempt to ** cryptographically sign outgoing messages. This can be overridden ** by use of the pgp menu, when signing is not required or ** encryption is requested as well. If $$smime_is_default is \fIset\fP, @@ -546,7 +546,7 @@ struct Option MuttVars[] = { { "crypt_autosmime", DT_BOOL, R_NONE, OPT_CRYPT_AUTOSMIME, 1 }, /* ** .pp - ** This variable controls whether or not mutt may automatically enable + ** This variable controls whether or not NeoMutt may automatically enable ** S/MIME encryption/signing for messages. See also $$crypt_autoencrypt, ** $$crypt_replyencrypt, ** $$crypt_autosign, $$crypt_replysign and $$smime_is_default. @@ -562,13 +562,13 @@ struct Option MuttVars[] = { { "crypt_opportunistic_encrypt", DT_BOOL, R_NONE, OPT_CRYPT_OPPORTUNISTIC_ENCRYPT, 0 }, /* ** .pp - ** Setting this variable will cause Mutt to automatically enable and + ** Setting this variable will cause NeoMutt to automatically enable and ** disable encryption, based on whether all message recipient keys - ** can be located by Mutt. + ** can be located by NeoMutt. ** .pp - ** When this option is enabled, Mutt will enable/disable encryption + ** When this option is enabled, NeoMutt will enable/disable encryption ** each time the TO, CC, and BCC lists are edited. If - ** $$edit_headers is set, Mutt will also do so each time the message + ** $$edit_headers is set, NeoMutt will also do so each time the message ** is edited. ** .pp ** While this is set, encryption can't be manually enabled/disabled. @@ -607,14 +607,14 @@ struct Option MuttVars[] = { ** which are encrypted. This makes sense in combination with ** $$crypt_replyencrypt, because it allows you to sign all ** messages which are automatically encrypted. This works around - ** the problem noted in $$crypt_replysign, that mutt is not able + ** the problem noted in $$crypt_replysign, that NeoMutt is not able ** to find out whether an encrypted message is also signed. ** (Crypto only) */ { "crypt_timestamp", DT_BOOL, R_NONE, OPT_CRYPT_TIMESTAMP, 1 }, /* ** .pp - ** If \fIset\fP, mutt will include a time stamp in the lines surrounding + ** If \fIset\fP, NeoMutt will include a time stamp in the lines surrounding ** PGP or S/MIME output, so spoofing such lines is more difficult. ** If you are using colors to mark these lines, and rely on these, ** you may \fIunset\fP this setting. @@ -624,7 +624,7 @@ struct Option MuttVars[] = { /* ** .pp ** This variable controls the use of the GPGME-enabled crypto backends. - ** If it is \fIset\fP and Mutt was built with gpgme support, the gpgme code for + ** If it is \fIset\fP and NeoMutt was built with gpgme support, the gpgme code for ** S/MIME and PGP will be used instead of the classic code. Note that ** you need to set this option in .muttrc; it won't have any effect when ** used interactively. @@ -635,7 +635,7 @@ struct Option MuttVars[] = { { "crypt_use_pka", DT_BOOL, R_NONE, OPT_CRYPT_USE_PKA, 0 }, /* ** .pp - ** Controls whether mutt uses PKA + ** Controls whether NeoMutt uses PKA ** (see http://www.g10code.de/docs/pka-intro.de.pdf) during signature ** verification (only supported by the GPGME backend). */ @@ -667,7 +667,7 @@ struct Option MuttVars[] = { /* ** .pp ** The debug level. Note: to debug the early startup process (before the - ** configuration is loaded), ``-d'' mutt argument must be used. + ** configuration is loaded), ``-d'' neomutt argument must be used. ** debug_level/debug_file are ignored until it's read from the configuration ** file. */ @@ -706,14 +706,14 @@ struct Option MuttVars[] = { { "delete_untag", DT_BOOL, R_NONE, OPT_DELETE_UNTAG, 1 }, /* ** .pp - ** If this option is \fIset\fP, mutt will untag messages when marking them + ** If this option is \fIset\fP, NeoMutt will untag messages when marking them ** for deletion. This applies when you either explicitly delete a message, ** or when you save it to another folder. */ { "digest_collapse", DT_BOOL, R_NONE, OPT_DIGEST_COLLAPSE, 1 }, /* ** .pp - ** If this option is \fIset\fP, mutt's received-attachments menu will not show the subparts of + ** If this option is \fIset\fP, NeoMutt's received-attachments menu will not show the subparts of ** individual messages in a multipart/digest. To see these subparts, press ``v'' on that menu. */ { "display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, UL "" }, @@ -765,7 +765,7 @@ struct Option MuttVars[] = { { "duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPT_DUPLICATE_THREADS, 1 }, /* ** .pp - ** This variable controls whether mutt, when $$sort is set to \fIthreads\fP, threads + ** This variable controls whether NeoMutt, when $$sort is set to \fIthreads\fP, threads ** messages with the same Message-Id together. If it is \fIset\fP, it will indicate ** that it thinks they are duplicates of each other with an equals sign ** in the thread tree. @@ -780,7 +780,7 @@ struct Option MuttVars[] = { ** labels passed to your editor will be standard RFC2822 headers, ** (e.g. To:, Cc:, Subject:). Headers added in your editor must ** also be RFC2822 headers, or one of the pseudo headers listed in - ** ``$edit-header''. Mutt will not understand localized header + ** ``$edit-header''. NeoMutt will not understand localized header ** labels, just as it would not when parsing an actual email. ** .pp ** \fBNote\fP that changes made to the References: and Date: headers are @@ -792,7 +792,7 @@ struct Option MuttVars[] = { { "editor", DT_PATH, R_NONE, UL &Editor, 0 }, /* ** .pp - ** This variable specifies which editor is used by mutt. + ** This variable specifies which editor is used by NeoMutt. ** It defaults to the value of the \fC$$$VISUAL\fP, or \fC$$$EDITOR\fP, environment ** variable, or to the string ``vi'' if neither of those are set. ** .pp @@ -816,7 +816,7 @@ struct Option MuttVars[] = { { "encode_from", DT_BOOL, R_NONE, OPT_ENCODE_FROM, 0 }, /* ** .pp - ** When \fIset\fP, mutt will quoted-printable encode messages when + ** When \fIset\fP, NeoMutt will quoted-printable encode messages when ** they contain the string ``From '' (note the trailing space) in the beginning of a line. ** This is useful to avoid the tampering certain mail delivery and transport ** agents tend to do with messages (in order to prevent tools from @@ -919,7 +919,7 @@ struct Option MuttVars[] = { /* ** .pp ** Controls whether or not the ``Mail-Followup-To:'' header field is - ** generated when sending mail. When \fIset\fP, Mutt will generate this + ** generated when sending mail. When \fIset\fP, NeoMutt will generate this ** field when you are replying to a known mailing list, specified with ** the ``$subscribe'' or ``$lists'' commands. ** .pp @@ -949,7 +949,7 @@ struct Option MuttVars[] = { { "force_name", DT_BOOL, R_NONE, OPT_FORCE_NAME, 0 }, /* ** .pp - ** This variable is similar to $$save_name, except that Mutt will + ** This variable is similar to $$save_name, except that NeoMutt will ** store a copy of your outgoing message by the username of the address ** you are sending to even if that mailbox does not exist. ** .pp @@ -1057,23 +1057,23 @@ struct Option MuttVars[] = { ** added in a particular case, use the special value CR (aka ^M) ** for the corresponding character. ** .pp - ** This slightly odd interface is necessitated by mutt's handling of + ** This slightly odd interface is necessitated by NeoMutt's handling of ** string variables; one cannot tell a variable that is unset from one ** that is set to the empty string. */ { "gecos_mask", DT_REGEX, R_NONE, UL &GecosMask, UL "^[^,]*" }, /* ** .pp - ** A regular expression used by mutt to parse the GECOS field of a password + ** A regular expression used by NeoMutt to parse the GECOS field of a password ** entry when expanding the alias. The default value ** will return the string up to the first ``,'' encountered. ** If the GECOS field contains a string like ``lastname, firstname'' then you ** should set it to ``\fC.*\fP''. ** .pp ** This can be useful if you see the following behavior: you address an e-mail - ** to user ID ``stevef'' whose full name is ``Steve Franklin''. If mutt expands + ** to user ID ``stevef'' whose full name is ``Steve Franklin''. If NeoMutt expands ** ``stevef'' to ``"Franklin" stevef@foo.bar'' then you should set the $$gecos_mask to - ** a regular expression that will match the whole name so mutt will expand + ** a regular expression that will match the whole name so NeoMutt will expand ** ``Franklin'' to ``Franklin, Steve''. */ #ifdef USE_NNTP @@ -1110,7 +1110,7 @@ struct Option MuttVars[] = { { "header", DT_BOOL, R_NONE, OPT_HEADER, 0 }, /* ** .pp - ** When \fIset\fP, this variable causes Mutt to include the header + ** When \fIset\fP, this variable causes NeoMutt to include the header ** of the message you are replying to into the edit buffer. ** The $$weed setting applies. */ @@ -1119,7 +1119,7 @@ struct Option MuttVars[] = { /* ** .pp ** This variable points to the header cache database. - ** If pointing to a directory Mutt will contain a header cache + ** If pointing to a directory NeoMutt will contain a header cache ** database file per folder, if pointing to a file that file will ** be a single global header cache. By default it is \fIunset\fP so no header ** caching will be used. @@ -1136,7 +1136,7 @@ struct Option MuttVars[] = { { "header_cache_compress", DT_BOOL, R_NONE, OPT_HEADER_CACHE_COMPRESS, 1 }, /* ** .pp - ** When mutt is compiled with qdbm, tokyocabinet or kyotocabinet + ** When NeoMutt is compiled with qdbm, tokyocabinet or kyotocabinet ** as header cache backend, this option determines whether the ** database will be compressed. Compression results in database ** files roughly being one fifth of the usual diskspace, but the @@ -1149,7 +1149,7 @@ struct Option MuttVars[] = { { "header_cache_pagesize", DT_STRING, R_NONE, UL &HeaderCachePageSize, UL "16384" }, /* ** .pp - ** When mutt is compiled with either gdbm or bdb4 as the header cache backend, + ** When NeoMutt is compiled with either gdbm or bdb4 as the header cache backend, ** this option changes the database page size. Too large or too small ** values can waste space, memory, or CPU time. The default should be more ** or less optimal for most use cases. @@ -1175,14 +1175,14 @@ struct Option MuttVars[] = { ** .pp ** \fBNote:\fP The binding will not be displayed correctly if the ** function is bound to a sequence rather than a single keystroke. Also, - ** the help line may not be updated if a binding is changed while Mutt is + ** the help line may not be updated if a binding is changed while NeoMutt is ** running. Since this variable is primarily aimed at new users, neither ** of these should present a major problem. */ { "hidden_host", DT_BOOL, R_NONE, OPT_HIDDEN_HOST, 0 }, /* ** .pp - ** When \fIset\fP, mutt will skip the host name part of $$hostname variable + ** When \fIset\fP, NeoMutt will skip the host name part of $$hostname variable ** when adding the domain part to addresses. This variable does not ** affect the generation of Message-IDs, and it will not lead to the ** cut-off of first-level domains. @@ -1190,33 +1190,33 @@ struct Option MuttVars[] = { { "hide_limited", DT_BOOL, R_TREE|R_INDEX, OPT_HIDE_LIMITED, 0 }, /* ** .pp - ** When \fIset\fP, mutt will not show the presence of messages that are hidden + ** When \fIset\fP, NeoMutt will not show the presence of messages that are hidden ** by limiting, in the thread tree. */ { "hide_missing", DT_BOOL, R_TREE|R_INDEX, OPT_HIDE_MISSING, 1 }, /* ** .pp - ** When \fIset\fP, mutt will not show the presence of missing messages in the + ** When \fIset\fP, NeoMutt will not show the presence of missing messages in the ** thread tree. */ { "hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPT_HIDE_THREAD_SUBJECT, 1 }, /* ** .pp - ** When \fIset\fP, mutt will not show the subject of messages in the thread + ** When \fIset\fP, NeoMutt will not show the subject of messages in the thread ** tree that have the same subject as their parent or closest previously ** displayed sibling. */ { "hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPT_HIDE_TOP_LIMITED, 0 }, /* ** .pp - ** When \fIset\fP, mutt will not show the presence of messages that are hidden + ** When \fIset\fP, NeoMutt will not show the presence of messages that are hidden ** by limiting, at the top of threads in the thread tree. Note that when ** $$hide_limited is \fIset\fP, this option will have no effect. */ { "hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPT_HIDE_TOP_MISSING, 1 }, /* ** .pp - ** When \fIset\fP, mutt will not show the presence of missing messages at the + ** When \fIset\fP, NeoMutt will not show the presence of missing messages at the ** top of threads in the thread tree. Note that when $$hide_missing is ** \fIset\fP, this option will have no effect. */ @@ -1230,7 +1230,7 @@ struct Option MuttVars[] = { { "history_file", DT_PATH, R_NONE, UL &HistoryFile, UL "~/.mutthistory" }, /* ** .pp - ** The file in which Mutt will save its history. + ** The file in which NeoMutt will save its history. ** .pp ** Also see $$save_history. */ @@ -1244,12 +1244,12 @@ struct Option MuttVars[] = { { "honor_disposition", DT_BOOL, R_NONE, OPT_HONOR_DISPOSITION, 0 }, /* ** .pp - ** When \fIset\fP, Mutt will not display attachments with a + ** When \fIset\fP, NeoMutt will not display attachments with a ** disposition of ``attachment'' inline even if it could ** render the part to plain text. These MIME parts can only ** be viewed from the attachment menu. ** .pp - ** If \fIunset\fP, Mutt will render all MIME parts it can + ** If \fIunset\fP, NeoMutt will render all MIME parts it can ** properly transform to plain text. */ { "honor_followup_to", DT_QUAD, R_NONE, OPT_HONOR_FOLLOWUP_TO, MUTT_YES }, @@ -1261,7 +1261,7 @@ struct Option MuttVars[] = { { "hostname", DT_STRING, R_NONE, UL &Hostname, 0 }, /* ** .pp - ** Specifies the fully-qualified hostname of the system mutt is running on + ** Specifies the fully-qualified hostname of the system NeoMutt is running on ** containing the host's name and the DNS domain it belongs to. It is used ** as the domain part (after ``@'') for local email addresses as well as ** Message-Id headers. @@ -1271,7 +1271,7 @@ struct Option MuttVars[] = { ** domain is then looked up using the \fCgethostname(2)\fP and ** \fCgetaddrinfo(3)\fP functions. If those calls are unable to ** determine the domain, the full value returned by uname is used. - ** Optionally, Mutt can be compiled with a fixed domain name in + ** Optionally, NeoMutt can be compiled with a fixed domain name in ** which case a detected one is not used. ** .pp ** Also see $$use_domain and $$hidden_host. @@ -1280,14 +1280,14 @@ struct Option MuttVars[] = { { "idn_decode", DT_BOOL, R_MENU, OPT_IDN_DECODE, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will show you international domain names decoded. + ** When \fIset\fP, NeoMutt will show you international domain names decoded. ** Note: You can use IDNs for addresses even if this is \fIunset\fP. ** This variable only affects decoding. (IDN only) */ { "idn_encode", DT_BOOL, R_MENU, OPT_IDN_ENCODE, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will encode international domain names using + ** When \fIset\fP, NeoMutt will encode international domain names using ** IDN. Unset this if your SMTP server can handle newer (RFC6531) ** UTF-8 encoded domains. (IDN only) */ @@ -1305,7 +1305,7 @@ struct Option MuttVars[] = { ** Affects the behavior of the \fC\fP function when replying to ** messages from mailing lists (as defined by the ``$subscribe'' or ** ``$lists'' commands). When \fIset\fP, if the ``Reply-To:'' field is - ** set to the same value as the ``To:'' field, Mutt assumes that the + ** set to the same value as the ``To:'' field, NeoMutt assumes that the ** ``Reply-To:'' field was set by the mailing list to automate responses ** to the list, and will ignore this field. To direct a response to the ** mailing list when this option is \fIset\fP, use the \fC$\fP @@ -1324,12 +1324,12 @@ struct Option MuttVars[] = { { "imap_authenticators", DT_STRING, R_NONE, UL &ImapAuthenticators, UL 0 }, /* ** .pp - ** This is a colon-delimited list of authentication methods mutt may - ** attempt to use to log in to an IMAP server, in the order mutt should + ** This is a colon-delimited list of authentication methods NeoMutt may + ** attempt to use to log in to an IMAP server, in the order NeoMutt should ** try them. Authentication methods are either ``login'' or the right ** side of an IMAP ``AUTH=xxx'' capability string, e.g. ``digest-md5'', ``gssapi'' ** or ``cram-md5''. This option is case-insensitive. If it's - ** \fIunset\fP (the default) mutt will try all available methods, + ** \fIunset\fP (the default) NeoMutt will try all available methods, ** in order from most-secure to least-secure. ** .pp ** Example: @@ -1337,14 +1337,14 @@ struct Option MuttVars[] = { ** set imap_authenticators="gssapi:cram-md5:login" ** .te ** .pp - ** \fBNote:\fP Mutt will only fall back to other authentication methods if + ** \fBNote:\fP NeoMutt will only fall back to other authentication methods if ** the previous methods are unavailable. If a method is available but - ** authentication fails, mutt will not connect to the IMAP server. + ** authentication fails, NeoMutt will not connect to the IMAP server. */ { "imap_check_subscribed", DT_BOOL, R_NONE, OPT_IMAP_CHECK_SUBSCRIBED, 0 }, /* ** .pp - ** When \fIset\fP, mutt will fetch the set of subscribed folders from + ** When \fIset\fP, NeoMutt will fetch the set of subscribed folders from ** your server on connection, and add them to the set of mailboxes ** it polls for new mail just as if you had issued individual ``$mailboxes'' ** commands. @@ -1359,7 +1359,7 @@ struct Option MuttVars[] = { { "imap_headers", DT_STRING, R_INDEX, UL &ImapHeaders, UL 0 }, /* ** .pp - ** Mutt requests these header fields in addition to the default headers + ** NeoMutt requests these header fields in addition to the default headers ** (``Date:'', ``From:'', ``Subject:'', ``To:'', ``Cc:'', ``Message-Id:'', ** ``References:'', ``Content-Type:'', ``Content-Description:'', ``In-Reply-To:'', ** ``Reply-To:'', ``Lines:'', ``List-Post:'', ``X-Label:'') from IMAP @@ -1373,18 +1373,18 @@ struct Option MuttVars[] = { { "imap_idle", DT_BOOL, R_NONE, OPT_IMAP_IDLE, 0 }, /* ** .pp - ** When \fIset\fP, mutt will attempt to use the IMAP IDLE extension + ** When \fIset\fP, NeoMutt will attempt to use the IMAP IDLE extension ** to check for new mail in the current mailbox. Some servers ** (dovecot was the inspiration for this option) react badly - ** to mutt's implementation. If your connection seems to freeze + ** to NeoMutt's implementation. If your connection seems to freeze ** up periodically, try unsetting this. */ { "imap_keepalive", DT_NUMBER, R_NONE, UL &ImapKeepalive, 300 }, /* ** .pp - ** This variable specifies the maximum amount of time in seconds that mutt + ** This variable specifies the maximum amount of time in seconds that NeoMutt ** will wait before polling open IMAP connections, to prevent the server - ** from closing them before mutt has finished with them. The default is + ** from closing them before NeoMutt has finished with them. The default is ** well within the RFC-specified minimum amount of time (30 minutes) before ** a server is allowed to do this, but in practice the RFC does get ** violated every now and then. Reduce this number if you find yourself @@ -1407,7 +1407,7 @@ struct Option MuttVars[] = { { "imap_pass", DT_STRING, R_NONE|F_SENSITIVE, UL &ImapPass, UL 0 }, /* ** .pp - ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt will + ** Specifies the password for your IMAP account. If \fIunset\fP, NeoMutt will ** prompt you for your password when you invoke the \fC\fP function ** or try to open an IMAP folder. ** .pp @@ -1418,16 +1418,16 @@ struct Option MuttVars[] = { { "imap_passive", DT_BOOL, R_NONE, OPT_IMAP_PASSIVE, 1 }, /* ** .pp - ** When \fIset\fP, mutt will not open new IMAP connections to check for new - ** mail. Mutt will only check for new mail over existing IMAP + ** When \fIset\fP, NeoMutt will not open new IMAP connections to check for new + ** mail. NeoMutt will only check for new mail over existing IMAP ** connections. This is useful if you don't want to be prompted to - ** user/password pairs on mutt invocation, or if opening the connection + ** user/password pairs on NeoMutt invocation, or if opening the connection ** is slow. */ { "imap_peek", DT_BOOL, R_NONE, OPT_IMAP_PEEK, 1 }, /* ** .pp - ** When \fIset\fP, mutt will avoid implicitly marking your mail as read whenever + ** When \fIset\fP, NeoMutt will avoid implicitly marking your mail as read whenever ** you fetch a message from the server. This is generally a good thing, ** but can make closing an IMAP folder somewhat slower. This option ** exists to appease speed freaks. @@ -1437,7 +1437,7 @@ struct Option MuttVars[] = { ** .pp ** Controls the number of IMAP commands that may be queued up before they ** are sent to the server. A deeper pipeline reduces the amount of time - ** mutt must wait for the server, and can make IMAP servers feel much + ** NeoMutt must wait for the server, and can make IMAP servers feel much ** more responsive. But not all servers correctly handle pipelined commands, ** so if you have problems you might want to try setting this variable to 0. ** .pp @@ -1447,14 +1447,14 @@ struct Option MuttVars[] = { /* ** .pp ** This variable specifies the maximum amount of time in seconds - ** that mutt will wait for a response when polling IMAP connections + ** that NeoMutt will wait for a response when polling IMAP connections ** for new mail, before timing out and closing the connection. Set ** to 0 to disable timing out. */ { "imap_servernoise", DT_BOOL, R_NONE, OPT_IMAP_SERVERNOISE, 1 }, /* ** .pp - ** When \fIset\fP, mutt will display warning messages from the IMAP + ** When \fIset\fP, NeoMutt will display warning messages from the IMAP ** server as error messages. Since these messages are often ** harmless, or generated due to configuration problems on the ** server which are out of the users' hands, you may wish to suppress @@ -1472,9 +1472,9 @@ struct Option MuttVars[] = { { "implicit_autoview", DT_BOOL,R_NONE, OPT_IMPLICIT_AUTOVIEW, 0 }, /* ** .pp - ** If set to ``yes'', mutt will look for a mailcap entry with the + ** If set to ``yes'', NeoMutt will look for a mailcap entry with the ** ``\fCcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have - ** an internal viewer defined for. If such an entry is found, mutt will + ** an internal viewer defined for. If such an entry is found, NeoMutt will ** use the viewer defined in that entry to convert the body part to text ** form. */ @@ -1487,7 +1487,7 @@ struct Option MuttVars[] = { { "include_onlyfirst", DT_BOOL, R_NONE, OPT_INCLUDE_ONLYFIRST, 0 }, /* ** .pp - ** Controls whether or not Mutt includes only the first attachment + ** Controls whether or not NeoMutt includes only the first attachment ** of the message you are replying. */ { "indent_string", DT_STRING, R_NONE, UL &IndentString, UL "> " }, @@ -1515,7 +1515,7 @@ struct Option MuttVars[] = { ** ``Format strings'' are similar to the strings used in the C ** function \fCprintf(3)\fP to format output (see the man page for more details). ** For an explanation of the %? construct, see the $status_format description. - ** The following sequences are defined in Mutt: + ** The following sequences are defined in NeoMutt: ** .dl ** .dt %a .dd address of the author ** .dt %A .dd reply-to address (if present; otherwise: address of author) @@ -1546,7 +1546,7 @@ struct Option MuttVars[] = { ** .dt %M .dd number of hidden messages if the thread is collapsed. ** .dt %N .dd message score ** .dt %n .dd author's real name (or address if missing) - ** .dt %O .dd original save folder where mutt would formerly have + ** .dt %O .dd original save folder where NeoMutt would formerly have ** stashed the message: list name or recipient name ** if not sent to a list ** .dt %P .dd progress indicator for the built-in pager (how much of the file has been displayed) @@ -1611,7 +1611,7 @@ struct Option MuttVars[] = { /* ** .pp ** If set, specifies the program and arguments used to deliver news posted - ** by Mutt. Otherwise, mutt posts article using current connection to + ** by NeoMutt. Otherwise, NeoMutt posts article using current connection to ** news server. The following printf-style sequence is understood: ** .dl ** .dt %a .dd account url @@ -1648,7 +1648,7 @@ struct Option MuttVars[] = { ** they were sourced from. ** .pp ** If both ``$$keywords_legacy'' and - ** ``$$keywords_standard'' are \fCfalse\fP, mutt will save keywords + ** ``$$keywords_standard'' are \fCfalse\fP, NeoMutt will save keywords ** to legacy headers to ensure that it does not lose your labels. */ { "keywords_standard", DT_BOOL, R_NONE, OPT_KEYWORDS_STANDARD, 0 }, @@ -1659,30 +1659,30 @@ struct Option MuttVars[] = { ** legacy headers. ** .pp ** If both ``$$keywords_legacy'' and - ** ``$$keywords_standard'' are \fCfalse\fP, mutt will save keywords + ** ``$$keywords_standard'' are \fCfalse\fP, NeoMutt will save keywords ** to legacy headers to ensure that it does not lose your labels. */ { "mail_check", DT_NUMBER, R_NONE, UL &MailCheck, 5 }, /* ** .pp - ** This variable configures how often (in seconds) mutt should look for + ** This variable configures how often (in seconds) NeoMutt should look for ** new mail. Also see the $$timeout variable. */ { "mail_check_recent",DT_BOOL, R_NONE, OPT_MAIL_CHECK_RECENT, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will only notify you about new mail that has been received - ** since the last time you opened the mailbox. When \fIunset\fP, Mutt will notify you + ** When \fIset\fP, NeoMutt will only notify you about new mail that has been received + ** since the last time you opened the mailbox. When \fIunset\fP, NeoMutt will notify you ** if any new mail exists in the mailbox, regardless of whether you have visited it ** recently. ** .pp - ** When \fI$$mark_old\fP is set, Mutt does not consider the mailbox to contain new + ** When \fI$$mark_old\fP is set, NeoMutt does not consider the mailbox to contain new ** mail if only old messages exist. */ { "mail_check_stats", DT_BOOL, R_NONE, OPT_MAIL_CHECK_STATS, 0 }, /* ** .pp - ** When \fIset\fP, mutt will periodically calculate message + ** When \fIset\fP, NeoMutt will periodically calculate message ** statistics of a mailbox while polling for new mail. It will ** check for unread, flagged, and total message counts. Because ** this operation is more performance intensive, it defaults to @@ -1693,18 +1693,18 @@ struct Option MuttVars[] = { /* ** .pp ** When $$mail_check_stats is \fIset\fP, this variable configures - ** how often (in seconds) mutt will update message counts. + ** how often (in seconds) NeoMutt will update message counts. */ { "mailcap_path", DT_STRING, R_NONE, UL &MailcapPath, 0 }, /* ** .pp ** This variable specifies which files to consult when attempting to - ** display MIME bodies not directly supported by Mutt. + ** display MIME bodies not directly supported by NeoMutt. */ { "mailcap_sanitize", DT_BOOL, R_NONE, OPT_MAILCAP_SANITIZE, 1 }, /* ** .pp - ** If \fIset\fP, mutt will restrict possible characters in mailcap % expandos + ** If \fIset\fP, NeoMutt will restrict possible characters in mailcap % expandos ** to a well-defined set of safe characters. This is the safe setting, ** but we are not sure it doesn't break some more advanced MIME stuff. ** .pp @@ -1715,7 +1715,7 @@ struct Option MuttVars[] = { { "maildir_header_cache_verify", DT_BOOL, R_NONE, OPT_MAILDIR_HEADER_CACHE_VERIFY, 1 }, /* ** .pp - ** Check for Maildir unaware programs other than mutt having modified maildir + ** Check for Maildir unaware programs other than NeoMutt having modified maildir ** files when the header cache is in use. This incurs one \fCstat(2)\fP per ** message every time the folder is opened (which can be very slow for NFS ** folders). @@ -1732,11 +1732,11 @@ struct Option MuttVars[] = { { "maildir_check_cur", DT_BOOL, R_NONE, OPT_MAILDIR_CHECK_CUR, 0 }, /* ** .pp - ** If \fIset\fP, mutt will poll both the new and cur directories of + ** If \fIset\fP, NeoMutt will poll both the new and cur directories of ** a maildir folder for new messages. This might be useful if other ** programs interacting with the folder (e.g. dovecot) are moving new ** messages to the cur directory. Note that setting this option may - ** slow down polling for new messages in large folders, since mutt has + ** slow down polling for new messages in large folders, since NeoMutt has ** to scan all cur messages. */ { "mark_macro_prefix",DT_STRING, R_NONE, UL &MarkMacroPrefix, UL "'" }, @@ -1749,9 +1749,9 @@ struct Option MuttVars[] = { { "mark_old", DT_BOOL, R_BOTH, OPT_MARK_OLD, 1 }, /* ** .pp - ** Controls whether or not mutt marks \fInew\fP \fBunread\fP + ** Controls whether or not NeoMutt marks \fInew\fP \fBunread\fP ** messages as \fIold\fP if you exit a mailbox without reading them. - ** With this option \fIset\fP, the next time you start mutt, the messages + ** With this option \fIset\fP, the next time you start NeoMutt, the messages ** will show up with an ``O'' next to them in the index menu, ** indicating that they are old. */ @@ -1810,7 +1810,7 @@ struct Option MuttVars[] = { { "message_cache_clean", DT_BOOL, R_NONE, OPT_MESSAGE_CACHE_CLEAN, 0 }, /* ** .pp - ** If \fIset\fP, mutt will clean out obsolete entries from the message cache when + ** If \fIset\fP, NeoMutt will clean out obsolete entries from the message cache when ** the mailbox is synchronized. You probably only want to set it ** every once in a while, since it can be a little slow ** (especially for large folders). @@ -1818,11 +1818,11 @@ struct Option MuttVars[] = { { "message_cachedir", DT_PATH, R_NONE, UL &MessageCachedir, 0 }, /* ** .pp - ** Set this to a directory and mutt will cache copies of messages from + ** Set this to a directory and NeoMutt will cache copies of messages from ** your IMAP and POP servers here. You are free to remove entries at any ** time. ** .pp - ** When setting this variable to a directory, mutt needs to fetch every + ** When setting this variable to a directory, NeoMutt needs to fetch every ** remote message only once and can perform regular expression searches ** as fast as for local folders. ** .pp @@ -1842,7 +1842,7 @@ struct Option MuttVars[] = { { "meta_key", DT_BOOL, R_NONE, OPT_META_KEY, 0 }, /* ** .pp - ** If \fIset\fP, forces Mutt to interpret keystrokes with the high bit (bit 8) + ** If \fIset\fP, forces NeoMutt to interpret keystrokes with the high bit (bit 8) ** set as if the user had pressed the Esc key and whatever key remains ** after having the high bit removed. For example, if the key pressed ** has an ASCII value of \fC0xf8\fP, then this is treated as if the user had @@ -1853,13 +1853,13 @@ struct Option MuttVars[] = { { "metoo", DT_BOOL, R_NONE, OPT_METOO, 0 }, /* ** .pp - ** If \fIunset\fP, Mutt will remove your address (see the ``$alternates'' + ** If \fIunset\fP, NeoMutt will remove your address (see the ``$alternates'' ** command) from the list of recipients when replying to a message. */ { "mh_purge", DT_BOOL, R_NONE, OPT_MH_PURGE, 0 }, /* ** .pp - ** When \fIunset\fP, mutt will mimic mh's behavior and rename deleted messages + ** When \fIunset\fP, NeoMutt will mimic mh's behavior and rename deleted messages ** to \fI,\fP in mh folders instead of really deleting ** them. This leaves the message on disk but makes programs reading the folder ** ignore it. If the variable is \fIset\fP, the message files will simply be @@ -1929,9 +1929,9 @@ struct Option MuttVars[] = { ** attachment's extension is not found in the mime.types file. ** .pp ** The string may contain a ``%s'', which will be substituted with the - ** attachment filename. Mutt will add quotes around the string substituted + ** attachment filename. NeoMutt will add quotes around the string substituted ** for ``%s'' automatically according to shell quoting rules, so you should - ** avoid adding your own. If no ``%s'' is found in the string, Mutt will + ** avoid adding your own. If no ``%s'' is found in the string, NeoMutt will ** append the attachment filename to the end of the string. ** .pp ** The command should output a single line containing the @@ -1972,7 +1972,7 @@ struct Option MuttVars[] = { { "move", DT_QUAD, R_NONE, OPT_MOVE, MUTT_NO }, /* ** .pp - ** Controls whether or not Mutt will move read messages + ** Controls whether or not NeoMutt will move read messages ** from your spool mailbox to your $$mbox mailbox, or as a result of ** a ``$mbox-hook'' command. */ @@ -1996,7 +1996,7 @@ struct Option MuttVars[] = { { "new_mail_command", DT_PATH, R_NONE, UL &NewMailCommand, UL NULL }, /* ** .pp - ** If \fIset\fP, Mutt will call this command after a new message is received. + ** If \fIset\fP, NeoMutt will call this command after a new message is received. ** See the $$status_format documentation for the values that can be formatted ** into this command. */ @@ -2004,7 +2004,7 @@ struct Option MuttVars[] = { { "news_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.mutt" }, /* ** .pp - ** This variable pointing to directory where Mutt will save cached news + ** This variable pointing to directory where NeoMutt will save cached news ** articles and headers in. If \fIunset\fP, articles and headers will not be ** saved at all and will be reloaded from the server each time. */ @@ -2041,12 +2041,12 @@ struct Option MuttVars[] = { { "nntp_authenticators", DT_STRING, R_NONE, UL &NntpAuthenticators, UL 0 }, /* ** .pp - ** This is a colon-delimited list of authentication methods mutt may - ** attempt to use to log in to a news server, in the order mutt should + ** This is a colon-delimited list of authentication methods NeoMutt may + ** attempt to use to log in to a news server, in the order NeoMutt should ** try them. Authentication methods are either ``user'' or any ** SASL mechanism, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. ** This option is case-insensitive. If it's \fIunset\fP (the default) - ** mutt will try all available methods, in order from most-secure to + ** NeoMutt will try all available methods, in order from most-secure to ** least-secure. ** .pp ** Example: @@ -2054,9 +2054,9 @@ struct Option MuttVars[] = { ** set nntp_authenticators="digest-md5:user" ** .te ** .pp - ** \fBNote:\fP Mutt will only fall back to other authentication methods if + ** \fBNote:\fP NeoMutt will only fall back to other authentication methods if ** the previous methods are unavailable. If a method is available but - ** authentication fails, mutt will not connect to the IMAP server. + ** authentication fails, NeoMutt will not connect to the IMAP server. */ { "nntp_context", DT_NUMBER, R_NONE, UL &NntpContext, 1000 }, /* @@ -2083,7 +2083,7 @@ struct Option MuttVars[] = { /* ** .pp ** Your login name on the NNTP server. If \fIunset\fP and NNTP server requires - ** authentication, Mutt will prompt you for your account name when you + ** authentication, NeoMutt will prompt you for your account name when you ** connect to news server. */ { "nntp_pass", DT_STRING, R_NONE|F_SENSITIVE, UL &NntpPass, UL "" }, @@ -2095,7 +2095,7 @@ struct Option MuttVars[] = { /* ** .pp ** The time in seconds until any operations on newsgroup except post new - ** article will cause recheck for new news. If set to 0, Mutt will + ** article will cause recheck for new news. If set to 0, NeoMutt will ** recheck newsgroup on each operation in index (stepping, read article, ** etc.). */ @@ -2122,13 +2122,13 @@ struct Option MuttVars[] = { /* ** .pp ** The messages tagged with these tags are excluded and not loaded - ** from notmuch DB to mutt unless specified explicitly. + ** from notmuch DB to NeoMutt unless specified explicitly. */ { "nm_unread_tag", DT_STRING, R_NONE, UL &NmUnreadTag, UL "unread" }, /* ** .pp ** This variable specifies notmuch tag which is used for unread messages. The - ** variable is used to count unread messages in DB only. All other mutt commands + ** variable is used to count unread messages in DB only. All other NeoMutt commands ** use standard (e.g. maildir) flags. */ { "nm_db_limit", DT_NUMBER, R_NONE, UL &NmDbLimit, 0 }, @@ -2144,12 +2144,12 @@ struct Option MuttVars[] = { { "nm_record", DT_BOOL, R_NONE, OPT_NM_RECORD, 0 }, /* ** .pp - ** This variable specifies if the mutt record should indexed by notmuch. + ** This variable specifies if the NeoMutt record should indexed by notmuch. */ { "nm_record_tags", DT_STRING, R_NONE, UL &NmRecordTags, 0 }, /* ** .pp - ** This variable specifies the default tags applied to messages stored to the mutt record. + ** This variable specifies the default tags applied to messages stored to the NeoMutt record. ** When set to 0 this variable disable the window feature. */ { "nm_query_window_duration", DT_NUMBER, R_NONE, UL &NmQueryWindowDuration, 0 }, @@ -2185,7 +2185,7 @@ struct Option MuttVars[] = { ** like to use. ** .pp ** Using an external pager may have some disadvantages: Additional - ** keystrokes are necessary because you can't call mutt functions + ** keystrokes are necessary because you can't call NeoMutt functions ** directly from the pager, and screen resizes cause lines longer than ** the screen width to be badly formatted in the help menu. */ @@ -2194,7 +2194,7 @@ struct Option MuttVars[] = { ** .pp ** This variable controls the number of lines of context that are given ** when displaying the next or previous page in the internal pager. By - ** default, Mutt will display the line after the last one on the screen + ** default, NeoMutt will display the line after the last one on the screen ** at the top of the next page (0 lines of context). ** .pp ** This variable also specifies the amount of context given for search @@ -2234,25 +2234,25 @@ struct Option MuttVars[] = { { "pgp_auto_decode", DT_BOOL, R_NONE, OPT_PGP_AUTO_DECODE, 0 }, /* ** .pp - ** If \fIset\fP, mutt will automatically attempt to decrypt traditional PGP + ** If \fIset\fP, NeoMutt will automatically attempt to decrypt traditional PGP ** messages whenever the user performs an operation which ordinarily would ** result in the contents of the message being operated on. For example, ** if the user displays a pgp-traditional message which has not been manually - ** checked with the \fC$\fP function, mutt will automatically + ** checked with the \fC$\fP function, NeoMutt will automatically ** check the message for traditional pgp. */ { "pgp_create_traditional", DT_SYNONYM, R_NONE, UL "pgp_autoinline", 0 }, { "pgp_autoinline", DT_BOOL, R_NONE, OPT_PGP_AUTOINLINE, 0 }, /* ** .pp - ** This option controls whether Mutt generates old-style inline + ** This option controls whether NeoMutt generates old-style inline ** (traditional) PGP encrypted or signed messages under certain ** circumstances. This can be overridden by use of the pgp menu, ** when inline is not required. The GPGME backend does not support ** this option. ** .pp - ** Note that Mutt might automatically use PGP/MIME for messages - ** which consist of more than a single MIME part. Mutt can be + ** Note that NeoMutt might automatically use PGP/MIME for messages + ** which consist of more than a single MIME part. NeoMutt can be ** configured to ask before sending PGP/MIME messages when inline ** (traditional) would not work. ** .pp @@ -2265,7 +2265,7 @@ struct Option MuttVars[] = { { "pgp_check_exit", DT_BOOL, R_NONE, OPT_PGP_CHECK_EXIT, 1 }, /* ** .pp - ** If \fIset\fP, mutt will check the exit code of the PGP subprocess when + ** If \fIset\fP, NeoMutt will check the exit code of the PGP subprocess when ** signing or encrypting. A non-zero exit code means that the ** subprocess failed. ** (PGP only) @@ -2376,11 +2376,11 @@ struct Option MuttVars[] = { { "pgp_getkeys_command", DT_STRING, R_NONE, UL &PgpGetkeysCommand, 0 }, /* ** .pp - ** This command is invoked whenever Mutt needs to fetch the public key associated with + ** This command is invoked whenever NeoMutt needs to fetch the public key associated with ** an email address. Of the sequences supported by $$pgp_decode_command, %r is ** the only \fCprintf(3)\fP-like sequence used with this format. Note that ** in this case, %r expands to the email address, not the public key ID (the key ID is - ** unknown, which is why Mutt is invoking this command). + ** unknown, which is why NeoMutt is invoking this command). ** (PGP only) */ { "pgp_good_sign", DT_REGEX, R_NONE, UL &PgpGoodSign, 0 }, @@ -2395,7 +2395,7 @@ struct Option MuttVars[] = { { "pgp_ignore_subkeys", DT_BOOL, R_NONE, OPT_PGP_IGNORE_SUBKEYS, 1 }, /* ** .pp - ** Setting this variable will cause Mutt to ignore OpenPGP subkeys. Instead, + ** Setting this variable will cause NeoMutt to ignore OpenPGP subkeys. Instead, ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this ** if you want to play interesting key selection games. ** (PGP only) @@ -2420,10 +2420,10 @@ struct Option MuttVars[] = { ** .te ** .pp ** This format is also generated by the \fCpgpring\fP utility which comes - ** with mutt. + ** with NeoMutt. ** .pp ** Note: gpg's \fCfixed-list-mode\fP option should not be used. It - ** produces a different date format which may result in mutt showing + ** produces a different date format which may result in NeoMutt showing ** incorrect key generation dates. ** .pp ** This is a format string, see the $$pgp_decode_command command for @@ -2440,10 +2440,10 @@ struct Option MuttVars[] = { ** .te ** .pp ** This format is also generated by the \fCpgpring\fP utility which comes - ** with mutt. + ** with NeoMutt. ** .pp ** Note: gpg's \fCfixed-list-mode\fP option should not be used. It - ** produces a different date format which may result in mutt showing + ** produces a different date format which may result in NeoMutt showing ** incorrect key generation dates. ** .pp ** This is a format string, see the $$pgp_decode_command command for @@ -2454,7 +2454,7 @@ struct Option MuttVars[] = { /* ** .pp ** If \fIset\fP, use 64 bit PGP key IDs, if \fIunset\fP use the normal 32 bit key IDs. - ** NOTE: Internally, Mutt has transitioned to using fingerprints (or long key IDs + ** NOTE: Internally, NeoMutt has transitioned to using fingerprints (or long key IDs ** as a fallback). This option now only controls the display of key IDs ** in the key selection menu and a few other places. ** (PGP only) @@ -2462,7 +2462,7 @@ struct Option MuttVars[] = { { "pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGP_MIME_AUTO, MUTT_ASKYES }, /* ** .pp - ** This option controls whether Mutt will prompt you for + ** This option controls whether NeoMutt will prompt you for ** automatically sending a (signed/encrypted) message using ** PGP/MIME when inline (traditional) fails (for any reason). ** .pp @@ -2474,16 +2474,16 @@ struct Option MuttVars[] = { { "pgp_replyinline", DT_BOOL, R_NONE, OPT_PGP_REPLYINLINE, 0 }, /* ** .pp - ** Setting this variable will cause Mutt to always attempt to + ** Setting this variable will cause NeoMutt to always attempt to ** create an inline (traditional) message when replying to a ** message which is PGP encrypted/signed inline. This can be ** overridden by use of the pgp menu, when inline is not ** required. This option does not automatically detect if the - ** (replied-to) message is inline; instead it relies on Mutt + ** (replied-to) message is inline; instead it relies on NeoMutt ** internals for previously checked/flagged messages. ** .pp - ** Note that Mutt might automatically use PGP/MIME for messages - ** which consist of more than a single MIME part. Mutt can be + ** Note that NeoMutt might automatically use PGP/MIME for messages + ** which consist of more than a single MIME part. NeoMutt can be ** configured to ask before sending PGP/MIME messages when inline ** (traditional) would not work. ** .pp @@ -2523,7 +2523,7 @@ struct Option MuttVars[] = { { "pgp_show_unusable", DT_BOOL, R_NONE, OPT_PGP_SHOW_UNUSABLE, 1 }, /* ** .pp - ** If \fIset\fP, mutt will display non-usable keys on the PGP key selection + ** If \fIset\fP, NeoMutt will display non-usable keys on the PGP key selection ** menu. This includes keys which have been revoked, have expired, or ** have been marked as ``disabled'' by the user. ** (PGP only) @@ -2565,7 +2565,7 @@ struct Option MuttVars[] = { { "pgp_strict_enc", DT_BOOL, R_NONE, OPT_PGP_STRICT_ENC, 1 }, /* ** .pp - ** If \fIset\fP, Mutt will automatically encode PGP/MIME signed messages as + ** If \fIset\fP, NeoMutt will automatically encode PGP/MIME signed messages as ** quoted-printable. Please note that unsetting this variable may ** lead to problems with non-verifyable PGP signatures, so only change ** this if you know what you are doing. @@ -2581,9 +2581,9 @@ struct Option MuttVars[] = { { "pgp_use_gpg_agent", DT_BOOL, R_NONE, OPT_PGP_USE_GPG_AGENT, 0 }, /* ** .pp - ** If \fIset\fP, mutt will use a possibly-running \fCgpg-agent(1)\fP process. + ** If \fIset\fP, NeoMutt will use a possibly-running \fCgpg-agent(1)\fP process. ** Note that as of version 2.1, GnuPG no longer exports GPG_AGENT_INFO, so - ** mutt no longer verifies if the agent is running. + ** NeoMutt no longer verifies if the agent is running. ** (PGP only) */ { "pgp_verify_command", DT_STRING, R_NONE, UL &PgpVerifyCommand, 0 }, @@ -2609,7 +2609,7 @@ struct Option MuttVars[] = { /* ** .pp ** Used in connection with the \fC\fP command. When \fIunset\fP, - ** Mutt will pipe the messages without any preprocessing. When \fIset\fP, Mutt + ** NeoMutt will pipe the messages without any preprocessing. When \fIset\fP, NeoMutt ** will weed headers and will attempt to decode the messages ** first. */ @@ -2624,8 +2624,8 @@ struct Option MuttVars[] = { ** .pp ** Used in connection with the \fC\fP function following ** \fC\fP. If this variable is \fIunset\fP, when piping a list of - ** tagged messages Mutt will concatenate the messages and will pipe them - ** all concatenated. When \fIset\fP, Mutt will pipe the messages one by one. + ** tagged messages NeoMutt will concatenate the messages and will pipe them + ** all concatenated. When \fIset\fP, NeoMutt will pipe the messages one by one. ** In both cases the messages are piped in the current sorted order, ** and the $$pipe_sep separator is added after each message. */ @@ -2633,20 +2633,20 @@ struct Option MuttVars[] = { { "pop_auth_try_all", DT_BOOL, R_NONE, OPT_POP_AUTH_TRY_ALL, 1 }, /* ** .pp - ** If \fIset\fP, Mutt will try all available authentication methods. - ** When \fIunset\fP, Mutt will only fall back to other authentication + ** If \fIset\fP, NeoMutt will try all available authentication methods. + ** When \fIunset\fP, NeoMutt will only fall back to other authentication ** methods if the previous methods are unavailable. If a method is - ** available but authentication fails, Mutt will not connect to the POP server. + ** available but authentication fails, NeoMutt will not connect to the POP server. */ { "pop_authenticators", DT_STRING, R_NONE, UL &PopAuthenticators, UL 0 }, /* ** .pp - ** This is a colon-delimited list of authentication methods mutt may - ** attempt to use to log in to an POP server, in the order mutt should + ** This is a colon-delimited list of authentication methods NeoMutt may + ** attempt to use to log in to an POP server, in the order NeoMutt should ** try them. Authentication methods are either ``user'', ``apop'' or any ** SASL mechanism, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. ** This option is case-insensitive. If this option is \fIunset\fP - ** (the default) mutt will try all available methods, in order from + ** (the default) NeoMutt will try all available methods, in order from ** most-secure to least-secure. ** .pp ** Example: @@ -2657,14 +2657,14 @@ struct Option MuttVars[] = { { "pop_checkinterval", DT_NUMBER, R_NONE, UL &PopCheckinterval, 60 }, /* ** .pp - ** This variable configures how often (in seconds) mutt should look for + ** This variable configures how often (in seconds) NeoMutt should look for ** new mail in the currently selected mailbox if it is a POP mailbox. */ { "pop_delete", DT_QUAD, R_NONE, OPT_POP_DELETE, MUTT_ASKNO }, /* ** .pp - ** If \fIset\fP, Mutt will delete successfully downloaded messages from the POP - ** server when using the \fC$\fP function. When \fIunset\fP, Mutt will + ** If \fIset\fP, NeoMutt will delete successfully downloaded messages from the POP + ** server when using the \fC$\fP function. When \fIunset\fP, NeoMutt will ** download messages but also leave them on the POP server. */ { "pop_host", DT_STRING, R_NONE, UL &PopHost, UL "" }, @@ -2681,14 +2681,14 @@ struct Option MuttVars[] = { { "pop_last", DT_BOOL, R_NONE, OPT_POP_LAST, 0 }, /* ** .pp - ** If this variable is \fIset\fP, mutt will try to use the ``\fCLAST\fP'' POP command + ** If this variable is \fIset\fP, NeoMutt will try to use the ``\fCLAST\fP'' POP command ** for retrieving only unread messages from the POP server when using ** the \fC$\fP function. */ { "pop_pass", DT_STRING, R_NONE|F_SENSITIVE, UL &PopPass, UL "" }, /* ** .pp - ** Specifies the password for your POP account. If \fIunset\fP, Mutt will + ** Specifies the password for your POP account. If \fIunset\fP, NeoMutt will ** prompt you for your password when you open a POP mailbox. ** .pp ** \fBWarning\fP: you should only use this option when you are on a @@ -2698,7 +2698,7 @@ struct Option MuttVars[] = { { "pop_reconnect", DT_QUAD, R_NONE, OPT_POP_RECONNECT, MUTT_ASKYES }, /* ** .pp - ** Controls whether or not Mutt will try to reconnect to the POP server if + ** Controls whether or not NeoMutt will try to reconnect to the POP server if ** the connection is lost. */ { "pop_user", DT_STRING, R_NONE|F_SENSITIVE, UL &PopUser, 0 }, @@ -2712,7 +2712,7 @@ struct Option MuttVars[] = { { "post_indent_string",DT_STRING, R_NONE, UL &PostIndentString, UL "" }, /* ** .pp - ** Similar to the $$attribution variable, Mutt will append this + ** Similar to the $$attribution variable, NeoMutt will append this ** string after the inclusion of a message which is being replied to. */ { "post_indent_str", DT_SYNONYM, R_NONE, UL "post_indent_string", 0 }, @@ -2722,7 +2722,7 @@ struct Option MuttVars[] = { { "post_moderated", DT_QUAD, R_NONE, OPT_POST_MODERATED, MUTT_ASKYES }, /* ** .pp - ** If set to \fIyes\fP, Mutt will post article to newsgroup that have + ** If set to \fIyes\fP, NeoMutt will post article to newsgroup that have ** not permissions to posting (e.g. moderated). \fBNote:\fP if news server ** does not support posting to that newsgroup or totally read-only, that ** posting will not have an effect. @@ -2739,8 +2739,8 @@ struct Option MuttVars[] = { { "postponed", DT_PATH, R_INDEX, UL &Postponed, UL "~/postponed" }, /* ** .pp - ** Mutt allows you to indefinitely ``$postpone sending a message'' which - ** you are editing. When you choose to postpone a message, Mutt saves it + ** NeoMutt allows you to indefinitely ``$postpone sending a message'' which + ** you are editing. When you choose to postpone a message, NeoMutt saves it ** in the mailbox specified by this variable. ** .pp ** Also see the $$postpone variable. @@ -2749,7 +2749,7 @@ struct Option MuttVars[] = { /* ** .pp ** When \fIset\fP, postponed messages that are marked for encryption will be - ** self-encrypted. Mutt will first try to encrypt using the value specified + ** self-encrypted. NeoMutt will first try to encrypt using the value specified ** in $$pgp_self_encrypt_as or $$smime_self_encrypt_as. If those are not ** set, it will try the deprecated $$postpone_encrypt_as. ** (Crypto only) @@ -2765,10 +2765,10 @@ struct Option MuttVars[] = { { "preconnect", DT_STRING, R_NONE, UL &Preconnect, UL 0 }, /* ** .pp - ** If \fIset\fP, a shell command to be executed if mutt fails to establish + ** If \fIset\fP, a shell command to be executed if NeoMutt fails to establish ** a connection to the server. This is useful for setting up secure ** connections, e.g. with \fCssh(1)\fP. If the command returns a nonzero - ** status, mutt gives up opening the server. Example: + ** status, NeoMutt gives up opening the server. Example: ** .ts ** set preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net \(rs ** sleep 20 < /dev/null > /dev/null" @@ -2784,7 +2784,7 @@ struct Option MuttVars[] = { { "print", DT_QUAD, R_NONE, OPT_PRINT, MUTT_ASKNO }, /* ** .pp - ** Controls whether or not Mutt really prints messages. + ** Controls whether or not NeoMutt really prints messages. ** This is set to ``ask-no'' by default, because some people ** accidentally hit ``p'' often. */ @@ -2824,19 +2824,19 @@ struct Option MuttVars[] = { /* ** .pp ** If you use an \fIexternal\fP $$pager, setting this variable will - ** cause Mutt to prompt you for a command when the pager exits rather - ** than returning to the index menu. If \fIunset\fP, Mutt will return to the + ** cause NeoMutt to prompt you for a command when the pager exits rather + ** than returning to the index menu. If \fIunset\fP, NeoMutt will return to the ** index menu when the external pager exits. */ { "query_command", DT_PATH, R_NONE, UL &QueryCommand, UL "" }, /* ** .pp - ** This specifies the command Mutt will use to make external address + ** This specifies the command NeoMutt will use to make external address ** queries. The string may contain a ``%s'', which will be substituted - ** with the query string the user types. Mutt will add quotes around the + ** with the query string the user types. NeoMutt will add quotes around the ** string substituted for ``%s'' automatically according to shell quoting ** rules, so you should avoid adding your own. If no ``%s'' is found in - ** the string, Mutt will append the user's query to the end of the string. + ** the string, NeoMutt will append the user's query to the end of the string. ** See ``$query'' for more information. */ { "query_format", DT_STRING, R_NONE, UL &QueryFormat, UL "%4c %t %-25.25a %-25.25n %?e?(%e)?" }, @@ -2863,7 +2863,7 @@ struct Option MuttVars[] = { /* ** .pp ** This variable controls whether ``quit'' and ``exit'' actually quit - ** from mutt. If this option is \fIset\fP, they do quit, if it is \fIunset\fP, they + ** from NeoMutt. If this option is \fIset\fP, they do quit, if it is \fIunset\fP, they ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are ** prompted for confirmation when you try to quit. */ @@ -2885,10 +2885,10 @@ struct Option MuttVars[] = { { "read_inc", DT_NUMBER, R_NONE, UL &ReadInc, 10 }, /* ** .pp - ** If set to a value greater than 0, Mutt will display which message it + ** If set to a value greater than 0, NeoMutt will display which message it ** is currently on when reading a mailbox or when performing search actions ** such as search and limit. The message is printed after - ** this many messages have been read or searched (e.g., if set to 25, Mutt will + ** this many messages have been read or searched (e.g., if set to 25, NeoMutt will ** print a message when it is at message 25, and then again when it gets ** to message 50). This variable is meant to indicate progress when ** reading or searching large mailboxes which may take some time. @@ -2916,7 +2916,7 @@ struct Option MuttVars[] = { { "recall", DT_QUAD, R_NONE, OPT_RECALL, MUTT_ASKYES }, /* ** .pp - ** Controls whether or not Mutt recalls postponed messages + ** Controls whether or not NeoMutt recalls postponed messages ** when composing a new message. ** .pp ** Setting this variable to \fIyes\fP is not generally useful, and thus not @@ -2950,8 +2950,8 @@ struct Option MuttVars[] = { { "reflow_text", DT_BOOL, R_NONE, OPT_REFLOW_TEXT, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will reformat paragraphs in text/plain - ** parts marked format=flowed. If \fIunset\fP, Mutt will display paragraphs + ** When \fIset\fP, NeoMutt will reformat paragraphs in text/plain + ** parts marked format=flowed. If \fIunset\fP, NeoMutt will display paragraphs ** unaltered from how they appear in the message body. See RFC3676 for ** details on the \fIformat=flowed\fP format. ** .pp @@ -2978,7 +2978,7 @@ struct Option MuttVars[] = { { "reply_self", DT_BOOL, R_NONE, OPT_REPLY_SELF, 0 }, /* ** .pp - ** If \fIunset\fP and you are replying to a message sent by you, Mutt will + ** If \fIunset\fP and you are replying to a message sent by you, NeoMutt will ** assume that you want to reply to the recipients of that message rather ** than to yourself. ** .pp @@ -2987,7 +2987,7 @@ struct Option MuttVars[] = { { "reply_to", DT_QUAD, R_NONE, OPT_REPLY_TO, MUTT_ASKYES }, /* ** .pp - ** If \fIset\fP, when replying to a message, Mutt will use the address listed + ** If \fIset\fP, when replying to a message, NeoMutt will use the address listed ** in the Reply-to: header as the recipient of the reply. If \fIunset\fP, ** it will use the address in the From: header field instead. This ** option is useful for reading a mailing list that sets the Reply-To: @@ -3027,9 +3027,9 @@ struct Option MuttVars[] = { ** the command line) will have $$resume_draft_files automatically ** set when they are used as a draft file again. ** .pp - ** The first time a draft file is saved, mutt will add a header, + ** The first time a draft file is saved, NeoMutt will add a header, ** X-Mutt-Resume-Draft to the saved file. The next time the draft - ** file is read in, if mutt sees the header, it will set + ** file is read in, if NeoMutt sees the header, it will set ** $$resume_draft_files. ** .pp ** This option is designed to prevent multiple signatures, @@ -3039,7 +3039,7 @@ struct Option MuttVars[] = { { "reverse_alias", DT_BOOL, R_BOTH, OPT_REVERSE_ALIAS, 0 }, /* ** .pp - ** This variable controls whether or not Mutt will display the ``personal'' + ** This variable controls whether or not NeoMutt will display the ``personal'' ** name from your aliases in the index menu if it finds an alias that ** matches the message's sender. For example, if you have the following ** alias: @@ -3074,15 +3074,15 @@ struct Option MuttVars[] = { /* ** .pp ** This variable fine-tunes the behavior of the $$reverse_name feature. - ** When it is \fIset\fP, mutt will use the address from incoming messages as-is, - ** possibly including eventual real names. When it is \fIunset\fP, mutt will + ** When it is \fIset\fP, NeoMutt will use the address from incoming messages as-is, + ** possibly including eventual real names. When it is \fIunset\fP, NeoMutt will ** override any such real names with the setting of the $$realname variable. */ { "rfc2047_parameters", DT_BOOL, R_NONE, OPT_RFC2047_PARAMETERS, 0 }, /* ** .pp - ** When this variable is \fIset\fP, Mutt will decode RFC2047-encoded MIME - ** parameters. You want to set this variable when mutt suggests you + ** When this variable is \fIset\fP, NeoMutt will decode RFC2047-encoded MIME + ** parameters. You want to set this variable when NeoMutt suggests you ** to save attachments to files named like: ** .ts ** =?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?= @@ -3096,13 +3096,13 @@ struct Option MuttVars[] = { ** wild. ** .pp ** Also note that setting this parameter will \fInot\fP have the effect - ** that mutt \fIgenerates\fP this kind of encoding. Instead, mutt will + ** that NeoMutt \fIgenerates\fP this kind of encoding. Instead, NeoMutt will ** unconditionally use the encoding specified in RFC2231. */ { "save_address", DT_BOOL, R_NONE, OPT_SAVE_ADDRESS, 0 }, /* ** .pp - ** If \fIset\fP, mutt will take the sender's full address when choosing a + ** If \fIset\fP, NeoMutt will take the sender's full address when choosing a ** default folder for saving a mail. If $$save_name or $$force_name ** is \fIset\fP too, the selection of the Fcc folder will be changed as well. */ @@ -3113,7 +3113,7 @@ struct Option MuttVars[] = { ** when closed (the exception is $$spoolfile which is never removed). ** If \fIset\fP, mailboxes are never removed. ** .pp - ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt does not + ** \fBNote:\fP This only applies to mbox and MMDF folders, NeoMutt does not ** delete MH and Maildir directories. */ { "save_history", DT_NUMBER, R_NONE, UL &SaveHistory, 0 }, @@ -3147,8 +3147,8 @@ struct Option MuttVars[] = { /* ** .pp ** Messages which have been assigned a score equal to or lower than the value - ** of this variable are automatically marked for deletion by mutt. Since - ** mutt scores are always greater than or equal to zero, the default setting + ** of this variable are automatically marked for deletion by NeoMutt. Since + ** NeoMutt scores are always greater than or equal to zero, the default setting ** of this variable will never mark a message for deletion. */ { "score_threshold_flag", DT_NUMBER, R_NONE, UL &ScoreThresholdFlag, 9999 }, @@ -3161,8 +3161,8 @@ struct Option MuttVars[] = { /* ** .pp ** Messages which have been assigned a score equal to or lower than the value - ** of this variable are automatically marked as read by mutt. Since - ** mutt scores are always greater than or equal to zero, the default setting + ** of this variable are automatically marked as read by NeoMutt. Since + ** NeoMutt scores are always greater than or equal to zero, the default setting ** of this variable will never mark a message read. */ { "search_context", DT_NUMBER, R_NONE, UL &SearchContext, UL 0 }, @@ -3174,7 +3174,7 @@ struct Option MuttVars[] = { { "send_charset", DT_STRING, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8" }, /* ** .pp - ** A colon-delimited list of character sets for outgoing messages. Mutt will use the + ** A colon-delimited list of character sets for outgoing messages. NeoMutt will use the ** first character set into which the text can be converted exactly. ** If your $$charset is not ``iso-8859-1'' and recipients may not ** understand ``UTF-8'', it is advisable to include in the list an @@ -3183,14 +3183,14 @@ struct Option MuttVars[] = { ** ``iso-8859-1''. ** .pp ** In case the text cannot be converted into one of these exactly, - ** mutt uses $$charset as a fallback. + ** NeoMutt uses $$charset as a fallback. */ { "sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi" }, /* ** .pp - ** Specifies the program and arguments used to deliver mail sent by Mutt. - ** Mutt expects that the specified program interprets additional - ** arguments as recipient addresses. Mutt appends all recipients after + ** Specifies the program and arguments used to deliver mail sent by NeoMutt. + ** NeoMutt expects that the specified program interprets additional + ** arguments as recipient addresses. NeoMutt appends all recipients after ** adding a \fC--\fP delimiter (if not already present). Additional ** flags, such as for $$use_8bitmime, $$use_envelope_from, ** $$dsn_notify, or $$dsn_return will be added before the delimiter. @@ -3201,7 +3201,7 @@ struct Option MuttVars[] = { ** Specifies the number of seconds to wait for the $$sendmail process ** to finish before giving up and putting delivery in the background. ** .pp - ** Mutt interprets the value of this variable as follows: + ** NeoMutt interprets the value of this variable as follows: ** .dl ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing ** .dt 0 .dd wait forever for sendmail to finish @@ -3263,7 +3263,7 @@ struct Option MuttVars[] = { /* ** .pp ** This specifies the characters to be drawn between the sidebar (when - ** visible) and the other Mutt panels. ASCII and Unicode line-drawing + ** visible) and the other NeoMutt panels. ASCII and Unicode line-drawing ** characters are supported. */ { "sidebar_folder_indent", DT_BOOL, R_SIDEBAR, OPT_SIDEBAR_FOLDER_INDENT, 0 }, @@ -3391,7 +3391,7 @@ struct Option MuttVars[] = { ** $$signature. It is \fBstrongly\fP recommended that you not \fIunset\fP ** this variable unless your signature contains just your name. The ** reason for this is because many software packages use ``-- \n'' to - ** detect your signature. For example, Mutt has the ability to highlight + ** detect your signature. For example, NeoMutt has the ability to highlight ** the signature in a different color in the built-in pager. */ { "sig_on_top", DT_BOOL, R_NONE, OPT_SIG_ON_TOP, 0 }, @@ -3413,11 +3413,11 @@ struct Option MuttVars[] = { { "simple_search", DT_STRING, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s" }, /* ** .pp - ** Specifies how Mutt should expand a simple search into a real search + ** Specifies how NeoMutt should expand a simple search into a real search ** pattern. A simple search is one that does not contain any of the ``~'' pattern ** operators. See ``$patterns'' for more information on search patterns. ** .pp - ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt + ** For example, if you simply type ``joe'' at a search or limit prompt, NeoMutt ** will automatically expand it to the value specified by this variable by ** replacing ``%s'' with the supplied string. ** For the default value, ``joe'' would be expanded to: ``~f joe | ~s joe''. @@ -3470,7 +3470,7 @@ struct Option MuttVars[] = { { "smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0 }, /* ** .pp - ** Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle + ** Since for S/MIME there is no pubring/secring as with PGP, NeoMutt has to handle ** storage and retrieval of keys by itself. This is very basic right ** now, and keys and certificates are stored in two different ** directories, both named as the hash-value retrieved from @@ -3509,8 +3509,8 @@ struct Option MuttVars[] = { { "smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPT_SMIME_DECRYPT_USE_DEFAULT_KEY, 1 }, /* ** .pp - ** If \fIset\fP (default) this tells mutt to use the default key for decryption. Otherwise, - ** if managing multiple certificate-key-pairs, mutt will try to use the mailbox-address + ** If \fIset\fP (default) this tells NeoMutt to use the default key for decryption. Otherwise, + ** if managing multiple certificate-key-pairs, NeoMutt will try to use the mailbox-address ** to determine the key to use. It will ask you to supply a key, if it can't find one. ** (S/MIME only) */ @@ -3586,9 +3586,9 @@ struct Option MuttVars[] = { { "smime_is_default", DT_BOOL, R_NONE, OPT_SMIME_IS_DEFAULT, 0 }, /* ** .pp - ** The default behavior of mutt is to use PGP on all auto-sign/encryption + ** The default behavior of NeoMutt is to use PGP on all auto-sign/encryption ** operations. To override and to use OpenSSL instead this must be \fIset\fP. - ** However, this has no effect while replying, since mutt will automatically + ** However, this has no effect while replying, since NeoMutt will automatically ** select the same application that was used to sign/encrypt the original ** message. (Note that this variable can be overridden by unsetting $$crypt_autosmime.) ** (S/MIME only) @@ -3596,7 +3596,7 @@ struct Option MuttVars[] = { { "smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0 }, /* ** .pp - ** Since for S/MIME there is no pubring/secring as with PGP, mutt has to handle + ** Since for S/MIME there is no pubring/secring as with PGP, NeoMutt has to handle ** storage and retrieval of keys/certs by itself. This is very basic right now, ** and stores keys and certificates in two different directories, both ** named as the hash-value retrieved from OpenSSL. There is an index file @@ -3677,15 +3677,15 @@ struct Option MuttVars[] = { { "smtp_authenticators", DT_STRING, R_NONE, UL &SmtpAuthenticators, UL 0 }, /* ** .pp - ** This is a colon-delimited list of authentication methods mutt may - ** attempt to use to log in to an SMTP server, in the order mutt should + ** This is a colon-delimited list of authentication methods NeoMutt may + ** attempt to use to log in to an SMTP server, in the order NeoMutt should ** try them. Authentication methods are any SASL mechanism, e.g. ``plain'', ** ``digest-md5'', ``gssapi'' or ``cram-md5''. ** This option is case-insensitive. If it is ``unset'' - ** (the default) mutt will try all available methods, in order from + ** (the default) NeoMutt will try all available methods, in order from ** most-secure to least-secure. Support for the ``plain'' mechanism is ** bundled; other mechanisms are provided by an external SASL library (look - ** for +USE_SASL in the output of mutt -v). + ** for +USE_SASL in the output of neomutt -v). ** .pp ** Example: ** .ts @@ -3695,9 +3695,9 @@ struct Option MuttVars[] = { { "smtp_pass", DT_STRING, R_NONE|F_SENSITIVE, UL &SmtpPass, UL 0 }, /* ** .pp - ** Specifies the password for your SMTP account. If \fIunset\fP, Mutt will + ** Specifies the password for your SMTP account. If \fIunset\fP, NeoMutt will ** prompt you for your password when you first send mail via SMTP. - ** See $$smtp_url to configure mutt to send mail via SMTP. + ** See $$smtp_url to configure NeoMutt to send mail via SMTP. ** .pp ** \fBWarning\fP: you should only use this option when you are on a ** fairly secure machine, because the superuser can read your muttrc even @@ -3760,7 +3760,7 @@ struct Option MuttVars[] = { ** When sorting by threads, this variable controls how threads are sorted ** in relation to other threads, and how the branches of the thread trees ** are sorted. This can be set to any value that $$sort can, except - ** ``threads'' (in that case, mutt will just use ``date-sent''). You can also + ** ``threads'' (in that case, NeoMutt will just use ``date-sent''). You can also ** specify the ``last-'' prefix in addition to the ``reverse-'' prefix, but ``last-'' ** must come after ``reverse-''. The ``last-'' prefix causes messages to be ** sorted against its siblings by which has the last descendant, using @@ -3820,8 +3820,8 @@ struct Option MuttVars[] = { { "spoolfile", DT_PATH, R_NONE, UL &SpoolFile, 0 }, /* ** .pp - ** If your spool mailbox is in a non-default place where Mutt cannot find - ** it, you can specify its location with this variable. Mutt will + ** If your spool mailbox is in a non-default place where NeoMutt cannot find + ** it, you can specify its location with this variable. NeoMutt will ** initially set this variable to the value of the environment ** variable \fC$$$MAIL\fP or \fC$$$MAILDIR\fP if either is defined. */ @@ -3849,7 +3849,7 @@ struct Option MuttVars[] = { { "ssl_force_tls", DT_BOOL, R_NONE, OPT_SSL_FORCE_TLS, 0 }, /* ** .pp - ** If this variable is \fIset\fP, Mutt will require that all connections + ** If this variable is \fIset\fP, NeoMutt will require that all connections ** to remote servers be encrypted. Furthermore it will attempt to ** negotiate TLS even if the server does not advertise the capability, ** since it would otherwise have to abort the connection anyway. This @@ -3867,8 +3867,8 @@ struct Option MuttVars[] = { { "ssl_starttls", DT_QUAD, R_NONE, OPT_SSL_STARTTLS, MUTT_YES }, /* ** .pp - ** If \fIset\fP (the default), mutt will attempt to use \fCSTARTTLS\fP on servers - ** advertising the capability. When \fIunset\fP, mutt will not attempt to + ** If \fIset\fP (the default), NeoMutt will attempt to use \fCSTARTTLS\fP on servers + ** advertising the capability. When \fIunset\fP, NeoMutt will not attempt to ** use \fCSTARTTLS\fP regardless of the server's capabilities. */ #ifdef USE_SSL_OPENSSL @@ -3909,7 +3909,7 @@ struct Option MuttVars[] = { { "ssl_usesystemcerts", DT_BOOL, R_NONE, OPT_SSL_USESYSTEMCERTS, 1 }, /* ** .pp - ** If set to \fIyes\fP, mutt will use CA certificates in the + ** If set to \fIyes\fP, NeoMutt will use CA certificates in the ** system-wide certificate store when checking if a server certificate ** is signed by a trusted CA. */ @@ -3917,7 +3917,7 @@ struct Option MuttVars[] = { { "ssl_verify_dates", DT_BOOL, R_NONE, OPT_SSL_VERIFY_DATES, 1 }, /* ** .pp - ** If \fIset\fP (the default), mutt will not automatically accept a server + ** If \fIset\fP (the default), NeoMutt will not automatically accept a server ** certificate that is either not yet valid or already expired. You should ** only unset this for particular known hosts, using the ** \fC$\fP function. @@ -3925,7 +3925,7 @@ struct Option MuttVars[] = { { "ssl_verify_host", DT_BOOL, R_NONE, OPT_SSL_VERIFY_HOST, 1 }, /* ** .pp - ** If \fIset\fP (the default), mutt will not automatically accept a server + ** If \fIset\fP (the default), NeoMutt will not automatically accept a server ** certificate whose host name does not match the host used in your folder ** URL. You should only unset this for particular known hosts, using ** the \fC$\fP function. @@ -4004,7 +4004,7 @@ struct Option MuttVars[] = { ** .dt %S .dd current aux sorting method ($$sort_aux) ** .dt %t .dd number of tagged messages * ** .dt %u .dd number of unread messages * - ** .dt %v .dd Mutt version string + ** .dt %v .dd NeoMutt version string ** .dt %V .dd currently active limit pattern, if any * ** .dt %>X .dd right justify the rest of the string and pad with ``X'' ** .dt %|X .dd pad to the end of the line with ``X'' @@ -4046,7 +4046,7 @@ struct Option MuttVars[] = { ** For example, if you want to display the local hostname in lowercase, ** you would use: ``\fC%_h\fP''. ** .pp - ** If you prefix the sequence character with a colon (``:'') character, mutt + ** If you prefix the sequence character with a colon (``:'') character, NeoMutt ** will replace any dots in the expansion by underscores. This might be helpful ** with IMAP folders that don't like dots in folder names. */ @@ -4072,14 +4072,14 @@ struct Option MuttVars[] = { { "suspend", DT_BOOL, R_NONE, OPT_SUSPEND, 1 }, /* ** .pp - ** When \fIunset\fP, mutt won't stop when the user presses the terminal's - ** \fIsusp\fP key, usually ``^Z''. This is useful if you run mutt + ** When \fIunset\fP, NeoMutt won't stop when the user presses the terminal's + ** \fIsusp\fP key, usually ``^Z''. This is useful if you run NeoMutt ** inside an xterm using a command like ``\fCxterm -e mutt\fP''. */ { "text_flowed", DT_BOOL, R_NONE, OPT_TEXT_FLOWED, 0 }, /* ** .pp - ** When \fIset\fP, mutt will generate ``format=flowed'' bodies with a content type + ** When \fIset\fP, NeoMutt will generate ``format=flowed'' bodies with a content type ** of ``\fCtext/plain; format=flowed\fP''. ** This format is easier to handle for some mailing software, and generally ** just looks like ordinary text. To actually make use of this format's @@ -4097,14 +4097,14 @@ struct Option MuttVars[] = { ** .pp ** Users searching attachments or for non-ASCII characters should \fIset\fP ** this value because decoding also includes MIME parsing/decoding and possible - ** character set conversions. Otherwise mutt will attempt to match against the + ** character set conversions. Otherwise NeoMutt will attempt to match against the ** raw message received (for example quoted-printable encoded or with encoded ** headers) which may lead to incorrect search results. */ { "thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPT_THREAD_RECEIVED, 0 }, /* ** .pp - ** When \fIset\fP, mutt uses the date received rather than the date sent + ** When \fIset\fP, NeoMutt uses the date received rather than the date sent ** to thread messages by subject. */ { "tilde", DT_BOOL, R_PAGER, OPT_TILDE, 0 }, @@ -4120,29 +4120,29 @@ struct Option MuttVars[] = { ** variable controls the frequency with which progress updates are ** displayed. It suppresses updates less than $$time_inc milliseconds ** apart. This can improve throughput on systems with slow terminals, - ** or when running mutt on a remote system. + ** or when running NeoMutt on a remote system. ** .pp ** Also see the ``$tuning'' section of the manual for performance considerations. */ { "timeout", DT_NUMBER, R_NONE, UL &Timeout, 600 }, /* ** .pp - ** When Mutt is waiting for user input either idling in menus or - ** in an interactive prompt, Mutt would block until input is + ** When NeoMutt is waiting for user input either idling in menus or + ** in an interactive prompt, NeoMutt would block until input is ** present. Depending on the context, this would prevent certain ** operations from working, like checking for new mail or keeping ** an IMAP connection alive. ** .pp - ** This variable controls how many seconds Mutt will at most wait + ** This variable controls how many seconds NeoMutt will at most wait ** until it aborts waiting for input, performs these operations and ** continues to wait for input. ** .pp - ** A value of zero or less will cause Mutt to never time out. + ** A value of zero or less will cause NeoMutt to never time out. */ { "tmpdir", DT_PATH, R_NONE, UL &Tmpdir, 0 }, /* ** .pp - ** This variable allows you to specify where Mutt will place its + ** This variable allows you to specify where NeoMutt will place its ** temporary files needed for displaying and composing messages. If ** this variable is not set, the environment variable \fC$$$TMPDIR\fP is ** used. If \fC$$$TMPDIR\fP is not set then ``\fC/tmp\fP'' is used. @@ -4201,7 +4201,7 @@ struct Option MuttVars[] = { /* The default must be off to force in the validity checking. */ /* ** .pp - ** Controls whether mutt tries to set the terminal status line and icon name. + ** Controls whether NeoMutt tries to set the terminal status line and icon name. ** Most terminal emulators emulate the status line in the window title. */ { "ts_status_format", DT_STRING, R_BOTH, UL &TSStatusFormat, UL "NeoMutt with %?m?%m messages&no messages?%?n? [%n NEW]?" }, @@ -4215,7 +4215,7 @@ struct Option MuttVars[] = { { "tunnel", DT_STRING, R_NONE, UL &Tunnel, UL 0 }, /* ** .pp - ** Setting this variable will cause mutt to open a pipe to a command + ** Setting this variable will cause NeoMutt to open a pipe to a command ** instead of a raw socket. You may be able to use this to set up ** preauthenticated connections to your IMAP/POP3/SMTP server. Example: ** .ts @@ -4225,7 +4225,7 @@ struct Option MuttVars[] = { ** Note: For this example to work you must be able to log in to the remote ** machine without having to enter a password. ** .pp - ** When set, Mutt uses the tunnel for all remote connections. + ** When set, NeoMutt uses the tunnel for all remote connections. ** Please see ``$account-hook'' in the manual for how to use different ** tunnel commands per connection. */ @@ -4233,13 +4233,13 @@ struct Option MuttVars[] = { { "uncollapse_jump", DT_BOOL, R_NONE, OPT_UNCOLLAPSE_JUMP, 0 }, /* ** .pp - ** When \fIset\fP, Mutt will jump to the next unread message, if any, + ** When \fIset\fP, NeoMutt will jump to the next unread message, if any, ** when the current thread is \fIun\fPcollapsed. */ { "uncollapse_new", DT_BOOL, R_NONE, OPT_UNCOLLAPSE_NEW, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will automatically uncollapse any collapsed thread + ** When \fIset\fP, NeoMutt will automatically uncollapse any collapsed thread ** that receives a new message. When \fIunset\fP, collapsed threads will ** remain collapsed. the presence of the new message will still affect ** index sorting, though. @@ -4251,22 +4251,22 @@ struct Option MuttVars[] = { ** of sendmail which supports the \fC-B8BITMIME\fP flag (such as sendmail ** 8.8.x) or you may not be able to send mail. ** .pp - ** When \fIset\fP, Mutt will invoke $$sendmail with the \fC-B8BITMIME\fP + ** When \fIset\fP, NeoMutt will invoke $$sendmail with the \fC-B8BITMIME\fP ** flag when sending 8-bit messages to enable ESMTP negotiation. */ { "use_domain", DT_BOOL, R_NONE, OPT_USE_DOMAIN, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will qualify all local addresses (ones without the + ** When \fIset\fP, NeoMutt will qualify all local addresses (ones without the ** ``@host'' portion) with the value of $$hostname. If \fIunset\fP, no ** addresses will be qualified. */ { "use_envelope_from", DT_BOOL, R_NONE, OPT_USE_ENVELOPE_FROM, 0 }, /* ** .pp - ** When \fIset\fP, mutt will set the \fIenvelope\fP sender of the message. + ** When \fIset\fP, NeoMutt will set the \fIenvelope\fP sender of the message. ** If $$envelope_from_address is \fIset\fP, it will be used as the sender - ** address. If \fIunset\fP, mutt will attempt to derive the sender from the + ** address. If \fIunset\fP, NeoMutt will attempt to derive the sender from the ** ``From:'' header. ** .pp ** Note that this information is passed to sendmail command using the @@ -4280,7 +4280,7 @@ struct Option MuttVars[] = { { "use_from", DT_BOOL, R_NONE, OPT_USE_FROM, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will generate the ``From:'' header field when + ** When \fIset\fP, NeoMutt will generate the ``From:'' header field when ** sending messages. If \fIunset\fP, no ``From:'' header field will be ** generated unless the user explicitly sets one using the ``$my_hdr'' ** command. @@ -4289,16 +4289,16 @@ struct Option MuttVars[] = { { "use_ipv6", DT_BOOL, R_NONE, OPT_USE_IPV6, 1 }, /* ** .pp - ** When \fIset\fP, Mutt will look for IPv6 addresses of hosts it tries to - ** contact. If this option is \fIunset\fP, Mutt will restrict itself to IPv4 addresses. + ** When \fIset\fP, NeoMutt will look for IPv6 addresses of hosts it tries to + ** contact. If this option is \fIunset\fP, NeoMutt will restrict itself to IPv4 addresses. ** Normally, the default should work. */ #endif /* HAVE_GETADDRINFO */ { "user_agent", DT_BOOL, R_NONE, OPT_USER_AGENT, 1 }, /* ** .pp - ** When \fIset\fP, mutt will add a ``User-Agent:'' header to outgoing - ** messages, indicating which version of mutt was used for composing + ** When \fIset\fP, NeoMutt will add a ``User-Agent:'' header to outgoing + ** messages, indicating which version of NeoMutt was used for composing ** them. */ { "visual", DT_PATH, R_NONE, UL &Visual, 0 }, @@ -4318,14 +4318,14 @@ struct Option MuttVars[] = { { "virtual_spoolfile", DT_BOOL, R_NONE, OPT_VIRTUAL_SPOOLFILE, 0 }, /* ** .pp - ** When \fIset\fP, mutt will use the first defined virtual mailbox (see + ** When \fIset\fP, NeoMutt will use the first defined virtual mailbox (see ** virtual-mailboxes) as a spool file. */ #endif { "wait_key", DT_BOOL, R_NONE, OPT_WAIT_KEY, 1 }, /* ** .pp - ** Controls whether Mutt will ask you to press a key after an external command + ** Controls whether NeoMutt will ask you to press a key after an external command ** has been invoked by these functions: \fC\fP, ** \fC\fP, \fC\fP, \fC\fP, ** and \fC\fP commands. @@ -4334,22 +4334,22 @@ struct Option MuttVars[] = { ** that the corresponding mailcap entry has a \fIneedsterminal\fP flag, ** and the external program is interactive. ** .pp - ** When \fIset\fP, Mutt will always ask for a key. When \fIunset\fP, Mutt will wait + ** When \fIset\fP, NeoMutt will always ask for a key. When \fIunset\fP, NeoMutt will wait ** for a key only if the external command returned a non-zero status. */ { "weed", DT_BOOL, R_NONE, OPT_WEED, 1 }, /* ** .pp - ** When \fIset\fP, mutt will weed headers when displaying, forwarding, + ** When \fIset\fP, NeoMutt will weed headers when displaying, forwarding, ** printing, or replying to messages. */ { "wrap", DT_NUMBER, R_PAGER, UL &Wrap, 0 }, /* ** .pp - ** When set to a positive value, mutt will wrap text at $$wrap characters. - ** When set to a negative value, mutt will wrap text so that there are $$wrap + ** When set to a positive value, NeoMutt will wrap text at $$wrap characters. + ** When set to a negative value, NeoMutt will wrap text so that there are $$wrap ** characters of empty space on the right side of the terminal. Setting it - ** to zero makes mutt wrap at the terminal width. + ** to zero makes NeoMutt wrap at the terminal width. ** .pp ** Also see $$reflow_wrap. */ @@ -4380,10 +4380,10 @@ struct Option MuttVars[] = { { "write_bcc", DT_BOOL, R_NONE, OPT_WRITE_BCC, 1 }, /* ** .pp - ** Controls whether mutt writes out the ``Bcc:'' header when preparing - ** messages to be sent. Exim users may wish to unset this. If mutt + ** Controls whether NeoMutt writes out the ``Bcc:'' header when preparing + ** messages to be sent. Exim users may wish to unset this. If NeoMutt ** is set to deliver directly via SMTP (see $$smtp_url), this - ** option does nothing: mutt will never write out the ``Bcc:'' header + ** option does nothing: NeoMutt will never write out the ``Bcc:'' header ** in this case. */ { "write_inc", DT_NUMBER, R_NONE, UL &WriteInc, 10 }, @@ -4409,7 +4409,7 @@ struct Option MuttVars[] = { /* ** .pp ** The character used to delimit distinct keywords in X-Label headers. - ** X-Label is primarily a Mutt artifact, and the semantics of the field + ** X-Label is primarily a NeoMutt artifact, and the semantics of the field ** were never defined: it is free-form text. However interaction with ** X-Keywords:, X-Mozilla-Keys:, and Keywords: requires that we adopt ** some means of identifying separate keywords within the field. Set @@ -4423,14 +4423,14 @@ struct Option MuttVars[] = { { "x_comment_to", DT_BOOL, R_NONE, OPT_X_COMMENT_TO, 0 }, /* ** .pp - ** If \fIset\fP, Mutt will add ``X-Comment-To:'' field (that contains full + ** If \fIset\fP, NeoMutt will add ``X-Comment-To:'' field (that contains full ** name of original article author) to article that followuped to newsgroup. */ #endif { "collapse_all", DT_BOOL, R_NONE, OPT_COLLAPSE_ALL, 0 }, /* ** .pp - ** When \fIset\fP, Mutt will collapse all threads when entering a folder. + ** When \fIset\fP, NeoMutt will collapse all threads when entering a folder. */ /*--*/ { "pgp_encrypt_self", DT_QUAD, R_NONE, OPT_PGP_ENCRYPT_SELF, MUTT_NO }, diff --git a/opcodes.h b/opcodes.h index de5a7cdb8..98df6b6fb 100644 --- a/opcodes.h +++ b/opcodes.h @@ -94,7 +94,7 @@ _fmt(OP_EDITOR_CAPITALIZE_WORD, N_("capitalize the word")) \ _fmt(OP_EDITOR_DOWNCASE_WORD, N_("convert the word to lower case")) \ _fmt(OP_EDITOR_UPCASE_WORD, N_("convert the word to upper case")) \ - _fmt(OP_ENTER_COMMAND, N_("enter a muttrc command")) \ + _fmt(OP_ENTER_COMMAND, N_("enter a neomuttrc command")) \ _fmt(OP_ENTER_MASK, N_("enter a file mask")) \ _fmt(OP_EXIT, N_("exit this menu")) \ _fmt(OP_FILTER, N_("filter attachment through a shell command")) \ @@ -149,7 +149,7 @@ _fmt(OP_MAIN_SET_FLAG, N_("set a status flag on a message")) \ _fmt(OP_MAIN_SYNC_FOLDER, N_("save changes to mailbox")) \ _fmt(OP_MAIN_TAG_PATTERN, N_("tag messages matching a pattern")) \ - _fmt(OP_MAIN_QUASI_DELETE, N_("delete from mutt, don't touch on disk")) \ + _fmt(OP_MAIN_QUASI_DELETE, N_("delete from NeoMutt, don't touch on disk")) \ _fmt(OP_MAIN_UNDELETE_PATTERN, N_("undelete messages matching a pattern")) \ _fmt(OP_MAIN_UNTAG_PATTERN, N_("untag messages matching a pattern")) \ _fmt(OP_MARK_MSG, N_("create a hotkey macro for the current message")) \ @@ -204,7 +204,7 @@ _fmt(OP_UNDELETE_THREAD, N_("undelete all messages in thread")) \ _fmt(OP_UNDELETE_SUBTHREAD, N_("undelete all messages in subthread")) \ _fmt(OP_UNSUBSCRIBE_PATTERN, N_("unsubscribe from newsgroups matching a pattern")) \ - _fmt(OP_VERSION, N_("show the Mutt version number and date")) \ + _fmt(OP_VERSION, N_("show the NeoMutt version number and date")) \ _fmt(OP_VIEW_ATTACH, N_("view attachment using mailcap entry if necessary")) \ _fmt(OP_VIEW_ATTACHMENTS, N_("show MIME attachments")) \ _fmt(OP_WHAT_KEY, N_("display the keycode for a key press")) \ -- 2.40.0