Re: Issue 391 in lilypond: using relative filepath in \include "foo.ly"

[Hans Aberg]

On 3 Oct 2007, at 22:27, address@hidden wrote:

> Issue 391: using relative filepath in \include "foo.ly"
> http://code.google.com/p/lilypond/issues/detail?id=391

A similar question showed up in the case of Bison for the use of  
skeleton files. There, it was decided that when the include is in a  
(grammar source) file, it is relative that file, and when it is in a  
program startup option, it is relative the program invocation  
(working directory).

As for how filenames are expanded, that is really done by the shell  
on UNIX platforms. See for example 'man bash', section "COMMAND  
EXECUTION". As for Bison, it was decided to emulate this behavior.

  Hans Åberg