Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh and line breaks
- X-seq: zsh-workers 19780
- From: Clint Adams <clint@xxxxxxx>
- To: "Peter A. Castro" <doctor@xxxxxxxxxxxx>
- Subject: Re: zsh and line breaks
- Date: Thu, 15 Apr 2004 06:35:41 -0400
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <Pine.LNX.4.53.0404142318450.1010@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <29767.1081186817@xxxxxxx> <Pine.LNX.4.53.0404051424500.11532@xxxxxxxxxxxxxxxxxxxx> <20040415050315.GA26270@xxxxxxxxxxx> <Pine.LNX.4.53.0404142318450.1010@xxxxxxxxxxxxxxxxxxxx>
> The use of the shell wildcard (zsh*.html) makes the shell do a pattern
> match against the list of files in the directory in which it is run. If
> I was building from a work directory (say zsh-4.2.0/.build/Doc) and
> installing into a destination root other that "/" (say zsh-4.2.0/.inst)
> make executes this bit of shell code and it fails to find any zsh*.html
> files because make isn't currently in that directory (it's in
> .build/Doc). Prepending ${sdir} ensures the zsh*.html files are
Yes, and the html files are generated in the build directory, so it
won't find them in ${sdir}.
> So how, exactly, does this break VPATH? Can you give me an example?
> I'll try and correct it, but I don't yet see how it's broken.
Is Cygwin texi2html outputting to your source directory?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author