Documentation Channel for #raku | This channel is logged | Roadmap:
Set by [Coke] on 23 May 2022.
02:42 Voldenet_ joined, Voldenet left, Voldenet_ is now known as Voldenet 03:42 Voldenet_ joined 03:44 Voldenet left, Voldenet_ is now known as Voldenet 06:35 sena_kun joined 08:10 Geth left, Geth joined
Geth doc/main: 5d050f335c | (Salve J. Nilsen)++ (committed using GitHub Web editor) | doc/Language/operators.rakudoc
Improve ff() examples (#4329)

  - Add an element to the beginning and end of the arrays
   used in the ff() (and related) examples. This is to also
   show the main feature of ff() when the read looks for
   specific usage examples.
Co-authored-by: Salve J. Nilsen <>
[Coke] lizmat: looks like some new failures on rakuast-compare test. I just rebuilt with moar-latest and they're still there. 18:25
lizmat yeah... looking at them right now
almost clean again :-)
a decision was made to make :allow a purely renderer thing, rather than a thing that also affects parsing 18:26
this implied that any codepoint with :Lu uniprop is now legal as a markup starter
but this also means that the legacy podifier needs some adjustments 18:27
working on that now
also: it appears that my margin refactoring exposed some faulty pod / expectations
[Coke] cool 18:28
Geth doc/main: d6c96d375f | (Elizabeth Mattijsen)++ | 3 files
Fix expectations about =for code

  =for code
The legacy grammar incorrectly produces a Pod::Code object with
  " zippo" wheras the indentation of =for should be deducted
... (5 more lines)
lizmat that's one set of issues fixed
the other one is related to markup inside the meta area of a L<> 19:46
inside a code block allowing some markup 19:50
Geth doc/main: b4709779bf | (Elizabeth Mattijsen)++ | doc/Language/pod.rakudoc
Remove use of B<> markup in code block for now

Need to look at the ramifications of this further, but want the tests to be clean now.
lizmat [Coke] with this and the latest Rakudo commit, the doc tests should be clean again 19:55
there's still an issue with things like: L<B<foo> bar | baz C<zippo>> which I will look at tomorrow 19:56
when fixed, this could possible make the last doc commit redundant, but am not sure of that 19:57
and with that, my hacking for today come to an end&
[Coke] lizmat++ 20:24
lizmat: some of the failures are because %*ENV<PATH> is now rendering as %*ENPATH 21:14
which is implied by what you said, but wanted to call that out specifically (since it then causes aspell failures)
lizmat do you mean you still see errors? 22:27
22:28 sena_kun left
[Coke] need to retest. 22:31
will do so now
lizmat it was just clean for me on HEAD 22:36
please create a gist if it fails, will look tomorrow 22:38
but now sleep&
[Coke] yah, not clean, working on a gist 23:09
lizmat: 23:16