emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Lawrence Mitchell <wence@gmx.li>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH 1/2] lisp/ob.el: Fix org-babel-result-regexp to match users
Date: Thu, 02 Jun 2011 12:20:03 -0600	[thread overview]
Message-ID: <874o48ay36.fsf@gmail.com> (raw)
In-Reply-To: 1307009045-10010-1-git-send-email-wence@gmx.li

Applied, Thanks -- Eric

Lawrence Mitchell <wence@gmx.li> writes:

> * lisp/ob.el (org-babel-result-regexp): Use non-shy group around
> org-babel-data-names.
>
> By default regexp-opt returns a shy group around its arguments.  But
> users of org-babel-result-regexp expect the third match-string to
> contain the hash.  With a shy group, the second match-string contains
> the hash.
> ---
>  lisp/ob.el |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lisp/ob.el b/lisp/ob.el
> index 27f005c..e1f4372 100644
> --- a/lisp/ob.el
> +++ b/lisp/ob.el
> @@ -310,7 +310,7 @@ specific header arguments as well.")
>  
>  (defvar org-babel-result-regexp
>    (concat "^[ \t]*#\\+"
> -	  (regexp-opt org-babel-data-names)
> +	  (regexp-opt org-babel-data-names t)
>  	  "\\(\\[\\([[:alnum:]]+\\)\\]\\)?\\:[ \t]*")
>    "Regular expression used to match result lines.
>  If the results are associated with a hash key then the hash will

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 10:04 [PATCH 1/2] lisp/ob.el: Fix org-babel-result-regexp to match users Lawrence Mitchell
2011-06-02 10:04 ` [PATCH 2/2] lisp/ob.el: Don't modify babel info when hashing it Lawrence Mitchell
2011-06-02 18:22   ` Eric Schulte
2011-06-03  8:33     ` Lawrence Mitchell
2011-06-02 18:20 ` Eric Schulte [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=874o48ay36.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wence@gmx.li \
    /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).