From: "Peter Neilson" <neilson@windstream.net>
To: emacs-orgmode@gnu.org
Subject: Re: does this pandoc error look familiar to anybody?
Date: Mon, 19 Mar 2018 09:33:25 -0400 [thread overview]
Message-ID: <op.zf4k9zu9rns8nc@odin> (raw)
In-Reply-To: <87d100qmcq.fsf@yandex.com>
On Mon, 19 Mar 2018 08:30:13 -0400, Colin Baxter <m43cap@yandex.com> wrote:
>>>>>> Adonay Felipe Nogueira <adfeno@hyperbola.info> writes:
>
> ---------------- snip ----------------
>
> > Good academic and writting practice tells that headings shouldn't
> > be more than four levels deep. In LaTeX (which is used for PDF
> > export), and its default `article' class, you can have
> > `section{}', `subsection{}', `subsubsection{}' and --- if I'm not
> > mistaken --- `subsubsubsection{}'.
>
> There's also part{}.
Indeed, if your writing is to be read by other people, not just yourself,
you should try to stay to no more than two levels. If you feel you need
levels deeper than two, perhaps your should refactor your writing.
When I say "two" do I mean * and **, or do I mean ** and ***? Well, I
guess that depends upon what the value of two is.
Moreover, as we can already see in this discussion, any attempt to correct
errors of style, grammar or spelling will itself contain additional
errors. This phenomenon is sometimes called Muphry's Law. Yes, Muphry, not
Murphy. https://en.wikipedia.org/wiki/Muphry%27s_law
prev parent reply other threads:[~2018-03-19 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 4:43 does this pandoc error look familiar to anybody? Samuel Wales
2018-03-19 9:56 ` Eric S Fraga
2018-03-19 22:10 ` Samuel Wales
2018-03-20 7:42 ` Eric S Fraga
2018-03-20 18:04 ` Nick Dokos
2018-03-20 20:00 ` Samuel Wales
2018-03-24 23:58 ` Samuel Wales
2018-03-25 8:57 ` Julius Dittmar
2018-03-25 23:55 ` Samuel Wales
2018-03-19 12:02 ` Adonay Felipe Nogueira
2018-03-19 12:30 ` Colin Baxter
2018-03-19 13:33 ` Peter Neilson [this message]
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=op.zf4k9zu9rns8nc@odin \
--to=neilson@windstream.net \
--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).