From: Buddy Butterfly <buddy.butterfly@web.de>
To: emacs-orgmode@gnu.org
Subject: Re: What happened to clocktable in pdf export?
Date: Fri, 25 Jul 2014 11:29:50 +0200 [thread overview]
Message-ID: <53D2238E.2040505@web.de> (raw)
In-Reply-To: <87iomllsdg.fsf@nicolasgoaziou.fr>
Hi,
this is sooo cool! Was not aware of this syntax change.
It works now as expected.
Regarding
"\__" syntax doesn't exist anymore, so no exporter will recognize it.
The replacement is "\emsp". I fixed it in maint. Thank you for reporting
it.
How can I easily fix it in my Ubuntu dist? I am running the standard
repo version from Ubuntu 14.04. Any .el or something like that?
Just a small one. As now the line for the clocktable becomes longer,
is there a method to break up the clocktable header into multiple lines?
Thanks a lot man, you saved my docs ;-)
Cheers,
Matt
Am 25.07.2014 um 11:06 schrieb Nicolas Goaziou:
> Hello,
>
> Buddy Butterfly <buddy.butterfly@web.de> writes:
>
>> 1. Even though the column separators are given in latex, they are not
>> printed
>> anymore. Only when using the org-table standard feature |<>|. But such
>> an additional line will be deleted after a clocktable refresh.
> This is because syntax has changed. Attributes specific to the table
> have to be inserted above the table, not above the dynamic block. What
> you really want is (note the differences in "attr_latex" line)
>
> #+BEGIN: clocktable :maxlevel 7 :scope tree3 :indent t
> #+ATTR_LATEX: :environment longtable :align l|r|r|r
> | Headline | Time | | |
> ...
> #+END:
>
> Since the table is auto generated, you have to send this line through
> the :header property:
>
> #+BEGIN: clocktable :maxlevel 7 :scope tree3 :indent t :header "#+attr_latex: :align l|r|r|r :environment longtable\n"
> ...
> #+END:
>
> Now you can also avoid using both "#+latex:" lines with appropriate
> properties:
>
> #+BEGIN: clocktable :maxlevel 7 :scope tree3 :indent t :header "#+attr_latex: :align l|r|r|r :environment longtable :center t :font \\footnotesize\n"
> ...
> #+END:
>
> Eventually you can also insert a caption with, e.g.,
>
> #+BEGIN: clocktable :maxlevel 7 :scope tree3 :indent t :header "#+attr_latex: :align l|r|r|r :environment longtable :center t :font \\footnotesize\n#+caption: Clock summary at {{{time(%c)}}}\n"
>
>> 2. The indentation underscores are printed, which did not come before.
>> Especially
>> this makes it ugly. Before the _ have not been exported.
> "\__" syntax doesn't exist anymore, so no exporter will recognize it.
>
> The replacement is "\emsp". I fixed it in maint. Thank you for reporting
> it.
>
>
> Regards,
>
next prev parent reply other threads:[~2014-07-25 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 14:07 What happened to clocktable in pdf export? Buddy Butterfly
2014-04-28 9:30 ` Buddy Butterfly
2014-04-28 11:33 ` Nicolas Goaziou
2014-07-24 12:48 ` Buddy Butterfly
2014-07-25 9:06 ` Nicolas Goaziou
2014-07-25 9:29 ` Buddy Butterfly [this message]
2014-07-25 11:16 ` Nicolas Goaziou
2014-07-30 11:04 ` Buddy Butterfly
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=53D2238E.2040505@web.de \
--to=buddy.butterfly@web.de \
--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).