From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: [New Latex Exporter][BABEL][BUG] lists and inline src Date: Thu, 20 Sep 2012 08:28:40 -0600 Message-ID: <87zk4k4vl3.fsf@gmx.com> References: <87haqvf1e0.fsf@tajo.ucsd.edu> <87392eqv0e.fsf@bzg.ath.cx> <87627a3tk9.fsf@tajo.ucsd.edu> <878vc57et0.fsf_-_@gmx.com> <87vcf8dh93.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:56553) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEiIZ-0004Bz-NS for emacs-orgmode@gnu.org; Thu, 20 Sep 2012 11:04:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEiIT-0006Ck-JS for emacs-orgmode@gnu.org; Thu, 20 Sep 2012 11:04:15 -0400 Received: from mailout-eu.gmx.com ([213.165.64.43]:60077) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1TEiIT-0006CU-AR for emacs-orgmode@gnu.org; Thu, 20 Sep 2012 11:04:09 -0400 In-Reply-To: <87vcf8dh93.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 20 Sep 2012 14:13:28 +0200") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: cberry@tajo.ucsd.edu, emacs-orgmode@gnu.org Nicolas Goaziou writes: > Hello, > > Eric Schulte writes: > >> Does this problem present itself when you execute the inline code block >> interactively, or only when using the new latex exporter? If the later >> then it is a latex exporter bug and not a Babel bug. I've updated the >> subject line so that hopefully the latex export experts will notice this >> message. > > Indeed, the parser doesn't understand: > > - src_emacs-lisp{(+ 1 2)} > > That's a bug. The problem is related to > `org-babel-inline-src-block-regexp', which is used by the parser. More > accurately, at the beginning of that regexp, there is: > > "\\(?:^\\|[^-[:alnum:]]\\)\\(src_" > > Item contents start at the "s" from "src" but the regexp cannot match > from there. So, is "[^-[:alnum:]]" (and, therefore, > "\\(?:^\\|[^-[:alnum:]]\\)") really necessary? Why couldn't an user be > able to write an inline-src-block in the middle of something (for > example with raw results)? > Thanks for finding the source of this problem. The preceding character is checked so that inline source blocks can be commented. E.g., a user may want =src_sh{date}= to appear verbatim. Similarly if the preceding character is a letter e.g., notsrc_sh{date}, then the source block should not be executed. > > If checking the character before the inline-src-block object is > mandatory, I'll have to rely on an hack in org-element.el, along the > lines of: > > #+begin_src emacs-lisp > (save-excursion > (unless (bolp) (backward-char)) > (re-search-forward org-babel-inline-src-block-regexp nil limit) > ...) > #+end_src > > Obviously, I'd rather have the first part of the regexp removed. > > What do you think? > Ideally there would be a way to specify that *if* a character exists before the code block it must have some property, or to match the beginning of the element as another regexp option. I would say we can go ahead and remove the leading portion of the regexp, but as I recall I wrote it in response to legitimate complaints on the mailing list about the overly permissive behavior of inline source blocks, and I do not want for those problems to re-emerge. Best, > > > Regards, -- Eric Schulte http://cs.unm.edu/~eschulte