emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: RFC: inheritance of export attributes
Date: Sun, 31 Mar 2013 19:12:30 -0400	[thread overview]
Message-ID: <87hajrupsx.fsf@gmail.com> (raw)
In-Reply-To: <87sj3o5slg.fsf@gmail.com>

Hi Nicolas,

2013ko martxoak 21an, Nicolas Goaziou-ek idatzi zuen:
> 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?

This isn’t a solution, generally speaking.  I may be working on a graph
in R; I know that I want it to be inserted in the LaTeX output with
width 6in, even as I go through several iterations of changing the
graph.  So, each time I do, either I have to manually re-enter the
width, or be resigned to the LaTeX export being “broken” until I am
done.  (and the same goes for a table, of course)

> 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.

Well, this is one specific current use.  But the fact that it is a hack
doesn’t mean the inheritance approach is inherently hackish.

> 
> 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

This would lead to long begin_src lines, especially if one wants to
export to multiple backends.  I think it is much more pleasant to be
able to edit several lines:

#+ATTR_LaTeX: foo
#+ATTR_HTML: bar

rather than packing them all into one begin_src line.  (But I think I
could live with this as a solution, if I had to.)

What if attribute inheritance was only implemented for RESULTS drawers?
I guess that would look more like a “hack,” but it would avoid
interfering with other areas where attribute inheritance might cause
confusion.

Thanks,

-- 
Aaron Ecay

     prev parent reply	other threads:[~2013-03-31 23:12 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
2013-03-31 23:12   ` Aaron Ecay [this message]

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=87hajrupsx.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.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

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).