emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Francesco Pizzolante" <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mailing-list-org-mode
	<public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
	Francesco Pizzolante
	<public-fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Subject: Re: ATTR_LATEX not being applied on dynamic blocks
Date: Thu, 05 Sep 2013 10:18:46 +0200	[thread overview]
Message-ID: <874n9zisux.fsf@somewhere.org> (raw)
In-Reply-To: <878uzc4xwt.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Nicolas Goaziou's message of "Wed, 04 Sep 2013 13:41:06 +0200")



Hello Nicolas,

Nicolas Goaziou wrote:
> "Francesco Pizzolante" <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org> writes:
>
>> But if I try what you suggest and move the #+ATTR_LATEX line inside the
>> dynamic block (after the #+BEGIN: clocktable and just before the generated
>> table), then this line gets lost as soon as the dynamic block is
>> regenerated, which is not what I expect.
>
> Then some attribute could be added to dynamic block arguments in order to
> re-create the ATTR_LATEX keyword each time. IIRC we did that for #+CAPTION
> some months ago. It shouldn't be difficult to do it for this one.

I've seen, indeed (thanks!), that there was a ":header" option, which you can
use to add free text in front of the dynamic table.

--8<---------------cut here---------------start------------->8---
#+BEGIN: clocktable :maxlevel 2 :scope ("clock-file.org") :block 2013-08 :fileskip0 t :lang "en" :header "#+ATTR_LaTeX: :environment longtabu :align lXrr\n"
#+ATTR_LaTeX: :environment longtabu :align lXrr
| File           | Headline            |   Time |      |
|----------------+---------------------+--------+------|
|                | ALL Total time      |   1:44 |      |
|----------------+---------------------+--------+------|
| clock-file.org | File time           | *1:44* |      |
|                | Projet management   |   1:44 |      |
|                | \__ Writing reports |        | 1:44 |
#+END:

Though, doing so, there is no CAPTION anymore...

I could add it in the "header", but then I loose the auto-generated (and
useful) stuff in the caption itself:

#+CAPTION: Clock summary at [2013-09-04 Wed 14:22], for August 2013.
--8<---------------cut here---------------end--------------->8---
                         ^^^^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^
                         useful                     very useful

Maybe adding a ":header" should not strip the autogenerated caption?

>> With Org 7, having the #+ATTR_LATEX line just before the #+BEGIN:
>> clocktable line applies the attributes to the inner table of the dynamic
>> block and the #+ATTR_LATEX line is not lost each time I regenerate the
>> dynamic block.
>
> This is not possible anymore.

OK.

Regards,
 Francesco

  parent reply	other threads:[~2013-09-05  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 15:24 ATTR_LATEX not being applied on dynamic blocks Francesco Pizzolante
2013-09-03 15:46 ` Nicolas Goaziou
     [not found]   ` <87a9jt3o2l.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-04  7:46     ` Francesco Pizzolante
2013-09-04 11:41       ` Nicolas Goaziou
     [not found]         ` <878uzc4xwt.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-05  8:18           ` Francesco Pizzolante [this message]
2013-09-10 10:19             ` [PATCH] Allow caption and header text in clocktable dblocks Sebastien Vauban

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=874n9zisux.fsf@somewhere.org \
    --to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
    --cc=n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
    --cc=public-fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY-wOFGN7rlS/M9smdsby/KFg@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).