From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [PATCH] ob-tangle: Correctly process tangling of single source block Date: Sat, 02 Mar 2013 17:15:47 +0100 Message-ID: <877glp4r4m.fsf@bzg.ath.cx> References: <20130115192641.734AA1BA269D@BigDog.local> <20130115202857.GA25834@BigDog.local> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59650) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UBqlL-00089h-3b for emacs-orgmode@gnu.org; Sat, 02 Mar 2013 13:02:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UBqlH-0006F1-SM for emacs-orgmode@gnu.org; Sat, 02 Mar 2013 13:02:23 -0500 Received: from mail-we0-x22a.google.com ([2a00:1450:400c:c03::22a]:54422) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UBqlH-0006Ei-Mu for emacs-orgmode@gnu.org; Sat, 02 Mar 2013 13:02:19 -0500 Received: by mail-we0-f170.google.com with SMTP id z53so3365577wey.15 for ; Sat, 02 Mar 2013 10:02:18 -0800 (PST) In-Reply-To: <20130115202857.GA25834@BigDog.local> (Rick Frankel's message of "Tue, 15 Jan 2013 15:28:57 -0500") 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: Rick Frankel Cc: emacs-orgmode@gnu.org Hi Rick, Rick Frankel writes: > Sorry, subject didn't get properly added: > ---------------- > > * lisp/ob-tangle.el > (org-babel-tangle): > - remove un-executed attempt to ask user for file-name if > tangling a single block (`:tangle' always has a value) > - change handling of block accumulation > > (org-babel-tangle-collect-block): new function to collect a single block > > When attempting to tangle a single block, `org-babel-tangle' would use > `narrow-to-region', causing any header arguments not on the > "#+BEGIN_SRC" line to be excluded from the tangled file. I finally applied a similar patch to fix this issue. Thanks for catching this! -- Bastien