[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: File local setting for export directory?

From: Loris Bennett
Subject: Re: File local setting for export directory?
Date: Tue, 04 Aug 2020 13:42:56 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Russell Adams <RLAdams@AdamsInfoServ.Com> writes:

> On Tue, Aug 04, 2020 at 08:25:13AM +0200, Loris Bennett wrote:
>> I'm surprised no-one was interested, although I suppose back then I was
>> probably also one of the uninterested :-)
> Please remember maintainer time is limited. There are often edge cases
> for one user as well for a software as flexible as Org.

I appreciate that, although some form of control of where things are
exported to seems to me to be fairly generic functionality and something
which might be of interest to a number of people.

>> I only have one org file from which I generate a number of graphics as
>> well a PDF which contains the graphics.  Don't many people do a lot more
>> of that kind of stuff and don't they want to exclude a directory with
>> generated files from, say, Git?
> I produce all of my professional documentation for customers in Org to
> Latex and PDF. I create a directory for each document where all the
> files go, and so I expect my .org, .tex, and .pdf files to be in the
> root of that directory. I will sometimes add subdirectories for small
> files (images, source code, etc) that I include in the final
> document. Which sounds like opposite the scheme you are using.
> This may also come from my history of code management, makefiles, etc.

In actual fact I do also have something similar for, say, presentations.
The .org file and all generated files are in one directory, with some
other files such as logos and photographs included from another directory.

It was mainly just the idea of being able to add a entire subdirectory
to .gitignore which made me think it would be nice to have a way of
changing export directory.



This signature is currently under construction.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]