* Stefano Lattarini wrote on Wed, Sep 14, 2011 at 11:35:37AM CEST:
> On Wednesday 14 September 2011, Ralf Wildenhues wrote:
> > It applies to any word that is surrounded by whitespace (or beginning or
> > end of command line), regardless of shell syntax. Please don't
> > formulate it like Solaris make would understand shell syntax when
> > rewriting rules, IMHO that's confusing and makes it harder to understand
> > the issue.
> >
> You're right, my previous formulation was somewhat confusing in this
> regard. What about the squash-in below?
Fine with me, thanks.
> +@dots{}}, which is typically undesirable. In fact, @command{make} is
> +completely unaware of shell syntax used in the rules, so the VPATH
> +rewrite can potentially apply to @emph{any} whitespace-separated word
> +in a rule -- including shell variables, functions, and keywords.
I think you want a comma rather than an emdash here; also, for American
English type setting, you'd write an emdash as three hyphens and no
space right before and afterwards, as texinfo markup.
Cheers,
Ralf
