fix whitespace

diff --git a/auto.def b/auto.def
index f31567710a6ebf98bf68519d6fa58a7873257e8b..95e55c05bb144d7d61093142d3214684d823ca6a 100644 (file)
--- a/auto.def
+++ b/auto.def
@@ -465,7 +465,7 @@ if {[get-define want-gpgme]} {
       user-error "Could not derive --cflags from $gpg_error_config"
     }
     define-append CFLAGS $res
-    
+
     # LIBS
     if {[catch {exec-with-stderr $gpg_error_config --libs} res err]} {
       user-error "Could not derive --libs from $gpg_error_config"

diff --git a/init.h b/init.h
index 752450523a2dcd90f91a6dd036fa793e67259cb9..d76e143cb82b542eb7babcbdc0973d71f8203bd4 100644 (file)
--- a/init.h
+++ b/init.h
@@ -1030,37 +1030,37 @@ struct ConfigDef MuttVars[] = {
   */
   { "external_search_command", DT_STRING|DT_COMMAND, &C_ExternalSearchCommand, 0 },
   /*
-   ** .pp
-   ** If set, contains the name of the external program used by "~I" patterns.
-   ** This will usually be a wrapper script around mairix, mu, or similar
-   ** indexers other than notmuch (for which there is optional special support).
-   ** .pp
-   ** Here is an example how it works.  Let's assume $$external_search_command
-   ** is set to "mairix_filter", and mairix_filter is a script which
-   ** runs the old but well loved mairix indexer with the arguments
-   ** given to mairix_filter, in the "raw" mode of mairix, producing
-   ** on the standard output a list of Message-IDs, one per line.
-   ** .pp
-   ** If possible, it also filters down the results coming from mairix
-   ** such that only messages in the current folder remain.  It can do
-   ** this because it gets a hidden first argument which is the path
-   ** to the folder.
-   ** (This can be the type of clean and simple script called a \fIone-liner\fP.)
-   ** .pp
-   ** Now if NeoMutt gets a limit or tag command followed by the pattern
-   ** "~I '-t s:bleeping='", mairix_filter runs mairix with the
-   ** arguments from inside the quotes (the quotes are needed because
-   ** of the space after "-t"), mairix finds all messages with
-   ** "bleeping" in the Subject plus all messages sharing threads
-   ** with these and outputs their file names, and mairix_filter
-   ** translates the file names into Message-IDs.  Finally, NeoMutt
-   ** reads the Message-IDs and targets the matching messages with the
-   ** command given to it.
-   ** .pp
-   ** You, the user, still have to rewrite the mairix_filter script to
-   ** match the behavior of your indexer, but this should help users
-   ** of indexers other than notmuch to integrate them cleanly with NeoMutt.
-   */
+  ** .pp
+  ** If set, contains the name of the external program used by "~I" patterns.
+  ** This will usually be a wrapper script around mairix, mu, or similar
+  ** indexers other than notmuch (for which there is optional special support).
+  ** .pp
+  ** Here is an example how it works.  Let's assume $$external_search_command
+  ** is set to "mairix_filter", and mairix_filter is a script which
+  ** runs the old but well loved mairix indexer with the arguments
+  ** given to mairix_filter, in the "raw" mode of mairix, producing
+  ** on the standard output a list of Message-IDs, one per line.
+  ** .pp
+  ** If possible, it also filters down the results coming from mairix
+  ** such that only messages in the current folder remain.  It can do
+  ** this because it gets a hidden first argument which is the path
+  ** to the folder.
+  ** (This can be the type of clean and simple script called a \fIone-liner\fP.)
+  ** .pp
+  ** Now if NeoMutt gets a limit or tag command followed by the pattern
+  ** "~I '-t s:bleeping='", mairix_filter runs mairix with the
+  ** arguments from inside the quotes (the quotes are needed because
+  ** of the space after "-t"), mairix finds all messages with
+  ** "bleeping" in the Subject plus all messages sharing threads
+  ** with these and outputs their file names, and mairix_filter
+  ** translates the file names into Message-IDs.  Finally, NeoMutt
+  ** reads the Message-IDs and targets the matching messages with the
+  ** command given to it.
+  ** .pp
+  ** You, the user, still have to rewrite the mairix_filter script to
+  ** match the behavior of your indexer, but this should help users
+  ** of indexers other than notmuch to integrate them cleanly with NeoMutt.
+  */
   { "fast_reply", DT_BOOL, &C_FastReply, false },
   /*
   ** .pp