From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Automatically adding local variables to tangled file Date: Sat, 08 Jun 2013 15:17:40 -0600 Message-ID: <87r4gcl2tn.fsf@gmail.com> References: <878v2omz5g.fsf@krugs.de> <51af4bfd.0c95ec0a.2372.097e@mx.google.com> <87ehcf6xey.fsf@gmail.com> <87ehcewdye.fsf@krugs.de> <8738ssmoyl.fsf@gmail.com> <87y5ak1fp8.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51395) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UlQWy-0007Fh-AF for emacs-orgmode@gnu.org; Sat, 08 Jun 2013 17:18:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UlQWw-0000SZ-TK for emacs-orgmode@gnu.org; Sat, 08 Jun 2013 17:18:36 -0400 Received: from mail-pb0-x22c.google.com ([2607:f8b0:400e:c01::22c]:49331) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UlQWw-0000ST-MG for emacs-orgmode@gnu.org; Sat, 08 Jun 2013 17:18:34 -0400 Received: by mail-pb0-f44.google.com with SMTP id uo1so1190390pbc.31 for ; Sat, 08 Jun 2013 14:18:33 -0700 (PDT) In-Reply-To: <87y5ak1fp8.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 08 Jun 2013 22:59:47 +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: Achim Gratz Cc: emacs-orgmode@gnu.org Achim Gratz writes: > Eric Schulte writes: >> I've added a :tangle-mode header argument which may be used to control >> the permissions of tangled files. See the manual for instructions on >> it's usage. > > The change in org-babel-read now requires that :shebang values are > quoted. Oh, I should have realized that shebang values weren't normally quoted. I've reverted this portion of my tangle-mode patch, so the reader no longer tries to read #-prefixed strings a elisp. Hopefully this won't affect too many people. > I've changed the test file accordingly as otherwise the file couldn't > be ingested. In general I'd suggest that reading header arguments as > eLisp should at be protected against an error propagating out of the > reader function. > I think in most cases it would be better to know if an error has occurred than not, and I think any sort of message output would quickly be overwritten by the remainder of the code block execution. Thanks for catching this quickly! > > > Regards, > Achim. -- Eric Schulte http://cs.unm.edu/~eschulte