From: Christopher Schmidt <christopher@ch.ristopher.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-check.org confusion
Date: Wed, 20 Mar 2013 20:32:04 +0000 (GMT) [thread overview]
Message-ID: <871ub9olre@ch.ristopher.com> (raw)
In-Reply-To: <FCEE4469EE8B234199968ECA9B0661E208CD34E8@STNEEX10MB02.stone.ne.gov> (David Loyall's message of "Wed, 20 Mar 2013 20:18:38 +0000")
"Loyall, David" <david.loyall@nebraska.gov> writes:
> Dear orgmode users: what does that represent?
(info "(emacs)Interlocking")
Christopher
next prev parent reply other threads:[~2013-03-20 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 20:06 org-check.org confusion Lawrence Bottorff
2013-03-20 20:18 ` Loyall, David
2013-03-20 20:32 ` Christopher Schmidt [this message]
2013-03-20 20:41 ` Lawrence Bottorff
2013-03-29 22:15 ` Loyall, David
2013-03-30 7:38 ` Sebastien Vauban
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=871ub9olre@ch.ristopher.com \
--to=christopher@ch.ristopher.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).