Changeset 5472:508ffc26dad2

Timestamp:

2008-08-11 07:42:06 (3 months ago)

Author:

Rocco Rutte <pdmef@…>

Branch:

HEAD

Message:

Prefer "backtick" over "backtic" on comments and docs as it's more common, closes #3101.

Files:

• ChangeLog (modified) (1 diff)
• alias.c (modified) (1 diff)
• doc/manual.xml.head (modified) (1 diff)
• init.c (modified) (1 diff)

ChangeLog

@@ +1 @@
+2008-07-27 10:48 -0400  Aron Griffis  <agriffis@n01se.net>  (3f595d14a285)
+
+        * doc/manual.xml.head: doc: semi-colon needs quoting too
+
+        If semi-colon is bound or macro'd, it needs to be quoted like space,
+        otherwise mutt thinks it's separating commands.
+
+        Signed-off-by: Aron Griffis <agriffis@n01se.net>
+
 2008-07-21 10:24 -0400  Aron Griffis  <agriffis@n01se.net>  (96b0dd25a550)
 

alias.c

@@ -149 +149 @@
  *      From: Michael `/bin/rm -f ~` Elkins <me@mutt.org>
  * and the user creates an alias for this, Mutt could wind up executing
- * the backtics because it writes aliases like
+ * the backticks because it writes aliases like
  *      alias me Michael `/bin/rm -f ~` Elkins <me@mutt.org>
- * To avoid this problem, use a backslash (\) to quote any backtics.  We also
+ * To avoid this problem, use a backslash (\) to quote any backticks.  We also
  * need to quote backslashes as well, since you could defeat the above by
  * doing

doc/manual.xml.head

@@ -1352 +1352 @@
 not interpreted for shell variables or quoting with a backslash [see
 next paragraph]), while double quotes indicate a string for which
-should be evaluated.  For example, backtics are evaluated inside of double
+should be evaluated.  For example, backticks are evaluated inside of double
 quotes, but <emphasis role="bold">not</emphasis> for single quotes.
 </para>

init.c

@@ -237 +237 @@
       if (!pc)
       {
-        dprint (1, (debugfile, "mutt_get_token: mismatched backtics\n"));
+        dprint (1, (debugfile, "mutt_get_token: mismatched backticks\n"));
         return (-1);
       }