|
Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki Set by [Coke] on 23 May 2022. |
|||
|
00:00
sjn joined,
tbrowder__ joined
|
|||
| coleman | deployed to prod | 00:31 | |
|
08:49
sena_kun joined
|
|||
| Geth | doc/main: 0fcfc364e5 | (Elizabeth Mattijsen)++ | doc/Language/create-cli.rakudoc Change C<<>> to V<<>> to handle rendering issues In RakuDoc, "C«%*SUB-MAIN-OPTS<named-anywhere>»" is seen as: C< %SUB-MAIN-OPT S< named-anywhere ... (6 more lines) |
09:15 | |
| doc/main: 942e09b718 | (Elizabeth Mattijsen)++ | 3 files Some more trailing whitespace in code blocks |
09:53 | ||
|
11:33
lucs left
11:34
lucs joined
|
|||
| Geth | doc/main: 56734cdabe | (Elizabeth Mattijsen)++ | doc/Language/glossary.rakudoc Fix rendering The old pod grammar doesn't handle 'C«<O(I<...>)>»' well, in the sense that it doesn't consider the inner 'I<...>' to be markup. The RakuAST grammar does, causing difference in rendering. Since the I<...> is really only for a little emphasis, it feels ok to remove that for now to get consistent rendering. |
13:05 | |
| doc/main: ed2c6f3b0b | (Elizabeth Mattijsen)++ | doc/Language/ipc.rakudoc Change C<<>> to V<<>> to handle rendering issues |
13:08 | ||
| lizmat | [Coke] so what to think of L<(foo|bar)|url> | 13:25 | |
|
13:58
sena_kun left
14:00
sena_kun joined
|
|||
| lizmat | down to 24 failing | 14:11 | |
| meh: | 14:56 | ||
| L«C<prefix:<|>>|/language/operators#prefix_|» | |||
| Geth | doc/main: 788f3cdda9 | (Elizabeth Mattijsen)++ | doc/Type/Telemetry/Instrument/Usage.rakudoc Fix improper use of =head |
15:02 | |
| doc/main: c56c927353 | (Elizabeth Mattijsen)++ | doc/Type/independent-routines.rakudoc Change C<<>> to V<<>> to handle rendering issues |
|||
| [Coke] | L<(foo|bar)|url> - my human expectation is that the ()s are wrapping it somehow, but I think the L could reasonably break on the | ther. can we \| the first |? | 15:41 | |
| lizmat | one approach would be to allow () as an alternate letterless markup | 15:43 | |
| [Coke] | your fix to make it the last one is fine. | ||
| lizmat | no, it's not | ||
| L«C<prefix:<|>>|/language/operators#prefix_|» | |||
| [Coke] | right, to make it more like the human parsing. :) | 15:44 | |
| ah | |||
| should I not run a test with 7e6e5a | 15:45 | ||
| should I not run a test with c7e6e5a, then? | |||
| lizmat | no | ||
| I mean, indeed don't run it | 15:46 | ||
| [Coke] | definitely looking forward to switching all our testing over to rakuast in raku/doc, thanks for all this effort! | 15:47 | |
| lizmat | yeah, it should be at least 5x as fast then | 15:48 | |
| I've just decided that I'm not going to open the can of worms wrt escaping | | 15:56 | ||
| if you want to use | inside a L<foo(a|b)|url> | |||
| then you should use V<> | |||
| if you want to use | inside a L<fooV<(a|b)>|url> | 15:57 | ||
| in the case of L«C<prefix:<|>>|/language/operators#prefix_|» | |||
| the :<|> is effectively doing that already, as the <|> there is a letterless markup | 15:58 | ||
| the only problem is that the Pod::To::Text doesn't render C<V<>> correctly :-( | 15:59 | ||
|
16:24
raiph joined
16:55
rf left
|
|||
| Geth | doc/main: 120a7f9384 | (Elizabeth Mattijsen)++ | doc/Programs/04-running-raku.rakudoc C<fooI<bar>> is not rendered correctly by Pod::To::Text So remove the I<> for now |
17:00 | |
| doc/main: 494f7a9b1d | (Elizabeth Mattijsen)++ | doc/Type/BagHash.rakudoc Remove trailing whitespace before | in L<> This is not rendered by Pod::To::Text, so remove now for consistency |
|||
| lizmat | down to 15 | ||
| doc/main: d5d0964c8e | (Elizabeth Mattijsen)++ | 2 files Change C<<>> to V<<>> to handle rendering issues |
|||
| lizmat | [Coke]: can we have =begin code blocks within =begin code blocks? | 17:03 | |
| [Coke] | ... I don't think it makes sense. | 17:10 | |
| Geth | doc/main: 10744b190a | (Elizabeth Mattijsen)++ | doc/Language/variables.rakudoc Change C<<>> to V<<>> to handle rendering issues Also remove nested "=begin code" blocks, as they were not necessary and there's question about the legality of such a structure. |
17:15 | |
| doc/main: 59837d0ede | (Elizabeth Mattijsen)++ | doc/Language/unicode_entry.rakudoc Escape column dividers in tables Otherwise they'd be illegal column dividers in a table with invisible column dividers. |
17:21 | ||
| doc/main: 6c6e9faf0c | (Elizabeth Mattijsen)++ | doc/Language/terms.rakudoc Remove trailing whitespace before | in L<> |
17:24 | ||
| lizmat | 12 | 17:32 | |
| [Coke] | \o/ | 17:34 | |
| Geth | doc/main: db4c47ba79 | (Elizabeth Mattijsen)++ | doc/Language/subscripts.rakudoc Remove trailing whitespace before | in L<> |
17:37 | |
| lizmat | 11 | ||
| Geth | doc/main: cafb2d8398 | (Elizabeth Mattijsen)++ | doc/Language/operators.rakudoc Add visual column dividers to prevent confusion |
17:48 | |
| doc/main: e2a80f0ac0 | (Elizabeth Mattijsen)++ | doc/Language/nativecall.rakudoc Some more trailing whitespace in code blocks Also remove some leading whitespace in code blocks for consistency |
17:52 | ||
| doc/main: 8d262b50e4 | (Elizabeth Mattijsen)++ | doc/Language/modules.rakudoc Remove trailing whitespace in code blocks and L<> |
17:55 | ||
| [Coke] | weird, we have a trailing whitespace test that was passing | 17:56 | |
| lizmat | the 8 remaining files need closer looks | ||
| and that will probably happen after the weekly tomorrow | |||
| Geth | doc/main: 535516f21d | (Will Coleda)++ | xt/01-raku-version.rakutest track latest compiler |
17:57 | |
| doc/main: 4d8909c02b | (Will Coleda)++ | xt/trailing-whitespace.rakutest no need to skip these files anymore removed from the repo. |
|||
| [Coke] | lizmat++ | 17:58 | |
| lizmat | dinner& | 17:59 | |
| [Coke] | ah. there isn't any protection in pod/cache in the doc repo for multiple simultaneous runs. not sure hy i thought there was | 18:01 | |
| so prbably ripping it out is best. | |||
| er, there is a .lock, so maybe it's working some place. | 18:12 | ||
| Geth | doc/main: fa2d6b3174 | (Elizabeth Mattijsen)++ | doc/Language/js-nutshell.rakudoc Add missing uri |
18:50 | |
| lizmat | 7 | ||
| Geth | doc/main: 9e531875f0 | (Elizabeth Mattijsen)++ | doc/Language/quoting.rakudoc Some more trailing whitespace in code blocks Even though some of this was intentionally there, it looks like no renderer will actually achieve the intended vision. So remove for now. |
19:42 | |
| lizmat | 6 | ||
| should implicit code blocks work within a =begin item / =end item ? | 19:44 | ||
| Geth | doc/main: c77dd3ebc0 | (Elizabeth Mattijsen)++ | doc/Language/regexes.rakudoc Fix some rendering issues - apparently, implicit code blocks do not work within =item, so make them explicit - C<foo C<bar>> is not rendered correctly by Pod::To::Text, so remove the inner C<> as it doesn't make any sense anyway. |
19:55 | |
| lizmat | 5 | 19:56 | |
| Geth | doc/main: f35b33b0f7 | (Elizabeth Mattijsen)++ | doc/Language/setbagmix.rakudoc Unbalanced < may only occur within something else than <> So mark the outer as << >> and the parser won't get confused anymore |
19:59 | |
| lizmat | 4 | ||
| so: doc/Type/Str.rakudoc has 7̈ in it | 20:07 | ||
| it looks like it upsets the markup detection state machine | 20:08 | ||
| so that really is going to be for tomorrow :-) | |||
| &afk | |||
|
21:39
sena_kun left
22:52
raiph left
|
|||
| [Coke] | lizmat++ | 23:14 | |