From: Brian Gough <bjg@network-theory.co.uk>
To: emacs-orgmode@gnu.org
Subject: [PATCH] more typos
Date: Tue, 30 Nov 2010 16:44:19 +0000 [thread overview]
Message-ID: <m3tyiy92xo.wl%bjg@network-theory.co.uk> (raw)
From 04038c5a1f22ecf8219343e5ea80d1c7298edb90 Mon Sep 17 00:00:00 2001
From: Brian Gough <bjg@network-theory.co.uk>
Date: Thu, 25 Nov 2010 17:04:22 +0000
Subject: [PATCH] more typos
---
doc/org.texi | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index a0b1b0b..9637fcb 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1557,8 +1557,9 @@ to disable them individually.
@vindex org-cycle-include-plain-lists
Items can be folded just like headline levels. Normally this works only if
the cursor is on a plain list item. For more details, see the variable
-@code{org-cycle-include-plain-lists}. to @code{integrate}, plain list items
-will be treated like low-level. The level of an item is then given by the
+@code{org-cycle-include-plain-lists}. If this variable is set to
+@code{integrate}, plain list items will be treated like low-level
+headlines. The level of an item is then given by the
indentation of the bullet/number. Items are always subordinate to real
headlines, however; the hierarchies remain completely separated.
@orgcmd{M-@key{RET},org-insert-heading}
@@ -9153,7 +9154,7 @@ after the backquote, a help window will pop up.
@kindex '
Pressing the single-quote @kbd{'} followed by another character modifies
the symbol before point with an accent or a font. If you wait more than
-1.5 seconds after the backquote, a help window will pop up. Character
+1.5 seconds after the single-quote, a help window will pop up. Character
modification will work only inside La@TeX{} fragments, outside the quote
is normal.
@end itemize
@@ -11966,7 +11967,7 @@ The @code{:tangle} header argument specifies whether or not the code
block should be included in tangled extraction of source code files.
@itemize @bullet
-@item @code{yes}
+@item @code{tangle}
The code block is exported to a source code file named after the
basename (name w/o extension) of the Org-mode file. E.g., @code{:tangle
yes}.
@@ -12274,7 +12275,7 @@ contents of the standard output stream are returned as text. (In certain
languages this also contains the error output stream; this is an area for
future work.)
-@subsection @code{:session}
+@subsection Session
@subsubsection @code{:results value}
The code is passed to the interpreter running as an interactive Emacs
inferior process. The result returned is the result of the last evaluation
@@ -13844,7 +13845,7 @@ Dynamic blocks are enclosed by a BEGIN-END structure that assigns a name
to the block and can also specify parameters for the function producing
the content of the block.
-#+BEGIN:dynamic block
+@cindex #+BEGIN:dynamic block
@example
#+BEGIN: myblock :parameter1 value1 :parameter2 value2 ...
--
1.6.0.6
reply other threads:[~2010-12-01 4:16 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=m3tyiy92xo.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--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).