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 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 file path setting in a subtree >>> export this afternoon. (on 8.0-pre) >>> >>> John >>> >>> On Mar 21, 2013 8:06 AM, "Rainer Stengele" <rainer.steng...@online.de >>> <mailto:rainer.steng...@online.de>> wrote: >>> >>> 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. >>> >>> Is this still possible with the new exporter? >>> How to deal with spaces in filepaths? >>> >>> Thanks, >>> Rainer >>> >>> Org-mode version 8.0-pre (release_8.0-pre-147-gfbb30a) >>> >>> >> C-c C-e C-s h o >> does save the file under the correct path. >> Unfortunately the "open" part for the html file fails: >> >> >> Wrote //max2008/diplan/0PROJEKT/Kunden/ROB/01 >> Kommunikation/Statusprotokolle/Status-ROB-Electronic-20130321b.html >> eval: ShellExecute failed: Das System kann die angegebene Datei nicht finden >> >> which translated means: The system cannot find the file >> > > Again, I'd try just removing all the path and seeing if Emacs can find > it then. Mine opens in a buffer with C-c C-e h o, by the way. I > probably need to tell Emacs to use a browser somehow. > >> 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 shouldn't it? > > Not sure about the noexport tag. Perhaps manually telling it to export > a subtree overrides? > > If you export a higher level subtree or the document, will it omit? > >> >> Thanks, Rainer > >
Using :EXPORT_FILE_NAME: x:/folder1/folder2/file.html works. //server/share paths do not work. 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. Thanks, Rainer
