[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Using link abbrevations for EXPORT_FILE_NAME ?
From: |
Nicolas Goaziou |
Subject: |
Re: [O] Using link abbrevations for EXPORT_FILE_NAME ? |
Date: |
Tue, 10 Nov 2015 18:22:49 +0100 |
AW <address@hidden> writes:
> Background: I'm using orgmode on different platforms, Windows and Linux. So I
> (being very proud of that!) wrote an if-clause:
>
> (setq org-link-abbrev-alist
> (if (eq system-type 'windows-nt)
> '(("foopath" . "//Sbs2011/ra2000/Bilder/2010/271-2011/%s")
> )
> '(("foopath" . "/home/AW/some/path/2011-271-project/%s")))
>
>
>
> So on Windows foopath becomes the first path, and on Linux the second and all
> my links in the orgmode files work on both platforms.
>
> A cheap solution for EXPORT_FILE_NAME: just have two lines and comment out
> the
> wrong one!
>
> -----------------
> * Subtree to be exported
> :PROPERTIES:
> # :EXPORT_FILE_NAME: //Sbs2011/ra2000/Bilder/2010/271-2011/filename
> :EXPORT_FILE_NAME: /home/AW/some/path/2011-271-project/filename
> :EXPORT_TITLE:
> :END:
>
> foo
>
> -----------------
>
> But comment seems not to work inside properties.
>
> However, :EXPORT_FILE_DIRECTORY: would only improve _my_ situation, if I
> could
> make it dependend on a condition.
At this point, I suggest to write your own `org-export-subtree-to'
function. You can have a look at, e.g., `org-html-export-to-html' and
override the call to `org-export-output-file-name'.
Elisp should provide the flexibility Org cannot offer.
Regards,