emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bryan Fink <bryan@basho.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ascii-export vs. "<<" and ">>" patch
Date: Fri, 8 Jan 2010 09:41:25 +0100	[thread overview]
Message-ID: <B67E7C3C-67D2-4ADE-BAD6-FECB73BEC2A2@gmail.com> (raw)
In-Reply-To: <473d01841001070930g19ba5a3l92beeb6a8a9c5478@mail.gmail.com>

Hi Bryan,

On Jan 7, 2010, at 6:30 PM, Bryan Fink wrote:

> Hi.  I'm using org-mode to write some documentation about Erlang
> modules.  Erlang's "binary" data type has a syntax like:
>
>   <<"this is binary data">>
>
> Org-mode's ascii-exporter in version 6.33f blindly strips all <<>>
> pairs from the file, leaving the text as
>
>   "this is binary data"
>
> which, unfortunately, is still valid Erlang syntax, but has a  
> different meaning.

First of all, you should have such code in code blocks like # 
+begin_src..., or, in running text, you need to protect it with  
something like =<<"this is binary data">>=.

Then things will work in HTML.

There is indeed a bug in ASCII export which does remove these without  
checking for protection - but I have just fixed that - so if you pull  
and protect, things should work.

HTH

- Carsten

>
> So, to help me and others write Erlang documentation in org-mode, I
> submit the patch attached to this email, which changes org-ascii.el
> such that it checks the org-protected text property before stripping
> <<>> characters, so examples marked as verbatim text should go
> untouched.
>
> -Bryan
> <0001-do-not-strip-and-from-protected-sections-during- 
> asci.patch>_______________________________________________
> 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-01-08  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 17:30 ascii-export vs. "<<" and ">>" patch Bryan Fink
2010-01-08  8:41 ` 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=B67E7C3C-67D2-4ADE-BAD6-FECB73BEC2A2@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bryan@basho.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).