From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Fraga Subject: Re: Beamer specific setupfile? Date: Wed, 25 Apr 2012 18:29:02 +0930 Message-ID: <874ns8mbl5.fsf@ucl.ac.uk> References: <5505.1331588928@alphaville> <6257.1331591439@alphaville> <6344.1331592244@alphaville> <8946.1331617585@alphaville> <878vhkmdkp.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33819) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SMy4G-0004km-UG for emacs-orgmode@gnu.org; Wed, 25 Apr 2012 04:59:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SMy4E-0004qU-N7 for emacs-orgmode@gnu.org; Wed, 25 Apr 2012 04:59:20 -0400 Received: from ch1ehsobe002.messaging.microsoft.com ([216.32.181.182]:42654 helo=ch1outboundpool.messaging.microsoft.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SMy4E-0004ps-Gx for emacs-orgmode@gnu.org; Wed, 25 Apr 2012 04:59:18 -0400 In-Reply-To: <878vhkmdkp.fsf@ucl.ac.uk> (Eric Fraga's message of "Wed, 25 Apr 2012 17:46:06 +0930") 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: nicholas.dokos@hp.com Cc: emacs-orgmode Eric Fraga writes: > Nick Dokos writes: > > [...] > >> org-infile-export-plist parses the current buffer and takes care of >> #+SETUPFILE: options (even recursive ones). It constructs an options > > This thread has been interesting for the effects it has had on my mail > reading experience. I use gnus and I have gnus configured to parse > *some* org syntax for fontifying messages. > > Interestingly, for these messages, org has tried to load in setup files! > With the original email message, I got the following error message: > > : Cannot read file "/home/xxx/org/aux/beamer-setup.org" > > and with the last line I quoted above from Nick's email, I got: > > : Cannot read file "/home/xxx/options (even recursive ones). It constructs an options" > > Fun! > > The question is: I believe that I have only configured gnus to do > fontification on source code blocks and a few other constructs. None of > the patterns I have specified includes general #+ lines. I cannot see > how these #+SETUPFILE lines are being interpreted. Any ideas of where > to look? It must (?) be an org issue, not gnus per se, I believe. > > Thanks, > eric Umm, it turns out that gnus does indeed catch lines that start with #+: ,---- | (org-meta-line | "^[ \t]*#\\+[[:alpha:]]+: " | "$" | mm-uu-org-src-code-block-extract)) `---- I need to investigate mm-uu-org-src-code-block-extract why this leads to setup file directives being followed. I do worry a little about security implications, although there probably aren't any. Side note: that regex doesn't capture all org mode directives! Apologies for the noise. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 : using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)