From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: :EXPORT_FILE_NAME: in new exporter possible? Date: Mon, 25 Mar 2013 15:57:53 +0100 Message-ID: <87620fo7bi.fsf@bzg.ath.cx> References: <87620kwyuj.fsf@ericabrahamsen.net> <87k3p073ba.fsf@med.uni-goettingen.de> <8738vo1go1.fsf@bzg.ath.cx> <878v5chvdj.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58818) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UK8qV-0002Gg-81 for emacs-orgmode@gnu.org; Mon, 25 Mar 2013 10:58:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UK8qQ-0007Dy-Ab for emacs-orgmode@gnu.org; Mon, 25 Mar 2013 10:57:59 -0400 Received: from mail-we0-x22c.google.com ([2a00:1450:400c:c03::22c]:36373) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UK8qQ-0007Dg-3j for emacs-orgmode@gnu.org; Mon, 25 Mar 2013 10:57:54 -0400 Received: by mail-we0-f172.google.com with SMTP id r3so1431314wey.17 for ; Mon, 25 Mar 2013 07:57:53 -0700 (PDT) In-Reply-To: (Achim Gratz's message of "Mon, 25 Mar 2013 11:09:52 +0100") 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: > Am 25.03.2013 06:45, schrieb Bastien: >> Bastien writes: >> >>> This is a problem with Org -- I have a patch for this on my local >>> branch, but I will push this branch only tomorrow. >> >> Applied now, thanks. > > I'd like to ask you to revisit that change. I don't think the question of > whether #+SETUPFILE should be honored can be decided based on whether the > buffer is read-only. I acknowledge this is not the ideal solution but it is better than the current behavior. > I'm not entirely sure what Gnus does to trigger that foray into Org > (a quick glance in the documentation didn't show anything), but if > anything this indicates that we might need a "safe mode" for Org to > open untrusted files. Feel free to propose a better behavior here. -- Bastien