From: Francesco Pizzolante <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: David Maus <dmaus-lYycHbxpNtazQB+pC5nmwQ@public.gmane.org>
Cc: mailing-list-org-mode
<emacs-orgmode-mXXj517/zsQ@public.gmane.org>,
Carsten Dominik
<carsten.dominik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: LaTeX export > Avoid \newline command after timestampsX-Draft-From: ("nnimap+mc:INBOX.sncb")
Date: Thu, 18 Mar 2010 17:06:12 +0100 [thread overview]
Message-ID: <877hp9r4wb.fsf@mundaneum.com> (raw)
In-Reply-To: <87wrx9skm4.wl%dmaus-lYycHbxpNtazQB+pC5nmwQ@public.gmane.org> (David Maus's message of "Thu, 18 Mar 2010 16:41:23 +0100")
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
Hi David,
> Yes, sorry, my brain's logical unit misfired. What I meant was
>
> ,----
> | (unless (or (looking-at ".*\n[ \t]*\n") (looking-at ".*\\\\newline[ \t]*$"))
> `----
>
> Translating to: insert /no/ \newline, if either (a) there is a empty
> line beneath this line or (b) there is already a \newline.
We're going ahead! ;-)
Your intention is also clearer for me now.
Examples 1 and 3 are OK. I still have a remark for example 2.
> 2) Heading with text and no blank line between heading and text
>
> ** STARTED Second
> SCHEDULED: <2010-03-01 Mon> DEADLINE: <2010-03-19 Fri>
> This task is split among all services and communication between the
> entities.
>
> Gives the following:
>
> \section{STARTED Second}
> \label{sec-2}
>
> \texttt{SCHEDULED:} \textit{2010-03-01 Mon} \texttt{DEADLINE:} \textit{2010-03-19 Fri}\newline
> This task is split among all services and communication between the
> entities.
>
> This would be Carsten's case.
Yes, it is. ;-)
> IMO inserting a \newline after the deadline/scheduled line if text follows
> immediately (example 2) makes sense.
I'm just wondering why having a special handling for this case (the second
one). Adding a simple blank line instead of the \newline command would be
cleaner as it you would totally rely on LaTeX for the formatting.
In addition, we keep having 2 different behaviors: in example 2, the text
starts on a newline (but on the same paragraph as what comes before) while on
example 3, the text starts on a new paragraph.
See the attached picture which shows clearly the difference between the text
of section 1.2 and the text of section 1.3: for this example, I simply use the
default article formatting which uses paragraph indentation except for the
first paragraph of sections.
From my point of view, both examples 2 and 3 should be exported the same way:
it should not matter if we have (or not) an empty line in the Org buffer between
the heading and text. While, in the LaTex code, we should always add blank
line instead of \newline commands. LaTeX will thus always put things on
separate paragraphs, which totally makes sens to me.
Does all this make sense to you?
F.
[-- Attachment #2: newline-capture.png --]
[-- Type: image/png, Size: 23303 bytes --]
[-- Attachment #3: Type: text/plain, Size: 222 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-03-18 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 12:43 LaTeX export > Avoid \newline command after timestampsX-Draft-From: ("nnimap+mc:INBOX.sncb") Francesco Pizzolante
2010-03-17 14:35 ` Carsten Dominik
2010-03-17 20:00 ` David Maus
2010-03-18 5:47 ` Carsten Dominik
[not found] ` <F8590385-44EE-4081-81FA-FC10AA364CA0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-03-18 9:07 ` Francesco Pizzolante
2010-03-18 11:45 ` David Maus
[not found] ` <87y6hpkg4f.wl%dmaus-lYycHbxpNtazQB+pC5nmwQ@public.gmane.org>
2010-03-18 13:54 ` Francesco Pizzolante
2010-03-18 15:41 ` David Maus
[not found] ` <87wrx9skm4.wl%dmaus-lYycHbxpNtazQB+pC5nmwQ@public.gmane.org>
2010-03-18 16:06 ` Francesco Pizzolante [this message]
2010-03-19 17:20 ` Carsten Dominik
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=877hp9r4wb.fsf@mundaneum.com \
--to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
--cc=carsten.dominik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=dmaus-lYycHbxpNtazQB+pC5nmwQ@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).