[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: many questions
From: |
Patrice Dumas |
Subject: |
Re: many questions |
Date: |
Tue, 4 Aug 2009 18:12:41 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Tue, Aug 04, 2009 at 10:53:26AM -0500, Karl Berry wrote:
> And should files also be searched for in destination directory? I think
> that
> it doesn't matter for input files, but would be better for images.
>
> What scenario do you have in mind with images?
I remember than we agreed that @images paths were relative to the
result file. So, to have paths right, @image should be searched for in
this directory.
> My inclination is to say that searching the destination directory for
> any kind of input file, image or otherwise, would just have great
For input files, indeed it has potential for confusion, but for
images, it seems to me to be rather logical. The issue with
images is that they aren't only something that is inputed in a
manual, they are also part of the final outputed manual (at least
in html).
> potential for confusion, since the output dir is often some temporary
> location; if it happened to include an image by the wrong name ... I
> can't think of any other program that does this. Better for users to
> use -I explicitly, I think?
I agree, avoiding magic as much as possible is better, indeed.
--
Pat