> On 13.06.2020, at 22:22, Jakob Reschke <forums.jakob at resfarm.de> wrote:
> 
> Even though the . stands for the current directory (whatever that is), still ./foo/bar is a relative path. It cannot be resolved without another value (the current or default directory) and is quite literally relative to that.
> 
> If on: expects an absolute path as Tobias said, you could also say it expects an already resolved path, which ./foo/bar is not.

Jakob is right.
-t

> 
> 
> K K Subbu <kksubbu.ml at gmail.com> schrieb am Sa., 13. Juni 2020, 20:01:
> On 13/06/20 8:36 pm, Levente Uzonyi wrote:
> > Why not use FileDirectory default / '.' instead of FileDirectory on: 
> > '.'? The former does what you want, the latter does what's specified by 
> > the tests. After a quick glimpse on #on:'s implementation, my impression 
> > is that it expects an absolute path.
> 
> But a path like ./foo/bar is a complete path. The '.' is just a short cut.
> 
> A name like foo/bar is incomplete and needs a list of potential 
> directories (e.g. {vmPath . imagePath} which the path may be found.
> 
> Regards .. Subbu
>