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

From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [export] org-export-with-* bugs
Date: Wed, 18 Dec 2013 00:24:46 -0500	[thread overview]
Message-ID: <87mwjyenoh.fsf@gmail.com> (raw)
In-Reply-To: <87wqj38jy3.fsf@gmail.com>

2013ko abenudak 17an, Nicolas Goaziou-ek idatzi zuen:
> The more I look at it, the more I'm inclined to think that it's totally
> useless. I don't think anyone wants tables removed from Org syntax.
> 
> Though, occasionally some line starting with "|" can be interpreted as
> a table. In this case, it's possible to use "\vert" entity anyway.
> 
> I'm not sure it is worth fixing. I think we really should remove it, or
> change its meaning, like "|:nil means that all tables are ignored in
> export process" (which is probably almost as useless). The same goes for
> "::nil".

I think either suggestion (total removal or changing semantics) is a
reasonable option.

> I attach a patch that should solve this (but doesn't handle tables or
> fixed-width areas).

(fixed-width is one of the branches in the ‘case’ form in the new
code...?)

I can confirm the fix.  It looks like the new mechanism is equivalent to
a parse tree filter.  (Also, reading the patch I feel like I finally
understand what a parse tree filter can/should look like.)  Should
org-export--remove-uninterpreted be added to the default value of
org-export-filter-parse-tree-functions, rather than hard-coding it into
org-export-as?

Thanks for the quick patch,

-- 
Aaron Ecay

next prev parent reply	other threads:[~2013-12-18  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16  3:37 [export] org-export-with-* bugs Aaron Ecay
2013-12-17 17:29 ` Nicolas Goaziou
2013-12-17 19:36   ` Rasmus
2013-12-18  5:24   ` Aaron Ecay [this message]
2013-12-18 13:31     ` Nicolas Goaziou

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=87mwjyenoh.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).