Re: use lib and locations in a variable

On 7/11/21 3:27 PM, Bruce Gray wrote: OUTPUT: ".".IO<-- again with the dot Hi Bruce, Back to the silly dot. I can hard code that myself. As far as I can tell, Raku, runs in the directory you start it in. And when I want the current directory, I want the full stinkin' path, not a dot.

Re: use lib and locations in a variable

> On Jul 11, 2021, at 1:13 AM, ToddAndMargo via perl6-users > wrote: —snip-- > $*PROGRAM.parent is just a silly dot. —snip— Todd, That is true only when the program you are running happens to be in your current directory (as is very common, but not nearly universal, and not the case for

Re: Windows tutorial needed (Todd?)

On 7/11/21 2:31 AM, Tom Browder wrote: See https://github.com/Raku/docs issue #3913. -Tom (tbrowder) Hi Tom, Would you be a little more specific. Are you looking for an install guide? Or something else? -T

Re: Windows tutorial needed (Todd?)

The link for that issue is https://github.com/Raku/doc/issues/3913 ("doc" not "docs") -y On Sun, Jul 11, 2021 at 5:31 AM Tom Browder wrote: > See https://github.com/Raku/docs issue #3913. > > -Tom (tbrowder) >

Windows tutorial needed (Todd?)

See https://github.com/Raku/docs issue #3913. -Tom (tbrowder)

Re: use lib and locations in a variable

> On 11 Jul 2021, at 01:11, Joseph Brenner wrote: > > I want my test files to be able to find the modules they're testing > just using their relative locations, given the usual layout of "lib" > and "t" locations in parallel inside the project directory. > > I find that while this works: > >

Re: use lib and locations in a variable

On 7/10/21 4:11 PM, Joseph Brenner wrote: I want my test files to be able to find the modules they're testing just using their relative locations, given the usual layout of "lib" and "t" locations in parallel inside the project directory. I find that while this works: use lib