emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Bug in org-src.el?
Date: Fri, 01 Feb 2013 15:55:25 +0100	[thread overview]
Message-ID: <8738xgf5ia.fsf@googlemail.com> (raw)


Hi List, 

when I export a (bit complicated) PicoLisp source block with ':results
html', I get an error:

,----------------------------------------------------
| error: "Invalid search bound (wrong side of point)"
`----------------------------------------------------

The error happens in org-src.el in the function:

,-------------------------------------------
| (defun org-escape-code-in-region (beg end)
|   "Escape lines between BEG and END.
`-------------------------------------------

because beg and end are interchanged, i.e. the function is called with 

,--------------------------------------
| (org-escape-code-in-region 2921 2908)
`--------------------------------------

when 

,------------
| +results:
| +BEGIN_HTML # char 2908 at beginning-of-line
| +END_HTML   # char 2921 at beginning-of-line
`------------

Here is the backtrace:

,------------------------------------------------------------------------
| Debugger entered--Lisp error: (error "Invalid search bound (wrong side
|   of point)") re-search-forward("^[ ]*,?\\(\\*\\|#\\+\\)" #<marker at
|   2908 in picodoc-test.org> t) (while (re-search-forward "^[
|   ]*,?\\(\\*\\|#\\+\\)" end t) (replace-match ",\\1" nil nil nil 1))
|   (save-excursion (goto-char beg) (while (re-search-forward "^[
|   ]*,?\\(\\*\\|#\\+\\)" end t) (replace-match ",\\1" nil nil nil 1)))
|   org-escape-code-in-region(2921 #<marker at 2908 in picodoc-test.org>)
| 
|   #[(start finish &optional no-escape) "b\210
|    \305Pc\210\nb\210\305Pc\210\f\204\306`\"\210b\210\307 b\210\310
|    \211\207" [end finish beg start no-escape "\n"
|    org-escape-code-in-region point-at-eol point-marker]
|    3]("#+BEGIN_HTML" "#+END_HTML")
| 
|   org-babel-insert-result(nil ("html" "output" "replace") ("picolisp" "
|   ... [omitted] ))
| 
|   org-babel-execute-src-block-maybe()
|   org-babel-execute-maybe()
|   org-babel-execute-safely-maybe()
|   run-hook-with-args-until-success(org-babel-execute-safely-maybe)
|   org-ctrl-c-ctrl-c(nil)
|   call-interactively(org-ctrl-c-ctrl-c nil nil)
`------------------------------------------------------------------------


and the system-info:

,-------------------------------------------------------------------
| Org-mode version 7.9.3e (7.9.3e-897-g787a07 @
| /home/tj/gitclone/org-mode/lisp/)
| 
| GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of
| 2013-01-20 on eric
`-------------------------------------------------------------------


-- 
cheers,
Thorsten

             reply	other threads:[~2013-02-01 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 14:55 Thorsten Jolitz [this message]
2013-02-11 14:45 ` Bug in org-src.el? Bastien
2013-02-12 16:19   ` Thorsten Jolitz
2013-02-12 16:49     ` Bastien

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=8738xgf5ia.fsf@googlemail.com \
    --to=tjolitz@googlemail.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).