docs: rename NeoMutt

flatcap · flatcap · commit 04ae509918a9 · 2025-11-04T19:09:09.000Z
diff --git a/_dev/actions/build.md b/_dev/actions/build.md
@@ -28,8 +28,8 @@ set of unit tests on some of the libraries.
 See, [How to build NeoMutt](https://neomutt.org/dev/build)
 
 **Steps**:
-- Configure Neomutt
-- Build Neomutt
+- Configure NeoMutt
+- Build NeoMutt
 - Build Tests
 - Run Tests
 
diff --git a/_dev/actions/codeql.md b/_dev/actions/codeql.md
@@ -24,8 +24,8 @@ This action performs static code checks.
 See, [How to build NeoMutt](https://neomutt.org/dev/build)
 
 **Steps**:
-- Configure Neomutt
-- Build Neomutt
+- Configure NeoMutt
+- Build NeoMutt
 - Run CodeQL checker
 
 ### Action Details
diff --git a/_dev/actions/coveralls.md b/_dev/actions/coveralls.md
@@ -45,7 +45,7 @@ Learn how the [coverage tests are performed](../analysis/coverage.md)
 See, [How to build NeoMutt](https://neomutt.org/dev/build)
 
 **Steps**:
-- Build Neomutt
+- Build NeoMutt
 - Build Tests
 - Make Coverage
 - Upload results to Coveralls
diff --git a/_dev/build/autosetup.md b/_dev/build/autosetup.md
@@ -21,7 +21,7 @@ according to the system capabilities and the user-selected options."
 
 The website explains in great details the major goals of the project and the
 similarities and differences with Autotools. For the sake of this short
-introduction, I'll summarize the major points, as relevant to Neomutt.
+introduction, I'll summarize the major points, as relevant to NeoMutt.
 
 ### Zero-dependency
 
@@ -94,7 +94,7 @@ take a little getting used to, but it's nothing compared to M4sh.
 **Bottom line**: readable and debuggable configure script, no M4sh quoting
 intricacies, easily extensible.
 
-## Autosetup for Neomutt
+## Autosetup for NeoMutt
 
 In this section, I'll explain a few design decisions I took when porting
 NeoMutt's build system to Autosetup.
diff --git a/_dev/github/repos.md b/_dev/github/repos.md
@@ -35,7 +35,7 @@ This is a list of all the Git repositories in the NeoMutt GitHub Project.
 | [muttrc-mode-el](https://github.com/neomutt/muttrc-mode-el)         | Emacs major mode for editing muttrc                                                                      |
 | [neo-bot](https://github.com/neomutt/neo-bot)                       | IRC bot for #neomutt                                                                                     |
 | [neomutt-contrib](https://github.com/neomutt/neomutt-contrib)       | User Contributions to NeoMutt                                                                            |
-| [neomutt-docs](https://github.com/neomutt/neomutt-docs)             | Documentation for Neomutt                                                                                |
+| [neomutt-docs](https://github.com/neomutt/neomutt-docs)             | Documentation for NeoMutt                                                                                |
 | [neomutt-old](https://github.com/neomutt/neomutt-old)               | Retired branches of NeoMutt                                                                              |
 | [neomutt-test-files](https://github.com/neomutt/neomutt-test-files) | Files and directories for NeoMutt's build test.                                                          |
 | [neomutt](https://github.com/neomutt/neomutt)                       | Teaching an Old Dog New Tricks -- IRC: #neomutt on irc.libera.chat
diff --git a/_dev/roadmap/closed-discussions.md b/_dev/roadmap/closed-discussions.md
@@ -277,7 +277,7 @@ Fork a new process to avoid NeoMutt waiting for an attachment viewer
 
 : **Raised by** @RichiH -- **Result**: desired, too busy
 
-### [#85 Neomutt true colors support][#85]
+### [#85 NeoMutt true colors support][#85]
 
 Allow full 24-bit (rgb) colours in Mutt
 
diff --git a/_distro/arch.md b/_distro/arch.md
@@ -43,7 +43,7 @@ The sections of interest are:
 
 ## Update <a id="update"></a>
 
-Neomutt can be updated together with other packages in the repositories.
+NeoMutt can be updated together with other packages in the repositories.
 
 ```
 pacman -Syu
diff --git a/_includes/header.html b/_includes/header.html
@@ -56,7 +56,7 @@
                   {% if site.github != '' %}
                   <li class="active"><a href="https://github.com/neomutt/neomutt"><img alt="stars" src="https://img.shields.io/github/stars/neomutt/neomutt.svg?style=social" /></a></li>
                   {% endif %}
-                  <li class="active"><a title="Please Sponsor Neomutt" class="nav-link" href="/sponsor"><span class="sponsor">Sponsor ❤️</span></a></li>
+                  <li class="active"><a title="Please Sponsor NeoMutt" class="nav-link" href="/sponsor"><span class="sponsor">Sponsor ❤️</span></a></li>
               </ul>
             </div>
 
diff --git a/_man/neomuttrc.html b/_man/neomuttrc.html
@@ -5863,7 +5863,7 @@ <h2>CONFIGURATION VARIABLES</h2>
           <p>When 
           <span class="emphasis">
             <em>set</em>
-          </span>, Neomutt will display a preview of message in the compose view.</p>
+          </span>, NeoMutt will display a preview of message in the compose view.</p>
         </dd>
         <dt>
           <span class="term">
@@ -5880,7 +5880,7 @@ <h2>CONFIGURATION VARIABLES</h2>
           <p>When 
           <span class="emphasis">
             <em>set</em>
-          </span>, Neomutt will display user-defined headers (set via my_hdr or from editing with edit-headers).</p>
+          </span>, NeoMutt will display user-defined headers (set via my_hdr or from editing with edit-headers).</p>
         </dd>
         <dt>
           <span class="term">
@@ -9424,7 +9424,7 @@ <h2>CONFIGURATION VARIABLES</h2>
             <br />Default:&#160;":" 
             <br /></p>
           </div>
-          <p>Use the value as maildir field delimiter. This is a single-character used to accommodate maildir mailboxes on platforms where `:` is not allowed in a filename. The recommended alternative on such platforms is `;`. Neomutt supports all non-alphanumeric values except for `-`, `.`, `\`, `/`. 
+          <p>Use the value as maildir field delimiter. This is a single-character used to accommodate maildir mailboxes on platforms where `:` is not allowed in a filename. The recommended alternative on such platforms is `;`. NeoMutt supports all non-alphanumeric values except for `-`, `.`, `\`, `/`. 
           <span class="strong">
             <strong>Note:</strong>
           </span>this only applies to maildir-style mailboxes. Setting it will have no effect on other mailbox types.</p>
@@ -10389,7 +10389,7 @@ <h2>CONFIGURATION VARIABLES</h2>
             <br />Default:&#160;"" 
             <br /></p>
           </div>
-          <p>This variable specifies the notmuch tag modifications (addition, removal, toggling) applied to messages added to the Neomutt record when $nm_record is true. See the description of the 
+          <p>This variable specifies the notmuch tag modifications (addition, removal, toggling) applied to messages added to the NeoMutt record when $nm_record is true. See the description of the 
           <span class="emphasis">
             <em>&lt;modify-labels&gt;</em>
           </span>function for the syntax.</p>
@@ -15499,7 +15499,7 @@ <h2>CONFIGURATION VARIABLES</h2>
           <span class="emphasis">
             <em>unset</em>
           </span>, then messages may also be grouped by subject. Unlike threading by "In-Reply-To:" and "References:" header, grouping by subject does not imply a parent-child relation between two messages.</p>
-          <p>To determine the ancestry between messages grouped by subject, Neomutt uses their date: only newer messages can be descendants of older ones.</p>
+          <p>To determine the ancestry between messages grouped by subject, NeoMutt uses their date: only newer messages can be descendants of older ones.</p>
           <p>When $thread_received is 
           <span class="emphasis">
             <em>set</em>
diff --git a/_posts/2018-03-07-news.md b/_posts/2018-03-07-news.md
@@ -3,7 +3,7 @@ author: flatcap
 title: Happy Birthday NeoMutt!
 ---
 
-Happy Birthday Neomutt! 🎉 Two years old today!🎈
+Happy Birthday NeoMutt! 🎉 Two years old today!🎈
 
 A big Thank You ❤️  to everyone who's contributed to NeoMutt.
 We wouldn't be anywhere without you.
diff --git a/_run/release/notify.md b/_run/release/notify.md
@@ -30,11 +30,11 @@ First, tidy some of the Markdown.
 - Replace `**` with `*` (that's enough emphasis for email)
 - Strip out `\` (escaping backslashes)
 
-Mail the Developers: `Neomutt Developers <neomutt-devel@neomutt.org>`
+Mail the Developers: `NeoMutt Developers <neomutt-devel@neomutt.org>`
 
 Next, strip out the sections mentioning Code, Build, Source, Upstream.
 
-Mail the Users: `Neomutt Users <neomutt-users@neomutt.org>`
+Mail the Users: `NeoMutt Users <neomutt-users@neomutt.org>`
 
 ## Downstream Packagers
 
diff --git a/guide/mimesupport.html b/guide/mimesupport.html
@@ -997,7 +997,7 @@ <h3 class="title">
       <code class="literal">multipart/alternative</code> email, otherwise it will be sent as a
       <code class="literal">multipart/mixed</code> email.</p>
       <p>Be aware that when sending a
-      <code class="literal">multipart/alternative</code> email, you have to manually prepare the alternative parts and attach them. However, you can use Neomutt's macro to perform all the operations needed, such that you can compose a plain text email as usual and turn that into a
+      <code class="literal">multipart/alternative</code> email, you have to manually prepare the alternative parts and attach them. However, you can use NeoMutt's macro to perform all the operations needed, such that you can compose a plain text email as usual and turn that into a
       <code class="literal">multipart/alternative</code> email in one single command, with one part being
       <code class="literal">text/plain</code> and the other
       <code class="literal">text/html</code>. An example macro which adds an HTML part to the main body of an email and sends it could be the following:</p>
@@ -1022,7 +1022,7 @@ <h2 class="title" style="clear: both">
         </div>
       </div>
     </div>
-    <p>Neomutt includes supports for reading and writing
+    <p>NeoMutt includes supports for reading and writing
     <code class="literal">multipart/multilingual</code> emails. A
     <code class="literal">multipart/multilingual</code> email is like a
     <code class="literal">multipart/alternative</code> email, except that it comes with parts of different versions of languages instead of appearances. Its format is described by
@@ -1036,14 +1036,14 @@ <h3 class="title">
           </div>
         </div>
       </div>
-      <p>Neomutt uses the
+      <p>NeoMutt uses the
       <code class="literal">$preferred_languages</code> variable to determine which languages to display when displaying a
       <code class="literal">multipart/multilingual</code> email. You can have several preferred languages, separated by
       <code class="literal">,</code></p>
       <pre class="screen">
 set preferred_languages="fr,en,de"
 </pre>
-      <p>Neomutt will try to match these strings again the multilingual header in the received emails "by prefix", e.g.,
+      <p>NeoMutt will try to match these strings again the multilingual header in the received emails "by prefix", e.g.,
       <code class="literal">en</code> will match both
       <code class="literal">en</code> and
       <code class="literal">en_US</code>.</p>
@@ -1094,7 +1094,7 @@ <h3 class="title">
         </ol>
       </div>
       <p>As in
-      <a class="link" href="#compose-alternative-order" title="5.2.&#160;Composing Multipart/Alternative Emails">Composing Multipart/Alternative</a>, you can also use Neomutt's macro and some external scripts to combine this procedure into one.</p>
+      <a class="link" href="#compose-alternative-order" title="5.2.&#160;Composing Multipart/Alternative Emails">Composing Multipart/Alternative</a>, you can also use NeoMutt's macro and some external scripts to combine this procedure into one.</p>
       <p>After grouping the separate parts will be displayed in a tree structure. Attachments can still be edited separately and reordered within the group, but must be ungrouped using the
       <code class="literal">&lt;ungroup-attachment&gt;</code> (#) binding for more advanced editing before tagging and grouping together again as described above.</p>
     </div>
@@ -1108,7 +1108,7 @@ <h2 class="title" style="clear: both">
         </div>
       </div>
     </div>
-    <p>Neomutt doesn't include any special support for reading
+    <p>NeoMutt doesn't include any special support for reading
     <code class="literal">multipart/related</code> emails, but it is possible to write a
     <code class="literal">multipart/related</code> email. A
     <code class="literal">multipart/related</code> attachment is intended for compound objects consisting of several inter-related body parts which are linked together using the
diff --git a/guide/reference.html b/guide/reference.html
@@ -3298,7 +3298,7 @@ <h3 class="title">
       <p>When
       <span class="emphasis">
         <em>set</em>
-      </span>, Neomutt will display a preview of message in the compose view.</p>
+      </span>, NeoMutt will display a preview of message in the compose view.</p>
     </div>
     <div class="sect2">
       <div class="titlepage">
@@ -3316,7 +3316,7 @@ <h3 class="title">
       <p>When
       <span class="emphasis">
         <em>set</em>
-      </span>, Neomutt will display user-defined headers (set via
+      </span>, NeoMutt will display user-defined headers (set via
       <a class="link" href="configuration.html#my-hdr" title="17.&#160;User-Defined Headers">my_hdr</a> or from editing with edit-headers).</p>
     </div>
     <div class="sect2">
@@ -7214,7 +7214,7 @@ <h3 class="title">
           <code class="literal">:</code>
         </span>”</span></p>
       </div>
-      <p>Use the value as maildir field delimiter. This is a single-character used to accommodate maildir mailboxes on platforms where `:` is not allowed in a filename. The recommended alternative on such platforms is `;`. Neomutt supports all non-alphanumeric values except for `-`, `.`, `\`, `/`.
+      <p>Use the value as maildir field delimiter. This is a single-character used to accommodate maildir mailboxes on platforms where `:` is not allowed in a filename. The recommended alternative on such platforms is `;`. NeoMutt supports all non-alphanumeric values except for `-`, `.`, `\`, `/`.
       <span class="bold">
         <strong>Note:</strong>
       </span>this only applies to maildir-style mailboxes. Setting it will have no effect on other mailbox types.</p>
@@ -8307,7 +8307,7 @@ <h3 class="title">
         <p>Type:&#160;string
         <br />Default:&#160;(empty)</p>
       </div>
-      <p>This variable specifies the notmuch tag modifications (addition, removal, toggling) applied to messages added to the Neomutt record when
+      <p>This variable specifies the notmuch tag modifications (addition, removal, toggling) applied to messages added to the NeoMutt record when
       <a class="link" href="#nm-record" title="3.287.&#160;nm_record">$nm_record</a> is true. See the description of the
       <code class="literal">&lt;modify-labels&gt;</code> function for the syntax.</p>
     </div>
@@ -13818,7 +13818,7 @@ <h3 class="title">
       <span class="emphasis">
         <em>unset</em>
       </span>, then messages may also be grouped by subject. Unlike threading by "In-Reply-To:" and "References:" header, grouping by subject does not imply a parent-child relation between two messages.</p>
-      <p>To determine the ancestry between messages grouped by subject, Neomutt uses their date: only newer messages can be descendants of older ones.</p>
+      <p>To determine the ancestry between messages grouped by subject, NeoMutt uses their date: only newer messages can be descendants of older ones.</p>
       <p>When
       <a class="link" href="#thread-received" title="3.518.&#160;thread_received">$thread_received</a> is
       <span class="emphasis">
