From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Clemente Subject: bug in org-element--object-lex seen when exporting (Invalid search bound, wrong side of point) Date: Sun, 23 Oct 2016 17:22:55 +0200 Message-ID: <87lgxfm6nk.wl-n142857@gmail.com> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-2022-JP Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47527) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1byKbo-000054-60 for emacs-orgmode@gnu.org; Sun, 23 Oct 2016 11:22:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1byKbl-00078Y-0D for emacs-orgmode@gnu.org; Sun, 23 Oct 2016 11:22:48 -0400 Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]:38613) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1byKbk-000785-Q5 for emacs-orgmode@gnu.org; Sun, 23 Oct 2016 11:22:44 -0400 Received: by mail-wm0-x232.google.com with SMTP id c78so71259680wme.1 for ; Sun, 23 Oct 2016 08:22:44 -0700 (PDT) Received: from noad.gmail.com ([92.60.17.22]) by smtp.gmail.com with ESMTPSA id yo1sm14296434wjc.16.2016.10.23.08.22.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Oct 2016 08:22:42 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hi. I describe a rare bug seen in today's org-mode (8.3.6) running in emacs 26.0.50.1. 1. emacs -Q, and load org-mode 2. Use this file (two lines): * <<>> a-bug 3. export to HTML (C-c C-e h h) I got: Debugger entered--Lisp error: (error "Invalid search bound (wrong side of point)") re-search-forward("\\(?:[_^][-{(*+.,[:alnum:]]\\)\\|[*~=+_/][^ \n]\\|\\<\\(?:b\\(?:bdb\\|ibtex\\)\\|doi\\|elisp\\|f\\(?:ile\\(?:\\+\\(?:\\(?:emac\\|sy\\)s\\)\\)?\\|tp\\)\\|h\\(?:elp\\|ttps?\\)\\|i\\(?:d\\|nfo\\|rc\\)\\|m\\(?:ailto\\|essage\\)\\|news\\|shell\\|tel\\|w\\(?:3m\\|l\\)\\):\\|\\[\\(?:fn:\\|\\[\\|[0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}\\|[0-9]*\\(?:%\\|/[0-9]*\\)\\]\\)\\|@@\\|{{{\\|<\\(?:%%\\|<\\|[0-9]\\|\\(?:b\\(?:bdb\\|ibtex\\)\\|doi\\|elisp\\|f\\(?:ile\\(?:\\+\\(?:\\(?:emac\\|sy\\)s\\)\\)?\\|tp\\)\\|h\\(?:elp\\|ttps?\\)\\|i\\(?:d\\|nfo\\|rc\\)\\|m\\(?:ailto\\|essage\\)\\|news\\|shell\\|tel\\|w\\(?:3m\\|l\\)\\)\\)\\|\\$\\|\\\\\\(?:[a-zA-Z[(]\\|\\\\[ ]*$\\|_ +\\)\\|\\(?:call\\|src\\)_" 13 t) org-element--object-lex((bold code entity export-snippet footnote-reference inline-babel-call inline-src-block italic line-break latex-fragment link macro radio-target statistics-cookie strike-through subscript superscript target timestamp underline verbatim)) org-element--parse-objects(13 19 (paragraph (:begin 13 :end 19 :contents-begin 13 :contents-end 19 :post-blank 0 :post-affiliated 13)) (bold code entity export-snippet footnote-reference inline-babel-call inline-src-block italic line-break latex-fragment link macro radio-target statistics-cookie strike-through subscript superscript target timestamp underline verbatim)) org-element--parse-elements(13 19 planning nil nil nil (section (:begin 13 :end 19 :contents-begin 13 :contents-end 19 :post-blank 0 :post-affiliated 13))) org-element--parse-elements(13 19 section nil nil nil (headline (:raw-value "<<>>" :begin 2 :end 19 :pre-blank 1 :contents-begin 13 :contents-end 19 :level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 0 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 2 :title ((radio-target (:begin 4 :end 11 :contents-begin 7 :contents-end 8 :post-blank 0 :value "a" :parent #0) #("a" 0 1 (:parent #3))))))) org-element--parse-elements(2 19 first-section nil nil nil (org-data nil)) org-element-parse-buffer(nil nil) … It happens with one-letter radios. I found it because I had <<>> and r-cran in the same file. Greetings, Daniel