emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@Nexgo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: :EXPORT_FILE_NAME: in new exporter possible?
Date: Mon, 25 Mar 2013 11:09:52 +0100	[thread overview]
Message-ID: <kip7oj$g7$1@ger.gmane.org> (raw)
In-Reply-To: <878v5chvdj.fsf@bzg.ath.cx>

Am 25.03.2013 06:45, schrieb Bastien:
> Bastien <bzg@altern.org> 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'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.


Regards,
-- 
Achim.

(on the road :-)

  reply	other threads:[~2013-03-25 10:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 13:06 :EXPORT_FILE_NAME: in new exporter possible? Rainer Stengele
2013-03-21 15:34 ` Eric Abrahamsen
2013-03-21 23:15   ` Andreas Leha
2013-03-21 23:23     ` Bastien
2013-03-25  5:45       ` Bastien
2013-03-25 10:09         ` Achim Gratz [this message]
2013-03-25 14:57           ` Bastien
2013-03-25 15:09             ` Achim Gratz
2013-03-25 15:54               ` Bastien
2013-03-25 16:13                 ` Achim Gratz
2013-03-25 16:57                   ` Bastien
2013-03-25 17:00                     ` Bastien
2013-03-25 17:39                     ` Achim Gratz
2013-03-25 18:52                       ` Bastien
2013-03-22  0:20 ` John Hendy
2013-03-22  7:41   ` Rainer Stengele
2013-03-22 14:51     ` John Hendy
2013-03-22 16:04       ` Rainer Stengele
2013-03-22 18:20         ` Nicolas Goaziou
2013-03-22 14:58     ` Nicolas Goaziou
2013-03-22 15:21       ` Rainer Stengele

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='kip7oj$g7$1@ger.gmane.org' \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).