emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: new exporter and latex attributes
Date: Tue, 21 Aug 2012 22:27:05 +0200	[thread overview]
Message-ID: <87628cc7om.fsf@gmail.com> (raw)
In-Reply-To: <20120821190812.GA95414@BigDog.local> (Rick Frankel's message of "Tue, 21 Aug 2012 15:08:12 -0400")

Hello,

Rick Frankel <rick@rickster.com> writes:

> BUT, if the source block is not named then a duplicate results will be
> created above the current results block w/ the attribute header when
> the source block is re-evaluated.

That's correct.

For convenience, Babel might copy src-block attributes to the generated
results upon block evaluation. It would be strange though: do both
src-block and results have to share the same caption, the same label..?
We could limit copy to ATTR keywords, perhaps. I feel it's hackish,
though.

> I guess it's acceptable to require all source blocks to be named if
> you want to have header attributes associated with the generated
> results, but this is a significant incompatible change from the
> behavior of the current exporter...

There are a few incompatible changes, indeed. You can't make an omelette
without breaking eggs.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2012-08-21 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 21:28 new exporter and latex attributes Rick Frankel
2012-08-20 22:54 ` Nicolas Goaziou
2012-08-21  0:55   ` Rick Frankel
     [not found]     ` <rick@rickster.com>
2012-08-21  5:34       ` Nick Dokos
2012-08-21 19:08         ` Rick Frankel
2012-08-21 20:27           ` Nicolas Goaziou [this message]
2012-08-21 13:06     ` Bastien
2012-08-21 13:04   ` Bastien
2012-08-21 13:07     ` Nicolas Goaziou
2012-08-21 13:47     ` Nick Dokos
2012-08-21 17:41       ` Bastien

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=87628cc7om.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).