emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Re: Bug: #+ATTR_LaTeX broken in LaTeX export [6.36trans (release_6.36.461.g798e)]
Date: Thu, 01 Jul 2010 00:22:16 +0200	[thread overview]
Message-ID: <87hbkkgnzb.wl%n.goaziou@gmail.com> (raw)
In-Reply-To: <8739w4tdo9.fsf@gmail.com>

I don't know about #+BEGIN_changemargin (but as far as I understand,
it's coming from org-exp-blocks and should be handled during
preprocess-hook, so it is beyond the scope of this patch).

There is some design choice involved here. Until recently, there was a
catch-all function called org-export-handle-comments that was called
at the end of the export process and removed any line starting with
a #. It was certainly useful, but made things hard to debug : had
the #+ATTR_LaTeX line been misinterpreted or just silently deleted ?

At the moment, org-export-handle-comments only handles... comments.
But everything that is not comments has to be taken care of somewhere
else. For example, org-export-attach-captions-and-attributes
deletes #+CAPTIONS and #+ATTR_backend in the process, and
org-export-select-backend-specific-text deletes #+backend
and #+ATTR_backend not used (that's what my patch do, actually).

If you want to apply my patch (v. 2), we have to define a function to
remove #+TBLFM and #+TBLNAME lines because there is none at the
moment. It could be org-export-special-table-lines but it doesn't look
like it's the purpose of that function.

Otherwise, you can just ignore the patch and bring back the full power
to org-export-handle-comments.

I personally prefer avoiding do-it-all functions. But I'm not a
maintainer.

Regards,

-- Nicolas

  reply	other threads:[~2010-06-30 22:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 18:49 Bug: #+ATTR_LaTeX broken in LaTeX export [6.36trans (release_6.36.461.g798e)] Tassilo Horn
2010-06-30 19:44 ` Sébastien Vauban
2010-06-30 20:44   ` Eric Schulte
2010-06-30 20:58     ` Sébastien Vauban
2010-06-30 21:05     ` Nicolas Goaziou
2010-06-30 21:26       ` Eric Schulte
2010-06-30 22:22         ` Nicolas Goaziou [this message]
2010-06-30 22:49           ` Eric Schulte
2010-06-30 23:03             ` Eric Schulte
2010-07-01  4:44             ` Tassilo Horn
2010-07-01  7:48               ` Carsten Dominik
2010-07-01  8:33                 ` Bernt Hansen
2010-07-01  9:03                   ` Carsten Dominik
2010-07-01  7:25           ` Sébastien 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=87hbkkgnzb.wl%n.goaziou@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --cc=wxhgmqzgwmuf@spammotel.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
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).