emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Gerhard <gsqual@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Example text and source code in agenda - orgmanual.org typo
Date: Tue, 08 Apr 2014 18:49:49 +0200	[thread overview]
Message-ID: <534428AD.6000108@gmail.com> (raw)

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

next             reply	other threads:[~2014-04-08 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 16:49 Gerhard [this message]
2014-04-08 18:50 ` Example text and source code in agenda - orgmanual.org typo Thomas S. Dye
2014-04-08 19:31   ` Nicolas Goaziou
2014-04-09  7:40     ` Gerhard

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=534428AD.6000108@gmail.com \
    --to=gsqual@gmail.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

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).