From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerhard Subject: Example text and source code in agenda - orgmanual.org typo Date: Tue, 08 Apr 2014 18:49:49 +0200 Message-ID: <534428AD.6000108@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52663) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXZDe-0005AO-E0 for emacs-orgmode@gnu.org; Tue, 08 Apr 2014 12:49:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WXZDd-000333-Ah for emacs-orgmode@gnu.org; Tue, 08 Apr 2014 12:49:54 -0400 Received: from mail-ee0-x236.google.com ([2a00:1450:4013:c00::236]:55580) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXZDd-00032i-2x for emacs-orgmode@gnu.org; Tue, 08 Apr 2014 12:49:53 -0400 Received: by mail-ee0-f54.google.com with SMTP id d49so930638eek.27 for ; Tue, 08 Apr 2014 09:49:51 -0700 (PDT) Received: from ?IPv6:2003:6c:6f0c:7301:1d31:3faf:9c0c:5f82? (p2003006C6F0C73011D313FAF9C0C5F82.dip0.t-ipconnect.de. [2003:6c:6f0c:7301:1d31:3faf:9c0c:5f82]) by mx.google.com with ESMTPSA id a4sm5676025eep.12.2014.04.08.09.49.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 09:49:50 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I was searching for the Org Mode Manual as org-mode file, but it was not easy to find. Then I discovered orgmanual.org by TS Dye https://github.com/tsdye/orgmanual. I remembered a thread about it in this mailing list. It seems to be not completely finished, but I like it. My expertise in org-mode is very small and I wanted to play around with that file. So I added it to the agenda. Building the agenda was slow and after a while I found out that it was because of typos in orgmanual.org (org-float instead of diary-float, see below), but also I did not expect dates or code from example text or source code snippets to appear on the agenda, but it does. Can I prevent that dates in example text like #+begin_example <2014-04-08 Di 15:54> #+end_example appear in the agenda? In orgmanual.org I discovered two examples that seem to contain "typos". Probably it was intended to write "diary-float" but it is written "org-float". (In 8.1 Timestamps, deadlines, and scheduling, and in 8.3 Deadlines and scheduling) And in the second it is written (diary-float t 42) instead of (diary-float t 4 2), I guess. Which is also in the original manual (info document) a typo, I guess. After correcting these issues in orgmanual.org, the agenda builds fast and no error messages like "Bad sexp at line 5464 in /home/gsqual/git/orgmanual/orgmanual.org: (org-float t 4 2)" appear any more. Gerhard