From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Using link abbrevations for EXPORT_FILE_NAME ? Date: Sat, 14 Nov 2015 19:11:24 +0000 Message-ID: <878u60mm5f.fsf@gmail.com> References: <8038470.jhX8ZjFPSM@linux-k2bd.site> <87bnb471d0.fsf@nicolasgoaziou.fr> <56409754.6020605@iancu.ch> <877fll566p.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxgEW-0008MT-FI for emacs-orgmode@gnu.org; Sat, 14 Nov 2015 14:11:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxgES-0006id-BE for emacs-orgmode@gnu.org; Sat, 14 Nov 2015 14:11:32 -0500 Received: from mail-wm0-x233.google.com ([2a00:1450:400c:c09::233]:34989) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxgES-0006iX-52 for emacs-orgmode@gnu.org; Sat, 14 Nov 2015 14:11:28 -0500 Received: by wmdw130 with SMTP id w130so66291805wmd.0 for ; Sat, 14 Nov 2015 11:11:27 -0800 (PST) In-Reply-To: <877fll566p.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou , Stelian Iancu Cc: AW , emacs-orgmode@gnu.org Hi Nicolas, 2015ko azaroak 14an, Nicolas Goaziou-ek idatzi zuen: >=20 > Thanks for your feedback. >=20 > 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=E2=80=99m not a user of multi-file export, but here=E2=80=99s the kind of= scenario I imagine arising (I=E2=80=99ve used an abbreviated syntax for specifying properties; hopefully it=E2=80=99s clear): a.org ,---- | * A project | ** One file | :EFN: foo.html |=20 | A link to [[bar/page.html]] |=20 | ** Another file | :EFN: bar/page.html |=20 | Interesting content. `---- b.org ,---- | * A version of the project for mobile | :EFD: mobile | :CSS: mobile.css |=20 | #+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 =E2=80=93 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, --=20 Aaron Ecay