From: Brian Gough <bjg@network-theory.co.uk>
To: emacs-orgmode@gnu.org
Cc: Barry Gidden <barryg@network-theory.co.uk>,
Brian Gough <bjg@network-theory.co.uk>
Subject: [PATCH] use emdashes when needed
Date: Wed, 8 Dec 2010 21:05:35 +0000 [thread overview]
Message-ID: <1291842341-15199-13-git-send-email-bjg@network-theory.co.uk> (raw)
In-Reply-To: <1291842341-15199-12-git-send-email-bjg@network-theory.co.uk>
---
doc/org.texi | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index fc4b17d..c30378c 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -943,7 +943,7 @@ to the mailing list, in order to minimize the work the mailing list
moderators have to do.}.
For bug reports, please first try to reproduce the bug with the latest
-version of Org available - if you are running an outdated version, it is
+version of Org available---if you are running an outdated version, it is
quite possible that the bug has been fixed already. If the bug persists,
prepare a report and provide as much information as possible, including the
version information of Emacs (@kbd{M-x emacs-version @key{RET}}) and Org
@@ -6150,7 +6150,7 @@ with a prefix arg, finalize and then jump to the captured item.
@orgcmd{C-c C-w,org-capture-refile}
Finalize the capture process by refiling (@pxref{Refiling notes}) the note to
a different place. Please realize that this is a normal refiling command
-that will be executed - so the cursor position at the moment you run this
+that will be executed---so the cursor position at the moment you run this
command is important. If you have inserted a tree with a parent and
children, first move the cursor back to the parent. Any prefix argument
given to this command will be passed on to the @code{org-refile} command.
@@ -7746,7 +7746,7 @@ having to recreate the agenda.@footnote{Custom commands can preset a filter by
binding the variable @code{org-agenda-filter-preset} as an option. This
filter will then be applied to the view and persist as a basic filter through
refreshes and more secondary filtering. The filter is a global property of
-the entire agenda view - in a block agenda, you should only set this in the
+the entire agenda view---in a block agenda, you should only set this in the
global options section, not in the section of an individual block.}
You will be prompted for a tag selection letter; @key{SPC} will mean any tag at
@@ -8024,7 +8024,7 @@ Org will create entries (in org-mode syntax) in that file instead. Most
entries will be stored in a date-based outline tree that will later make it
easy to archive appointments from previous months/years. The tree will be
built under an entry with a @code{DATE_TREE} property, or else with years as
-top-level entries. Emacs will prompt you for the entry text - if you specify
+top-level entries. Emacs will prompt you for the entry text---if you specify
it, the entry will be created in @code{org-agenda-diary-file} without further
interaction. If you directly press @key{RET} at the prompt without typing
text, the target file will be shown in another window for you to finish the
@@ -10038,7 +10038,7 @@ exportable as a beamer presentation. By default, the top-level entries (or
the first level below the selected subtree heading) will be turned into
frames, and the outline structure below this level will become itemize lists.
You can also configure the variable @code{org-beamer-frame-level} to a
-different level - then the hierarchy above frames will produce the sectioning
+different level---then the hierarchy above frames will produce the sectioning
structure of the presentation.
A template for useful in-buffer settings or properties can be inserted into
@@ -12632,7 +12632,7 @@ Source code blocks can be evaluated during export, or when pressing @kbd{C-c
C-c} in the block. The most important thing to realize here is that Org mode
files which contain code snippets are, in a certain sense, like executable
files. So you should accept them and load them into Emacs only from trusted
-sources - just like you would do with a program you install on your computer.
+sources---just like you would do with a program you install on your computer.
Make sure you know what you are doing before customizing the variables
which take off the default security brakes.
@@ -13028,7 +13028,7 @@ indentation shifts by two@footnote{See the variable
stars but the last one are made invisible using the @code{org-hide}
face@footnote{Turning on @code{org-indent-mode} sets
@code{org-hide-leading-stars} to @code{t} and @code{org-adapt-indentation} to
-@code{nil}.} - see below under @samp{2.} for more information on how this
+@code{nil}.}---see below under @samp{2.} for more information on how this
works. You can turn on @code{org-indent-mode} for all files by customizing
the variable @code{org-startup-indented}, or you can turn it on for
individual files using
--
1.6.0.6
next prev parent reply other threads:[~2010-12-08 21:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 21:05 [PATCH] use @result{} instead of --> (looks nicer) Brian Gough
2010-12-08 21:05 ` [PATCH] use macro for @LaTeX name Brian Gough
2010-12-08 21:05 ` [PATCH] make use of the provided @ie and @eg macros to fix the spacing Brian Gough
2010-12-08 21:05 ` [PATCH] fix commas that should be full stops, semicolons or emdashes Brian Gough
2010-12-08 21:05 ` [PATCH] fix plain text that looks better with markup Brian Gough
2010-12-08 21:05 ` [PATCH] use kbd font Brian Gough
2010-12-08 21:05 ` [PATCH] improvements to wording style Brian Gough
2010-12-08 21:05 ` [PATCH] include explanations of how to look up a docstring Brian Gough
2010-12-08 21:05 ` [PATCH] use a full sentence Brian Gough
2010-12-08 21:05 ` [PATCH] tangling is not a widely-known term, describe it as literate programming Brian Gough
2010-12-08 21:05 ` [PATCH] make "time stamps" consistent with timestamps Brian Gough
2010-12-08 21:05 ` [PATCH] make explanation of keyword lines clearer Brian Gough
2010-12-08 21:05 ` Brian Gough [this message]
2010-12-08 21:05 ` [PATCH] put emacs functions in code font Brian Gough
2010-12-08 21:05 ` [PATCH] use code font for example footnote labels Brian Gough
2010-12-08 21:05 ` [PATCH] fix missing word in math formatting section Brian Gough
2010-12-08 21:05 ` [PATCH] typo/grammar fix for .done CSS explanation Brian Gough
2010-12-08 21:05 ` [PATCH] explain how to check the default version of Org Brian Gough
2010-12-08 21:05 ` [PATCH] add index entries Brian Gough
2011-02-01 11:37 ` [Accepted] " Bastien Guerry
2011-02-01 11:36 ` [Accepted] explain how to check the default version of Org Bastien Guerry
2011-02-01 11:34 ` [Accepted] typo/grammar fix for .done CSS explanation Bastien Guerry
2011-02-01 11:33 ` [Accepted] use code font for example footnote labels Bastien Guerry
2011-02-01 11:32 ` [Accepted] put emacs functions in code font Bastien Guerry
2011-02-01 11:29 ` [Accepted] make "time stamps" consistent with timestamps Bastien Guerry
2010-12-09 17:38 ` [PATCH] include explanations of how to look up a docstring Giovanni Ridolfi
2011-01-26 17:33 ` [Accepted] use @result{} instead of --> (looks nicer) Bastien Guerry
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=1291842341-15199-13-git-send-email-bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=barryg@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).