Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Bastien
Bastien b...@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. -- Bastien

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Achim Gratz
Am 25.03.2013 06:45, schrieb Bastien: Bastien b...@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

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Bastien
Achim Gratz strom...@nexgo.de writes: Am 25.03.2013 06:45, schrieb Bastien: Bastien b...@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

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Achim Gratz
Am 25.03.2013 15:57, schrieb Bastien: 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

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Bastien
Achim Gratz strom...@nexgo.de writes: As I said, I don't even know why Gnus decides it should treat this mail as an Org file. From the sources of Gnus, it appears that it should only do this if the MIME type was text/x-org. Rainers mail didn't have this MIME type nor was it a multipart MIME

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Achim Gratz
Am 25.03.2013 16:54, schrieb Bastien: What about this patch? I don't think Gnus should be switching major modes just to get fontification and definitely not with Org. The change in Gnus is then trivial (see other patch). Again, I'd rather have a derived mode (org-safe-mode, perhaps) that

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Bastien
Achim Gratz strom...@nexgo.de writes: Am 25.03.2013 16:54, schrieb Bastien: What about this patch? I don't think Gnus should be switching major modes just to get fontification and definitely not with Org. But it does. The change in Gnus is then trivial (see other patch). Again, I'd

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Bastien
Bastien b...@altern.org writes: Evaluating it against your ideal fix will obvisouly make it look rudimentary. But I think it's better than the current situation. PS: that's not to say that the door is closed for your ideal fix, of course. But I favor existing patches vs. ideal solutions. --

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Achim Gratz
Am 25.03.2013 17:57, schrieb Bastien: Can you evaluate my patch against the current state of affair? The current state of affairs is this: 1. Gnus is doing something it shouldn't do, even though it may once have been OK or at least not dangerous. 2. Org doesn't have something that can

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-25 Thread Bastien
Achim Gratz strom...@nexgo.de 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

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-22 Thread Rainer Stengele
Am 22.03.2013 01:20, schrieb John Hendy: Can you try using just file and file.html (but without quotes) and see I'd it pops out in your working directory ? Your current path looks like a Windows server share which might be an issue. Even if not, simplifying the path might be one place to

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-22 Thread John Hendy
On Fri, Mar 22, 2013 at 2:41 AM, Rainer Stengele rainer.steng...@online.de wrote: Am 22.03.2013 01:20, schrieb John Hendy: Can you try using just file and file.html (but without quotes) and see I'd it pops out in your working directory ? Your current path looks like a Windows server share

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-22 Thread Nicolas Goaziou
Hello, Rainer Stengele rainer.steng...@online.de writes: Another funny issue here is that for the test my exported subtree has the tag :noexport: My setting is: org-export-exclude-tags is a variable defined in `ox.el'. Its value is (noexport) So the export shouldn't export that subtree

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-22 Thread Rainer Stengele
Am 22.03.2013 15:58, schrieb Nicolas Goaziou: Hello, Rainer Stengele rainer.steng...@online.de writes: Another funny issue here is that for the test my exported subtree has the tag :noexport: My setting is: org-export-exclude-tags is a variable defined in `ox.el'. Its value is

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-22 Thread Rainer Stengele
Am 22.03.2013 15:51, schrieb John Hendy: On Fri, Mar 22, 2013 at 2:41 AM, Rainer Stengele rainer.steng...@online.de wrote: Am 22.03.2013 01:20, schrieb John Hendy: Can you try using just file and file.html (but without quotes) and see I'd it pops out in your working directory ? Your current

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-22 Thread Nicolas Goaziou
Hello, Rainer Stengele rainer.steng...@online.de writes: Secondly, the :EXPORT_FILE_NAME: property is only followed when doing subtree export. It is ignored for buffer export no matter where I put the property definition. Please help. There is no buffer keyword equivalent to

[O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-21 Thread Rainer Stengele
Hi, Exporting to HTML I cannot get EXPORT_FILE_NAME to work: :PROPERTIES: :VISIBILITY: folded #+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org #+CATEGORY: ROB :EXPORT_FILE_NAME: //max2008/diplan/0PROJEKT/Kunden/ROB/Status-ROB-Electronic-20130321b.html :END: :EXPORT_FILE_NAME: entry is in one line.

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-21 Thread Eric Abrahamsen
Rainer Stengele rainer.steng...@online.de writes: Hi, Exporting to HTML I cannot get EXPORT_FILE_NAME to work: :PROPERTIES: :VISIBILITY: folded #+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org #+CATEGORY: ROB :EXPORT_FILE_NAME:

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-21 Thread Andreas Leha
Eric Abrahamsen e...@ericabrahamsen.net writes: Rainer Stengele rainer.steng...@online.de writes: Hi, Exporting to HTML I cannot get EXPORT_FILE_NAME to work: :PROPERTIES: :VISIBILITY: folded #+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org #+CATEGORY: ROB :EXPORT_FILE_NAME:

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-21 Thread Bastien
Hi Andreas and Eric, Andreas Leha andreas.l...@med.uni-goettingen.de writes: It was the same for me and this should definitely not happen. So, I am also 'a little worried'. Is this a problem with my gnus setup or an orgmode problem? This is a problem with Org -- I have a patch for this on

Re: [O] :EXPORT_FILE_NAME: in new exporter possible?

2013-03-21 Thread John Hendy
Can you try using just file and file.html (but without quotes) and see I'd it pops out in your working directory ? Your current path looks like a Windows server share which might be an issue. Even if not, simplifying the path might be one place to start . I just successfully exported using the