From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: AW <alexander.willand@t-online.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using link abbrevations for EXPORT_FILE_NAME ?
Date: Tue, 10 Nov 2015 18:22:49 +0100 [thread overview]
Message-ID: <8737wdwyza.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1680721.RnRcZu7HBl@linux-k2bd.site> (AW's message of "Mon, 09 Nov 2015 22:03:07 +0100")
AW <alexander.willand@t-online.de> 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,
prev parent reply other threads:[~2015-11-10 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 14:07 Using link abbrevations for EXPORT_FILE_NAME ? AW
2015-11-08 19:11 ` Nicolas Goaziou
2015-11-09 12:53 ` Stelian Iancu
2015-11-14 8:35 ` Nicolas Goaziou
2015-11-14 19:11 ` Aaron Ecay
2015-11-09 21:03 ` AW
2015-11-10 17:22 ` Nicolas Goaziou [this message]
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=8737wdwyza.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=alexander.willand@t-online.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).