From: Nick Dokos <nicholas.dokos@hp.com>
To: scrawler@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: plain text best practice?
Date: Wed, 06 Jun 2012 00:11:33 -0400 [thread overview]
Message-ID: <5683.1338955893@alphaville> (raw)
In-Reply-To: Message from scrawler@gmail.com of "Tue, 05 Jun 2012 22:38:13 CDT." <20120605223813.464454b5@tomsarchtoo>
scrawler@gmail.com wrote:
> howdy guys,
>
> I want to use org-mode for writing documents that don't necessarily
> have very many headings or sub-headings.
>
> I could do:
>
> * Chapter One
> lots of text
> * Chapter Two
> lots more text
>
> or:
>
> * Chapter One
> - lots of text
> * Chapter Two
> - lots more text
>
> or:
>
> * Chapter One
> ** paragraph 1
> lots of text
> ** paragraph 2
> lots of text
> * Chapter Two
>
> ...but I'm not sure which to use. It almost seems like the last format
> is the best, but I don't want to type paragraph headings. Maybe the
> first few words of the paragraph could be a heading after the fact, but
> not as I write.
>
> Apologies for such a basic question, but I how can I leverage org-mode
> to just write? What do you do?
>
Use the first form. If you feel that the chapter needs to be split up,
use second level headings to split it up into sections. If a section
gets too big, use third-level headings for subsections. And so on...
Org-mode is not buying you much in this case: you can navigate easily
between chapters and you can hide the contents of all the other chapters
while leaving exposed the one you are working on. But it doesn't cost
anything either. And if you ever decide to publish the thing (on paper,
as a PDF on the web, as HTML on the web, etc.), you will be able to
trivially do it. So just write and don't sweat it too much.
Nick
next prev parent reply other threads:[~2012-06-06 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 3:38 plain text best practice? scrawler
2012-06-06 3:50 ` Christopher Schmidt
2012-06-06 4:02 ` William LÉCHELLE
2012-06-06 4:11 ` Nick Dokos [this message]
2012-06-06 4:33 ` Eric Abrahamsen
2012-06-13 14:39 ` Eric S Fraga
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=5683.1338955893@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=scrawler@gmail.com \
/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).