> The :include property may be used to include extra files. Its value
> may be a list of filenames to include. The filenames are considered
> relative to the base directory.
D'oh! Begging your pardon.
> (setq org-publish-project-alist
> '(("test-htaccess"
> :base-directory
Jeff Horn writes:
>> The problem is, that `org-publish-get-base-files' seems to put basenames
>> into `org-publish-temp-files' instead of absolute paths.
>
> Ah. Thanks for the info. That makes sense.
>
>> I'm currently working on it (probably my fault anyway).
>
> I really appreciate your help,
Jeff Horn writes:
> We had a bit of a discussion off list, but I still haven't been able
> to get the behavior I am after. See below.
>
>
> When I make the change as you have suggested above, I get the original
> file not found error.
>
> From the *Messages* buffer:
>
> The problem is, that `org-publish-get-base-files' seems to put basenames
> into `org-publish-temp-files' instead of absolute paths.
Ah. Thanks for the info. That makes sense.
> I'm currently working on it (probably my fault anyway).
I really appreciate your help, and I don't blame anyone for
We had a bit of a discussion off list, but I still haven't been able
to get the behavior I am after. See below.
When I make the change as you have suggested above, I get the original
file not found error.
>From the *Messages* buffer:
--
Jeff Horn writes:
> Hi orgsters,
>
> I'm wondering how I should publish .htaccess files? My current setup
> is a source directory under ~/org/, which is kept at Dropbox, and a
> publishing directory under ~/Sites/, which is not. Since data loss is
> pyschologically crippling, I like to keep *all*
Hi orgsters,
I'm wondering how I should publish .htaccess files? My current setup
is a source directory under ~/org/, which is kept at Dropbox, and a
publishing directory under ~/Sites/, which is not. Since data loss is
pyschologically crippling, I like to keep *all* my source files
(images, css,
