From: Patrick Daly <ichaleynbin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Tutorial Typos
Date: Mon, 15 Jul 2013 20:28:59 -0400 [thread overview]
Message-ID: <CAE2UF2xFL2_eWNwLmuvWPn8-nq2gFQyZtrzd3pBoi9_s5fkRPQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
To whom it may concern:
While looking through the tutorial,
<http://orgmode.org/worg/org-tutorials/org4beginners.html>I found a few
typos which were confusing to me at first.
In the 'Keep track of lists and notes' section, the following source code
line:
Start a new document (*C-x b),
seems to be missing a trailing asterisk with regard to the keyboard
shortcut C-x b, resulting in what looks like *C-x as the initial command.
Fixed looks like this:
Start a new document (*C-x b*),
In Agendas: New shortcuts, the following source code line:
- C-c .* -- add date
Seems to be missing a lead asterisk, which causes a confusing looking
shortcut in both the source and compiled versions, as well as a lack of
bolding in the source version. Fixed looks like this:
- *C-c .* -- add date
In Agendas - Appointments and Deadlines section, the following source code
line:
/Call fred/ (*M-RET*Call
fred), but at the end press *C-c .*.
Should contain an additional space, between *M-RET* and 'Call fred.' The
lack of space is causing the entire statement to be bolded in the source
version, where 'M-RET' and 'C-c .' are the only things which should be
bolded, as well as showing the C-c command as *C-c .. which is sorely
confusing. Fixed looks so:
/Call fred/ (*M-RET* Call
fred), but at the end press *C-c .* .
Thanks for putting together a nice tutorial! It helped me learn orgmode
very quickly, despite the delay to figure out the typos.
[-- Attachment #2: Type: text/html, Size: 1857 bytes --]
next reply other threads:[~2013-07-16 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 0:28 Patrick Daly [this message]
2013-07-16 0:46 ` Tutorial Typos Josiah Schwab
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=CAE2UF2xFL2_eWNwLmuvWPn8-nq2gFQyZtrzd3pBoi9_s5fkRPQ@mail.gmail.com \
--to=ichaleynbin@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
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).