From: "Eric Schulte" <schulte.eric@gmail.com>
To: maurizio.vitale@polymath-solutions.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] problems with org-babel-src-block-regexp (full text)
Date: Mon, 22 Mar 2010 11:27:00 -0600 [thread overview]
Message-ID: <87tys8468r.fsf@gmail.com> (raw)
In-Reply-To: <87y6hyhj3m.fsf@cuma.i-did-not-set--mail-host-address--so-tickle-me> (Maurizio Vitale's message of "Thu, 11 Mar 2010 12:19:09 -0500")
Hi Maurizio,
Thanks for finding and demonstrating this bug. It should now be fixed.
Best -- Eric
Maurizio Vitale
<mav@cuma.i-did-not-set--mail-host-address--so-tickle-me> writes:
> [sorry for the double posting, but the control char in the regexp
> prevented the full message from appearing. This is what I meant to send]
>
> There're problems with org-babel-src-block-regexp when the src block
> contains the block delimiters (for instance in strings or comments).
>
> Granted, this is an uncommon occurrence (which I discovered by accident)
> editing an org-file containing elisp code that needed to insert
> #+begin_src...#+end_src pairs, but if it is not too difficult to fix it
> would be nice to have a more useful behaviour.
>
> This is my setting (replaced 0x0 with ^@ to avoid posting problems):
> org-babel-src-block-regexp is a variable defined in `org-babel.el'.
> Its value is
> "^[ ]*#\\+begin_src[ ]+\\(python\\|sh\\|emacs-lisp\\)[ ]*\\([^\":\n]*\"[^\"\n*]*\"[^\":\n]*\\|[^\":\n]*\\)\\([^\n]*\\)\n\\([^^@]+?\\)#\\+end_src"
>
> And these are two test cases. I'm particularly puzzled by the first,
> because the regexp seems to be anchored to the begin of line and hence
> it shouldn't match the begin_src inside the string.
> For end_src, it should probably be anchored to the begin of line.
>
> #+begin_src emacs-lisp
> ;;; evaluating the following C-x C-e with the point at the end is ok
> (org-babel-where-is-src-block-head)
> (defun foo () (insert "#+begin_src emacs-lisp"))
> ;;; evaluating the following C-x C-e with the point at the end is not ok
> (org-babel-where-is-src-block-head)
> #+end_src
>
> #+begin_src emacs-lisp
> ;;; evaluating the following C-x C-e with the point at the end is ok
> (org-babel-where-is-src-block-head)
> (defun foo () (insert "#+end_src emacs-lisp"))
> ;;; evaluating the following C-x C-e with the point at the end is not ok
> (org-babel-where-is-src-block-head)
> #+end_src
>
> Best regards,
>
> Maurizio
>
>
>
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2010-03-22 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 17:02 [babel] problems with org-babel-src-block-regexp Maurizio Vitale
2010-03-11 17:19 ` [babel] problems with org-babel-src-block-regexp (full text) Maurizio Vitale
2010-03-22 17:27 ` 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=87tys8468r.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maurizio.vitale@polymath-solutions.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).