emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, Stelian Iancu <si@siancu.net>
Cc: AW <alexander.willand@t-online.de>, emacs-orgmode@gnu.org
Subject: Re: Using link abbrevations for EXPORT_FILE_NAME ?
Date: Sat, 14 Nov 2015 19:11:24 +0000	[thread overview]
Message-ID: <878u60mm5f.fsf@gmail.com> (raw)
In-Reply-To: <877fll566p.fsf@nicolasgoaziou.fr>

Hi Nicolas,

2015ko azaroak 14an, Nicolas Goaziou-ek idatzi zuen:
> 
> Thanks for your feedback.
> 
> Any other feedback on the "EXPORT_FILE_DIRECTORY" feature?

In an earlier email you wrote:

> When set, e.g. to "dir", assuming EXPORT_FILE_NAME is set to "foo/file",
> export file name becomes "dir/file".

Would it make more sense to concatenate the properties: dir/foo/file?
I’m not a user of multi-file export, but here’s the kind of scenario
I imagine arising (I’ve used an abbreviated syntax for specifying
properties; hopefully it’s clear):

a.org

,----
| * A project
| ** One file
| :EFN: foo.html
| 
| A link to [[bar/page.html]]
| 
| ** Another file
| :EFN: bar/page.html
| 
| Interesting content.
`----

b.org

,----
| * A version of the project for mobile
| :EFD: mobile
| :CSS: mobile.css
| 
| #+include: a.org
`----

In this case, the link will break.  (Maybe the link could be made to
work in org by using e.g. an ID link – but someone still might want the
mobile version of bar/page.html to live at mobile/bar/page.html not
mobile/page.html).

Maybe you have a different kind of use-case in mind?

Thanks,

-- 
Aaron Ecay

next prev parent reply	other threads:[~2015-11-14 19:11 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 [this message]
2015-11-09 21:03   ` AW
2015-11-10 17:22     ` Nicolas Goaziou

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=878u60mm5f.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=alexander.willand@t-online.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=si@siancu.net \
    /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

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).