The two extra attributes—SPEC and CWD—specify what type of operating system semantics the path should use as well as the "current working directory" for the path, i.e. if it's a relative path, then it's relative to that directory. This means that regardless of how you made one, an IO::Path ...

At creation, each IO::Path object is given information about the current working directory the path might be relative to using the $.CWD attribute (defaults to $*CWD), as well as what operating system semantics should be used for path manipulation using the special IO::Spec type given in the $.SPEC attribute.

Returns IO::Path representing new $*CWD on success. On failure, returns Failure and leaves $*CWD untouched. The $path can be any object with an IO method that returns an IO::Path object. The available file tests are: ... By default, only :d test is performed.

$ perl6 work_dir01.p6 /opt/tor-browser /opt/rakudo /usr/src /usr/sbin /usr/lib32 /usr/lib64 /usr/share /usr/lib IO::Path · chdir - changes the current working directory. The current working directory can be read from the $*CWD variable.

Also creates parent directories, as needed (similar to *nix utility mkdir with -p option); that is, mkdir "foo/bar/ber/meow" will create foo, foo/bar, and foo/bar/ber directories if they do not exist, as well as foo/bar/ber/meow. ... Changes value of $*CWD variable to the provided $path, optionally ensuring the new path passes several file tests.

Notice that $*CWD returns the current working directory. Then we created a new Raku subroutine called hellofromc() that should act as a wrapper to its counterpart C function having the same name and residing in the C library found in LIBPATH. All of this was done by using the is native trait.

This is done this way, because there is no concept of a "default directory per OS thread". And since Raku does not fork, but only does threading, it was felt that the "current directory" concept should be in the $*CWD dynamic variable, which can be lexically scoped, and thus can be thread-safe.

Since the tests are performed against Str arguments, not IO, the tests are executed in the $*CWD, instead of the target directory.

If $merge is set to True, the standard output and error stream end up merged in $proc.out. ... When sunk, the Proc object will throw X::Proc::Unsuccessful if the process it ran exited unsuccessfully. ... shell 'ls /qqq'; # OUTPUT: # (exit code 1) ls: cannot access '/qqq': No such file or directory # The spawned command 'ls /qqq' exited unsuccessfully (exit code: 2) # in block <unit> at /tmp/3169qXElwq line 1 # ... method spawn(*@args ($, *@), :$cwd = $*CWD, Hash() :$env = %*ENV, :$arg0, :$win-verbatim-args = False --> Bool:D)

The main subroutine is collect. It requires a file config.raku to be in the $CWD (current working directory). In CRD the executable Raku-Doc initiates the collection by setting up sources and installing a config.raku file.

Here is a small example that prints the first ten FileChanged-notifications for the current working directory: Raku highlighting · my $finish = Promise.new; my $count = 0; IO::Notification.watch-path($*CWD).act( -> $change { $count++ if $change.event ~~ FileChanged; say "($count) $change.path(): $change.event()"; $finish.keep if $count >= 10; }); await $finish; The type of the change is very much dependent both on the platform and on specific system calls that were used to initiate the change.

At creation, each IO::Path object is given information about the current working directory the path might be relative to using the $.CWD attribute (defaults to $*CWD), as well as what operating system semantics should be used for path manipulation using the special IO::Spec type given in the $.SPEC attribute.

IO::Path::Win32.new("foo/bar").raku.say; # OUTPUT: IO::Path::Win32.new("foo/bar", :CWD("C:\\Users\\camelia")) Note that this string includes the value of the .CWD attribute that is set to $*CWD when the path object was created, by default.

I hope this helps you understand why there isn't a 'boo boo' in the documentation, and why what others have said is actually answering the question you asked. Regards, Richard (finanalyst) On 03/11/2025 08:03, ToddAndMargo via perl6-users wrote: Hi All, I do believe I came across a boo-boo in the docs for "run": https://docs.raku.org/routine/run sub run( *@args ($, *@), :$in = '-', :$out = '-', :$err = '-', Bool :$bin = False, Bool :$chomp = True, Bool :$merge = False, Str:D :$enc = 'UTF-8', Str:D :$nl = "\n", :$cwd = $*CWD, Hash() :$env = %*ENV, :$arg0, :$win-verbatim-args = False --> Proc:D) The above stated that it return a variable of type "Proc".

is · supersede · Variables · $ $*ARGFILES · $*COLLATION · $*CWD · $*DEFAULT-READ-ELEMS · $*DISTRO · $*ERR · $*EXCEPTION · $*EXECUTABLE · $*EXECUTABLE-NAME · $*EXIT · $*GROUP · $*HOME · $*HOMEDRIVE · $*HOMEPATH · $*IN · $*INIT-INSTANT · $*KERNEL · $*OUT · $*PERL · $*PID · $*PROGRAM · $*PROGRAM-NAME · $*RAKU ·

December 2, 2022 - To get the gist of what the variable is: To see a variable’s contents call raku on it or pass it to the builtin data dumper function (dd): Why does a $*CWD variable work like that? Just ask WHY … · Or even HOW the variable works – it’s Higher Order Workings, can be accessed with ^ like so: Raku variables include everything you need to understand how to use them.

Returns the contents of a directory as a lazy list of IO::Path objects representing relative paths, filtered by smartmatching their names (as strings) against the :test parameter. The path of returned files will be absolute or relative depending on what $path is.

July 29, 2018 - The tests for &*chdir in 430ab897a make an incorrect assumption that qx`pwd`.chomp.IO would give process dir, but in reality that follows whatever $*CWD is set to. Don't immediately know how to see what the process dir is.

August 7, 2023 - This post is focused on the lifecycle of the standard raku scalar variable with the $ sigil since it is the obvious inheritor of the perl $ variable which can also be seen in similar guise in places like Bash, PHP and SASS.