emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bug exporting code blocks to html
Date: Tue, 23 Mar 2010 08:56:57 +0100	[thread overview]
Message-ID: <8F994B21-14B3-4090-B4BC-22AF44D26DA9@gmail.com> (raw)
In-Reply-To: <87pr2w2oa0.fsf@gmail.com>


On Mar 22, 2010, at 7:40 PM, Eric Schulte wrote:

> Hi Martin,
>
> This appears to be a bug in org-mode at large, rather than anything
> specifically babel related.
>
> notice that the following slight alteration of your new reference  
> syntax
> works as expected
>
> #+begin_src xml -n -r -l "ref:%s"
> <test>
>  <important/> ref:imp
> </test>
> #+end_src
>
> Line no. [[(imp)]] is important!


The docstring of org-coderef-label-format says (please note the final  
paragraph):

   "The default coderef format.
This format string will be used to search for coderef labels in literal
examples (EXAMPLE and SRC blocks).  The format can be overwritten in
an individual literal example with the -f option, like

#+BEGIN_SRC pascal +n -r -l \"((%s))\"
...
#+END_SRC

If you want to use this for HTML export, make sure that the format does
not introduce special font-locking, and avoid the HTML special
characters `<', `>', and `&'.  The reason for this restriction is that
the labels are searched for only after htmlize has done its job."

- Carsten


>
> Best -- Eric
>
> "Martin G. Skjæveland" <martige@ifi.uio.no> writes:
>
>> Hi,
>>
>> when I export
>>
>> -----------------------------------start
>> * test
>> #+begin_src xml -n -r -l "<!--(ref:%s)-->"
>> <test>
>>  <important/> <!--(ref:imp)-->
>> </test>
>> #+end_src
>>
>> Line no. [[(imp)]] is important!
>> -----------------------------------end
>>
>> to html I get (copying from my browser)
>>
>> -----------------------------------start
>> 1 test
>>
>> 1:  <test>
>> 2:    <important/> <!--(ref:imp)-->
>> 3:  </test>
>>
>> Line no. nil is important!
>> -----------------------------------end
>>
>> I would like "<!--(ref:imp)-->" in line 2 of the block to be removed
>> from output and the last line to read "Line no. 2 is important!".
>>
>> Thanks!
>>
>> Martin
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

      reply	other threads:[~2010-03-23  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 12:52 [babel] bug exporting code blocks to html "Martin G. Skjæveland"
2010-03-22 18:40 ` Eric Schulte
2010-03-23  7:56   ` Carsten Dominik [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=8F994B21-14B3-4090-B4BC-22AF44D26DA9@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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
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).