summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDirk-Jan C. Binnema <djcb@djcbsoftware.nl>2025-05-04 16:23:53 +0300
committerGitHub <noreply@github.com>2025-05-04 16:23:53 +0300
commit3a506f4065ce2f6101dfbcb879b32e843e87d2ea (patch)
tree612f5f3a307dd1cb3c25f34dd8ee2e063f6b9a11
parent998a6448d502fcdc022816d719f730eb7d7d044e (diff)
parent3dd922ff6ca10dcc9ff2cd12f57b1134f89c4ff3 (diff)
Merge pull request #2828 from a3a3el/bugfix/man-page-quoting-fixes/v1
man: fix some single-quoted strings
-rw-r--r--man/mu-query.7.org6
1 files changed, 3 insertions, 3 deletions
diff --git a/man/mu-query.7.org b/man/mu-query.7.org
index 694a56e..a561793 100644
--- a/man/mu-query.7.org
+++ b/man/mu-query.7.org
@@ -23,7 +23,7 @@ See the *ANALYZING QUERIES* section for further details.
*NOTE:* if you use queries on the command-line (say, for *mu find*), you need to
quote any characters that would otherwise be interpreted by the shell, such as
-'"', '*', '(' and ')'. The details are shell-specific. In case of doubt, the
+`"', `*', `(' and `)'. The details are shell-specific. In case of doubt, the
*--analyze* option can be useful.
* TERMS
@@ -136,7 +136,7 @@ $ mu find "hello*"
#+end_example
Quoting the "hello*" is recommended; some shells (but not all) would otherwise
-expand the '*' to all files in the current directory.
+expand the `*' to all files in the current directory.
* REGULAR EXPRESSIONS
@@ -165,7 +165,7 @@ whitespace, so the search for a message with subject "hello world", you can writ
#+begin_example
mu find 'subject:/hello\\040world/'
#+end_example
-(with the \040 specifying a space in the regular expression, and and extra '\'
+(with the \\040 specifying a space in the regular expression, and and extra `\\'
to escape it). In many cases,
#+begin_example
mu find 'subject:/hello.world/'