From: Carsten Dominik <carsten.dominik@gmail.com>
To: Francesco Pizzolante <fpz@missioncriticalit.com>
Cc: mailing-list-org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export > Avoid \newline command after timestampsX-Draft-From: ("nnimap+mc:INBOX.sncb")
Date: Wed, 17 Mar 2010 15:35:38 +0100 [thread overview]
Message-ID: <A6077194-7757-4F60-9164-44C3D31240FC@gmail.com> (raw)
In-Reply-To: <87ocin3yq6.fsf@mundaneum.com>
Hi Francesco,
thanks for this. The reason why I put this is is to make sure that
text after that line will start
in a new line, and now flow into the scheduled/deadline line. For
example:
*** DONE My Task :Be:
SCHEDULED: <2010-03-01 Mon> DEADLINE: <2010-03-05 Fri>
this should start a new line but does not with your patch
Do you disagree that this is the right thing to do? Do you know a
method to achieve the same result without generating extra white space?
- Carsten
On Mar 17, 2010, at 1:43 PM, Francesco Pizzolante wrote:
> Hi,
>
> When exporting an Org buffer to latex, I can see that Org generates
> an extra
> \newline command just after exporting the timestamps to the heading.
>
> An example.
>
> This Org stuff:
> --8<---------------cut here---------------start------------->8---
> *** DONE My Task :Be:
> SCHEDULED: <2010-03-01 Mon> DEADLINE: <2010-03-05 Fri>
> :LOGBOOK:
> - State "STARTED" from "TODO" [2010-03-02 Tue 09:30]
> - State "DONE" from "STARTED" [2010-03-02 Tue 10:00]
> CLOCK: [2010-03-02 Tue 09:30]--[2010-03-02 Tue 10:00] => 0:30
> - PWA.
> :END:
> :PROPERTIES:
> :Effort: 4:00
> :END:
> --8<---------------cut here---------------end--------------->8---
>
> Is exported to latex this way:
> --8<---------------cut here---------------start------------->8---
> \subsubsection{\textbf{DONE} My Task \textbf{:Be:}}
> \label{sec-2.2.2}
>
> \texttt{SCHEDULED:} \textit{2010-03-01 Mon} \texttt{DEADLINE:}
> \textit{2010-03-05 Fri}\newline
> --8<---------------cut here---------------end--------------->8---
>
> At the end of the timestamps line, you can see the extra \newline
> command.
>
> This \newline command should be removed as it adds extra vertical
> space which
> does not respect the document class definition used for the document.
>
> In order to do that, I made the following change to org-latex.el and
> it works
> for me, but I'm not sure my change is completely safe:
>
> --8<---------------cut here---------------start------------->8---
> index 03216a8..88bd8c3 100644
> --- a/lisp/org-latex.el
> +++ b/lisp/org-latex.el
> @@ -1511,7 +1511,7 @@ The conversion is made depending of STRING-
> BEFORE and STRING-AFTER."
> (beginning-of-line 1)
> (unless (looking-at ".*\\\\newline[ \t]*$")
> (end-of-line 1)
> - (insert "\\newline")))))
> + ))))
>
> (defun org-export-latex-fixed-width (opt)
> "When OPT is non-nil convert fixed-width sections to LaTeX."
> --8<---------------cut here---------------end--------------->8---
>
> Is this the right thing to do to avoid this extra \newline command?
>
> Thanks,
> Francesco
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-03-17 14:35 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 [this message]
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
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=A6077194-7757-4F60-9164-44C3D31240FC@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fpz@missioncriticalit.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).