From: Francesco Pizzolante <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: Carsten Dominik
<carsten.dominik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mailing-list-org-mode <emacs-orgmode-mXXj517/zsQ@public.gmane.org>
Subject: Re: LaTeX export > Avoid \newline command after timestampsX-Draft-From: ("nnimap+mc:INBOX.sncb")
Date: Thu, 18 Mar 2010 10:07:37 +0100 [thread overview]
Message-ID: <87aau6t2ue.fsf@mundaneum.com> (raw)
In-Reply-To: <F8590385-44EE-4081-81FA-FC10AA364CA0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Carsten Dominik's message of "Thu, 18 Mar 2010 06:47:05 +0100")
Hi,
Thanks for your remarks.
>>> 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?
>>
>> We could simply insert a blank line (e.g. "\n\n"), couldn't we? This
>> would let LaTeX start a new paragraph if there's no space between
>> scheduled/deadline line and do no harm if there is, because LaTeX
>> doesn't care about multiple newlines.
>
> Yes, we could, but what I tries was to *not* start a new paragraph...
Why not? From my point of view, the timestamps are more technical information
and the text you have after is the "real" text regarding the heading, so why
not put them on separate paragraphs?
After a few more tests, I think that David's suggestion is the best one:
having a simple blank line after the timestamps in the generated LaTex code.
This way, if we have some text in the heading, LaTex will simply start a new
paragraph and we will have the correct spacing. If don't have text in the
heading, LaTeX will simply ignore the blank line and will format the next
heading according to the document class chosen.
The problem with the actual implementation is that it forces a newline in all
cases (both if you have text in the heading or not) which does not respect the
document class formatting that you've chosen.
What do you think?
Thanks a lot,
Francesco
_______________________________________________
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 9:07 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aau6t2ue.fsf@mundaneum.com \
--to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
--cc=carsten.dominik-Re5JQEeQqe8AvxtiuMwx3w@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.