From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: PATCH: typos in documentation Date: Tue, 24 Mar 2009 15:19:50 -0400 Message-ID: <13217.1237922390@alphaville.usa.hp.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LmCBk-0002gF-Vm for emacs-orgmode@gnu.org; Tue, 24 Mar 2009 15:21:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LmCBf-0002eI-S5 for emacs-orgmode@gnu.org; Tue, 24 Mar 2009 15:21:28 -0400 Received: from [199.232.76.173] (port=51543 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LmCBf-0002e0-53 for emacs-orgmode@gnu.org; Tue, 24 Mar 2009 15:21:23 -0400 Received: from g1t0028.austin.hp.com ([15.216.28.35]:19417) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LmCBe-0003Ti-QL for emacs-orgmode@gnu.org; Tue, 24 Mar 2009 15:21:22 -0400 Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114]) by g1t0028.austin.hp.com (Postfix) with ESMTP id F03DA1C5D6 for ; Tue, 24 Mar 2009 19:19:51 +0000 (UTC) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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 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