From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Prepare release 8.2.6 Date: Mon, 07 Apr 2014 12:19:41 +0200 Message-ID: <87ha65jvb6.fsf@gmail.com> References: <87ha6adikd.fsf@bzg.ath.cx> <87y4zj60vz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37779) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WX6eC-0004mZ-8U for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 06:19:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WX6e3-0007s4-7p for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 06:19:24 -0400 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:48732) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WX6e3-0007rw-0q for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 06:19:15 -0400 Received: by mail-wi0-f169.google.com with SMTP id hm4so5907355wib.2 for ; Mon, 07 Apr 2014 03:19:14 -0700 (PDT) In-Reply-To: (R. Michael Weylandt's message of "Sun, 6 Apr 2014 21:48:59 -0400") 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: "R. Michael Weylandt" Cc: "emacs-orgmode@gnu.org" Hello, "R. Michael Weylandt" writes: > I'm not as familiar with org-element-context, but I think the attached > is what you had in mind. Thanks. Comments follow. >> Another option for the problem at hand is to simply remove newline >> characters in inline source blocks before executing them. > > That might be better but would require a bit more work: It would require more work, but adding functions to `fill-nobreak-predicate' has a cost, too. It needs to be discussed, but I tend to think that it would be better to allow newlines characters in macros and inline babel calls, even if it means replacing them with a space when needed. > at present, > inline source blocks can't extend over multiple lines so org wouldn't > recognize a construct like > > src_python[:exports results]{1 + 2 + > 3 + 4} > > as an inline source block in the first place. Looking at > org-inline-src-block-regexp I'm not sure why though. Because there is everywhere [^...\n...], which means "no newline characters, please". The same goes for ".*?", as "." cannot match a newline character. > +(defun org-fill-element-nobreak-p () Technically, it is about "objects", not elements. So the function could be named `org-fill-objects-nobreak-p'. > + "Non-nil when a new line at point would break an element which > + cannot be split over multiple lines." Ditto. Also the first sentence in the docstring cannot be split into two lines. > + (member (car (org-element-context)) > + '(inline-src-block macro))) (memq (org-element-type (org-element-context)) ...) Regards, -- Nicolas Goaziou