From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: RFC: inheritance of export attributes
Date: Thu, 21 Mar 2013 22:51:55 +0100 [thread overview]
Message-ID: <87sj3o5slg.fsf@gmail.com> (raw)
In-Reply-To: <87a9q0vtr7.fsf@gmail.com> (Aaron Ecay's message of "Tue, 19 Mar 2013 01:33:16 -0400")
Hello,
Aaron Ecay <aaronecay@gmail.com> writes:
> I have noticed a difficulty with :results table drawer babel blocks. It
> isn’t possible to put ATTR_LATEX keywords on the table in that case. If
> they are placed outside of the drawer, they apply to the drawer and not
> the table. If they are placed inside it, they will be deleted when the
> block is reevaluated.
What about evaluating it, inserting the attr_latex keyword, and then
disabling evaluation for that block?
> Would it be possible for ATTR_FOO attributes to be inherited by child
> elements, so that this case would work? It would solve this problem,
> and also allow things like:
>
> #+ATTR_LATEX: :width 200px
> :DRAWER:
> # several images, all of which should be 200 px wide
> :END:
>
> I thought I would ask for comments, since this might break other things
> in ways I’m not thinking of.
I understand the interest for the problem at hand, but, generally
speaking, I tend to think it could lead to confusion.
Attributes inheritance is but a hack used to parametrize inline images,
until we agree on a proper link syntax including its own attributes.
Another way to solve the problem would be to let Babel generate
attributes from source code with a specific keyword, e.g.:
#+begin_src :results table :attr-latex ":align lll"
...
#+end_src
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-21 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 5:33 RFC: inheritance of export attributes Aaron Ecay
2013-03-21 21:51 ` Nicolas Goaziou [this message]
2013-03-31 23:12 ` Aaron Ecay
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=87sj3o5slg.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--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).