emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: emacs-orgmode@gnu.org, mail@christianmoe.com
Subject: Re: [bug, babel] export corruption bug and 3 more bugs
Date: Thu, 02 Jun 2011 12:19:04 -0600	[thread overview]
Message-ID: <87aae0ay3d.fsf@gmail.com> (raw)
In-Reply-To: 87hb8glp7d.wl%dmaus@ictsoc.de

Hi David,

Sorry it took me a while to notice this thread -- incidentally after a
patch to this effect was shared by Lawrence Mitchell in a separate
thread.  I've just applied Lawrence's patch, which should resolve this
issue as well.

Please let me know if the problem remains.  Now that this thread is on
my radar I should be more attentive to it.

Thanks -- Eric

David Maus <dmaus@ictsoc.de> writes:

> At Wed, 25 May 2011 09:58:03 -0700,
> Samuel Wales wrote:
>>
>> Minimal .emacs and test case for export corruption bug.
>
> Okay, I can reproduce the args out of range with Emacs 22. Turns out
> that `regexp-opt` behaves different when creating
> `org-babel-result-regexp'.
>
> (regexp-opt org-babel-data-names)
>
> encloses the regexp for babel data names in a shy grouping construct
> in Emacs 23
>
> (regexp-opt org-babel-data-names) => "\\(?:DATA\\|RES\\(?:NAME\\|ULTS\\)\\|TBLNAME\\)"
>
> While it does not in Emacs 22
>
> (regexp-opt org-babel-data-names) => "DATA\\|RES\\(?:NAME\\|ULTS\\)\\|TBLNAME"
>
> Thus the literal string "results" in the example file is matched by
> Org Babel in `org-exp-res/src-name-cleanup'.
>
> Looks like setting up `org-babel-result-regexp' should do a check for
> the Emacs version and explictly add the shy grouping construct if
> version < 23 -- I'm really not familar with all the Babel parts so Cc:
> Erik Schulte who I assume knows Babel better than me.
>
> I'll check the other (compatibilty) problems during the weekend.
>
> Best,
>   -- David
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  parent reply	other threads:[~2011-06-02 18:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 16:58 [bug] export corruption bug and 3 more bugs Samuel Wales
2011-05-27  4:52 ` [bug, babel] " David Maus
2011-05-27 14:15   ` Samuel Wales
2011-05-27 14:47     ` [bug, babel][OT] " Jambunathan K
2011-05-27 15:01       ` Samuel Wales
2011-05-27 15:22         ` Jambunathan K
2011-06-01  7:16     ` [bug, babel] " David Maus
2011-06-02  6:12       ` Samuel Wales
2011-06-02 18:19   ` Eric Schulte [this message]
2011-06-02 20:37     ` Samuel Wales
2011-06-02 21:00       ` Eric Schulte

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=87aae0ay3d.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.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).