From: KDr2 <killy.draw@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] Merge export-block type within special-block
Date: Thu, 25 Sep 2014 23:12:53 +0800 [thread overview]
Message-ID: <CAHfjm6hUTOKfMndKE761G6fpC_UMCXd6EM3yWfa3RWjiw5-Tig@mail.gmail.com> (raw)
In-Reply-To: <87oav0vmv1.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
I found this was fixed on both maint and master branch :)
Thanks for all your works, but would you tell us how did you do it? or give
the commit id? (Sorry I did not find it by myself...)
Thank you very much.
On Sun, Aug 31, 2014 at 8:56 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> KDr2 <killy.draw@gmail.com> writes:
>
> > This is nice, but it brought a bug, `[N]' in HTML block is recognized as
> > footnote, e.g.:
> >
> > #+BEGIN_HTML
> > ONE[1]
> > <script>
> > console.log(v1[0]);
> > </script>
> > #+END_HTML
> >
> > There are two footnotes in the generated HTML. Would you fix this
> > please?
>
> Unfortunately, no, I cannot fix it.
>
> The problem is even deeper. Indeed, my approach is fundamentally wrong:
> it is impossible to postpone choosing between parsed or raw data at
> export time. This information must be obtained at parsing time.
>
> Yet, I think syntax should not depend on the libraries loaded. So the
> initial problem still needs a solution.
>
> Special blocks and export blocks are just too similar. We could make
> them slightly different. One solution is to mark explicitly blocks meant
> to insert raw code. E.g.,
>
> #+BEGIN_SOMETHING :special t
> ...
> #+END_SOMETHING
>
> vs
>
> #+BEGIN_SOMETHING
> ...
> #+END_SOMETHING
>
> In the first case contents would be parsed and the block treated as
> a special block (i.e. depending on the back-end) whereas in the second
> case, contents would be inserted as-is in the buffer, provided target
> export back-ends accepts data from "SOMETHING" blocks (IOW "SOMETHING"
> = "LATEX" if ox-latex is used).
>
> This is clearly not backward-compatible. But it only modifies syntax for
> special blocks, which, I guess, are much less used than their cousins,
> export blocks. The ":special t" may be shorter, too.
>
> Cc'ing Bastien for his opinion.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
--
--
KDr2, http://kdr2.com
[-- Attachment #2: Type: text/html, Size: 2836 bytes --]
next prev parent reply other threads:[~2014-09-25 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 12:37 [ANN] Merge export-block type within special-block Nicolas Goaziou
2014-07-27 22:13 ` Bastien
2014-08-29 14:02 ` KDr2
2014-08-31 12:56 ` Nicolas Goaziou
2014-09-25 15:12 ` KDr2 [this message]
2014-09-26 9:09 ` Nicolas Goaziou
2014-09-28 6:18 ` Aaron Ecay
2014-09-28 7:26 ` 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=CAHfjm6hUTOKfMndKE761G6fpC_UMCXd6EM3yWfa3RWjiw5-Tig@mail.gmail.com \
--to=killy.draw@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).