From: David Rogers <davidandrewrogers@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: LaTex Adjustments for Org-Export
Date: Sat, 03 Aug 2013 19:03:37 -0700 [thread overview]
Message-ID: <8761vmus92.fsf@gmail.com> (raw)
In-Reply-To: <CA+M2ft-54tZeNF5nc=20reSaDw-6s35k_QyZh0J9SLOdaj8s+g@mail.gmail.com> (John Hendy's message of "Sat, 3 Aug 2013 20:26:46 -0500")
John Hendy <jw.hendy@gmail.com> writes:
> That was [mostly] a joke. I'm actually not clear from the text above
> what is desired. The description says "no leading indent and blank
> line between," but the example text shows non-indent on first
> paragraph, indent on second (which would void the page-span concern),
> and no line break...
At first, I didn't understand the original post, but when I took the
original request to mean "no indent *on the first paragraph of the
chapter or section*", then the rest made more sense to me.
My take on the subject:
- indent is good if you want it;
- added blank line is good if you want it;
- both at once is never good; it's necessary to choose between extra
blank OR indenting, and stick with your choice throughout a work;
- indenting the first paragraph of a chapter, or putting an extra blank
line directly after the chapter heading, should both be
eliminated. (Of course chapter headings should have suitable vertical
space after them depending on the style - I'm talking about not also
adding extra after that.)
- In either case, this means a special rule is needed: paragraphs should
begin with indent, or with an added blank line - BUT not if this is
the first paragraph.
--
David
next prev parent reply other threads:[~2013-08-04 2:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 12:27 LaTex Adjustments for Org-Export Jeff Rush
2013-07-31 13:44 ` John Hendy
2013-07-31 14:01 ` Nick Dokos
2013-07-31 16:24 ` Nick Dokos
2013-07-31 18:56 ` Suvayu Ali
2013-07-31 21:26 ` Nick Dokos
2013-08-03 20:49 ` Brian van den Broek
2013-08-04 1:26 ` John Hendy
2013-08-04 2:03 ` David Rogers [this message]
2013-08-04 4:16 ` Brian van den Broek
2013-08-04 14:51 ` Anthony Lander
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=8761vmus92.fsf@gmail.com \
--to=davidandrewrogers@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).