From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: LaTeX export > Avoid \newline command after timestampsX-Draft-From: ("nnimap+mc:INBOX.sncb") Date: Fri, 19 Mar 2010 18:20:20 +0100 Message-ID: References: <87ocin3yq6.fsf@mundaneum.com> <87fx3yg1mm.wl%dmaus@ictsoc.de> <87aau6t2ue.fsf@mundaneum.com> <87y6hpkg4f.wl%dmaus@ictsoc.de> <871vfhspjj.fsf@mundaneum.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NshIK-0001T6-Iq for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:40 -0400 Received: from [140.186.70.92] (port=50094 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NshII-0001Rx-UV for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NshIG-0006Po-WA for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:38 -0400 Received: from ey-out-1920.google.com ([74.125.78.144]:15716) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NshIG-0006Pa-B4 for emacs-orgmode@gnu.org; Fri, 19 Mar 2010 14:51:36 -0400 Received: by ey-out-1920.google.com with SMTP id 4so293006eyg.34 for ; Fri, 19 Mar 2010 11:51:35 -0700 (PDT) In-Reply-To: <871vfhspjj.fsf@mundaneum.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Francesco Pizzolante Cc: mailing-list-org-mode On Mar 18, 2010, at 2:54 PM, Francesco Pizzolante wrote: > Hi David, > > David Maus wrote: >> Took me a while to realize the problem with current implementation: >> If >> you already have a blank line between scheduled/deadline line and the >> content the newline forces extra spacing between scheduled/deadline >> and the following paragraph. > > I'm sorry if I wasn't clear enough. > > >> This cleary /is/ problem. Maybe we should catch these two cases >> (patch attached): >> >> ,---- >> | (unless (and (looking-at ".*\n[ \t]*\n") (looking-at ".*\\\ >> \newline[ \t]*$")) >> `---- >> >> Insert \newline only if there is no paragraph separator. As far as I >> can see the LaTeX code is already rendered when >> `org-export-latex-keywords' is called so this should work out. > > I tried your patch, but I still get extra \newline commands in the > generated > LaTeX. > > Let's go back to examples, I think it will be easier to understand > my problem. > > 1) Heading with no text > > --8<---------------cut here---------------start------------->8--- > ** STARTED First > SCHEDULED: <2010-03-01 Mon> DEADLINE: <2010-03-19 Fri> > --8<---------------cut here---------------end--------------->8--- > > Gives the following: > > --8<---------------cut here---------------start------------->8--- > \subsection{\textbf{STARTED} First} > \label{sec-1.1} > > \texttt{SCHEDULED:} \textit{2010-03-01 Mon} \texttt{DEADLINE:} > \textit{2010-03-19 Fri}\newline > --8<---------------cut here---------------end--------------->8--- > > Which gives me an extra vertical space between this heading and the > next one. > > While I would expect this (with or without the extra blank line in > this case, > as there's no text after): > > --8<---------------cut here---------------start------------->8--- > \subsection{\textbf{STARTED} First} > \label{sec-1.1} > > \texttt{SCHEDULED:} \textit{2010-03-01 Mon} \texttt{DEADLINE:} > \textit{2010-03-19 Fri} > > --8<---------------cut here---------------end--------------->8--- > > > 2) Heading with text and no blank line between heading and text > > --8<---------------cut here---------------start------------->8--- > ** STARTED Second > SCHEDULED: <2010-03-01 Mon> DEADLINE: <2010-03-19 Fri> > This task is split among all services and communication between the > entities. > --8<---------------cut here---------------end--------------->8--- > > This gives the following: > > --8<---------------cut here---------------start------------->8--- > \subsection{\textbf{STARTED} Second} > \label{sec-1.2} > > \texttt{SCHEDULED:} \textit{2010-03-01 Mon} \texttt{DEADLINE:} > \textit{2010-03-19 Fri}\newline\newline > This task is split among all services and communication between the > entities. > --8<---------------cut here---------------end--------------->8--- > > I also get an extra vertical space between the timestamps and the > text which > is on a new paragraph. > > Instead, I was expecting this: > > --8<---------------cut here---------------start------------->8--- > \subsection{\textbf{STARTED} Second} > \label{sec-1.2} > > \texttt{SCHEDULED:} \textit{2010-03-01 Mon} \texttt{DEADLINE:} > \textit{2010-03-19 Fri} > > This task is split among all services and communication between the > entities. > --8<---------------cut here---------------end--------------->8--- > > > 3) Heading with text and blank line between heading and text > > --8<---------------cut here---------------start------------->8--- > ** DONE Third > DEADLINE: <2010-03-26 Fri> > > This task is split among all services and communication between the > entities. > Second paragraph. > > fdqsfdq > --8<---------------cut here---------------end--------------->8--- > > This gives the following: > > --8<---------------cut here---------------start------------->8--- > \subsection{\textbf{DONE} Third} > \label{sec-1.3} > > \texttt{DEADLINE:} \textit{2010-03-26 Fri}\newline > > This task is split among all services and communication between the > entities. > Second paragraph. > > fdqsfdq > --8<---------------cut here---------------end--------------->8--- > > In this case, again, I get an extra vertical space between the > timestamps and > the text which is also in a new paragraph. > > Instead, I would simply expect this: > > --8<---------------cut here---------------start------------->8--- > \subsection{\textbf{DONE} Third} > \label{sec-1.3} > > \texttt{DEADLINE:} \textit{2010-03-26 Fri} > > This task is split among all services and communication between the > entities. > Second paragraph. > > fdqsfdq > --8<---------------cut here---------------end--------------->8--- > > > As you can see from these 3 examples, it is safer to always generate > blank > lines only instead of \newline commands. > > Sorry for the length of this message. On the contrary, thank you for this long message. This is exactly what nails the discussion and shows the problems. I agree with what I think is the conclusion of this discussion: No \newline, only an empty line to star a new paragraph, in all three example cases. I have made this change now, thank you both. - Carsten