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 19:52:24 +0100 Message-ID: <87ehf371nb.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> <87620fo7bi.fsf@bzg.ath.cx> <87wqsvmq48.fsf@bzg.ath.cx> <87vc8fa03f.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKCVe-00005B-Ao for emacs-orgmode@gnu.org; Mon, 25 Mar 2013 14:52:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UKCVQ-0007h1-Cw for emacs-orgmode@gnu.org; Mon, 25 Mar 2013 14:52:42 -0400 Received: from mail-we0-x22a.google.com ([2a00:1450:400c:c03::22a]:36981) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKCVQ-0007gr-6D for emacs-orgmode@gnu.org; Mon, 25 Mar 2013 14:52:28 -0400 Received: by mail-we0-f170.google.com with SMTP id z2so3868744wey.15 for ; Mon, 25 Mar 2013 11:52:27 -0700 (PDT) In-Reply-To: (Achim Gratz's message of "Mon, 25 Mar 2013 18:39:15 +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: > talking different implementations of the second point above. But given > that Gnus expects to use a major mode with no setup, why not give them > this: > > (define-derived-mode org-safe-mode org-mode "Org-Safe" > ;; docstring etc. > ) My feeling is that having a new mode just for preventing users to read setup files is too much. Do you have an idea on how to make org-safe-mode not too heavy? > and then conditionalize on the value of mode-name instead of an extra > variable that they should bind? The extra defcustom is useful IMHO: the problem we have in Gnus, users will have it anytime when opening a file that is not theirs and that contains a #+SETUPFILE (e.g. files in Worg.) Paranoids (or those who don't use #+SETUPFILE) will probably want to be asked when Org tries to read an arbitrary file in their paths. Others will just set this to (setq org-read-setup-file t). So even if we have a org-safe-mode, I don't see how it will spare us with the cost of a new option. > This would also help to later add more > "safe" functionality without changing things again and again in Org, Gnus > or elsewhere. For example, not running source blocks (we already have a > way of doing that for export, so it shouldn't be hard to add this). Yeah, I see where you go, but you know my dreadful tendency to favor actual things against potential ones, and to go the ugly way rather than going the clean one :) Half-joking -- the thing is I really don't know what org-safe-mode would look like, where else it would be useful, and how it spares us the option for paranoid. If you can help on each of these three points, that'd great (no hurry, as I don't know if I'll have time to follow this thread in the next few days.) > I'm not arguing against your fix, I'd just prefer we'd start with something > we just need to extend into a proper safe-mode instead of having to start > again from scratch after hot-fixing this unfortunate interaction with Gnus > (and I still don't know how Gnus gets there, anyway). See my second patch, it gives directions on the Gnus side. -- Bastien