From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: Args out of range: #, 0, 1 Date: Wed, 14 Jan 2015 09:27:22 +0100 Message-ID: <86sifdzs0l.fsf@example.com> References: <86iogara9o.fsf@example.com> <874mrulluj.fsf@yahoo.fr> <86r3uyo1ni.fsf@example.com> <87387ejqb2.fsf@yahoo.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Nicolas Richard wrote: > Sebastien Vauban writes: >> This still leaves me with one question: how do we reproduce the >> problem? What's the trigger for it? > > Mostly luck. i.e. you need to have called a function that callled > string-match on a string, with a regexp containing (at least) > 4 grouping constructs, and the 4th matched at the beginning of that > string (beginning position 0) but only one character (end position > 1). And then later call org-babel-demarcate-block. Between the two, > many things may have happened as long as the match data was preserved. OK. I understand now I had problems figuring out what the trigger was for the problem... >> PS- @NicolasG, thanks for fixing it... > > And also thanks for mentionning org-babel-src-block-regexp... and > completely rewriting org-babel-where-is-src-block-head. Very > impressive! Yep, that was quick (as very often). Best regards, Seb -- Sebastien Vauban