From: Nick Dokos <nicholas.dokos@hp.com>
To: emacs-orgmode@gnu.org
Subject: PATCH: typos in documentation
Date: Tue, 24 Mar 2009 15:19:50 -0400 [thread overview]
Message-ID: <13217.1237922390@alphaville.usa.hp.com> (raw)
In researching the answer to Carsten's C-a M - { . } RET
"match TODOs with empty tags" challenge, I went through
a section of the docs and (in addition to enlightening
myself about the meaning of the mysterious runes) I found
a couple of typos. Here's a patch:
From 5d574f62aeea8bfce3ee92fce9aaf0ae4a313710 Mon Sep 17 00:00:00 2001
From: Nick Dokos <nicholas.dokos@hp.com>
Date: Tue, 24 Mar 2009 15:14:50 -0400
Subject: [PATCH] Fix typos.
---
doc/org.texi | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 23fc8af..bdc6987 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6184,7 +6184,7 @@ commands}.
A search string can use Boolean operators @samp{&} for AND and @samp{|} for
OR. @samp{&} binds more strongly than @samp{|}. Parenthesis are currently
not implemented. Each element in the search is either a tag, a regular
-rexpression matching tags, or an expression like @code{PROPERTY OPERATOR
+expression matching tags, or an expression like @code{PROPERTY OPERATOR
VALUE} with a comparison operator, accessing a property value. Each element
may be preceded by @samp{-}, to select against it, and @samp{+} is syntactic
sugar for positive selection. The AND operator @samp{&} is optional when
@@ -6230,7 +6230,7 @@ keyword @samp{WAITING}.
Waiting tasks both at work and at home.
@end table
-When matching properties, a number of different operaors can be used to test
+When matching properties, a number of different operators can be used to test
the value of a property. Here is a complex example:
@example
--
1.5.4.3
reply other threads:[~2009-03-24 19:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13217.1237922390@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).