5 Nov 2024
patrickb todo.sr.ht/~patrickb/Rainbow 21:39
coleman Got it, thank you :) 21:43
patrickb Yeah, the linking is suboptimal on sr.ht. The uplinks from the ticket/list/git/... sites up to the project hub are missing. It's on their evergrowing todo list... 21:45
7 Nov 2024
Geth doc-website/dev: ff4eb39b46 | finanalyst++ | .buildkite/pipeline.yaml
test no highlighter
21:24
doc-website/dev: cc245f9590 | finanalyst++ | 14 files
re-enabling epub, adding rainbow to epub
22:10
8 Nov 2024
doc-website/docs-dev: ff4eb39b46 | finanalyst++ | .buildkite/pipeline.yaml
test no highlighter
03:40
doc-website/docs-dev: cc245f9590 | finanalyst++ | 14 files
re-enabling epub, adding rainbow to epub
doc-website/docs-dev: c6b3993187 | (Coleman McFarland)++ | 14 files
Merge branch 'dev' into docs-dev
[Coke] coleman++ finanalyst++ 13:10
9 Nov 2024
Geth doc-website/main: d636f203b2 | (Richard Hainsworth)++ (committed using GitHub Web editor) | 28 files
removes the syntax highlighting dependency on Net (#418)

  * removes the syntax highlighting dependency on Net
  * update META6
  * bump to refire buildkite
... (12 more lines)
09:07
12 Nov 2024
doc-website/readme-cleanup: f34c924c87 | (Coleman McFarland)++ | repo_docs/README.rakudoc
Update the README

We fix a typo and remove reference to the nodejs highlighter.
I also felt that the deployment section could be shortened to the bare minimum: what happens on merges to main and how production is updated.
02:09
doc-website/readme-cleanup: de787519ec | (Coleman McFarland)++ | repo_docs/README.rakudoc
Update the README

We fix a typo and remove reference to the nodejs highlighter.
I also felt that the deployment section could be shortened to the bare minimum: what happens on merges to main and how production is updated.
02:31
doc-website: dontlaugh++ created pull request #420:
Update the README
02:32
doc-website/readme-cleanup: 6280439f71 | (Coleman McFarland)++ | 2 files
Add README update instructions, fixes #320
02:45
doc-website/readme-cleanup: 7d0fe44ada | (Coleman McFarland)++ | README.md
work around markdown2 render bug
02:46
doc/main: 1719ad2c87 | rir++ (committed by Coleman McFarland) | doc/Language/nativecall.rakudoc
NativeCall void function returns Mu type object

Doc' NativeCall's default `returns` trait as `Mu:U`.
Emphasize `void`-is-only-for-pointers with its own paragraph.
03:06
doc/rm-defunct-dockerignore: ff05c0cd31 | (Coleman McFarland)++ | .dockerignore
Remove .dockerignore file

This repo no longer includes a Dockerfile
03:14
doc: dontlaugh++ created pull request #4531:
Remove .dockerignore file
doc-website/main: dfc2ba9863 | (Coleman McFarland)++ (committed using GitHub Web editor) | 2 files
Update the README (#420)
03:49
doc/main: 4fe6620839 | (Coleman McFarland)++ (committed using GitHub Web editor) | .dockerignore
Remove .dockerignore file (#4531)

This repo no longer includes a Dockerfile
12:52
13 Nov 2024
doc/do-clarification: 106233bb57 | (Daniel Sockwell)++ (committed using GitHub Web editor) | doc/Language/control.rakudoc
Clarify when `do` runs a block

See StackOverflow Q&A at stackoverflow.com/q/68744854/10173009
13:17
doc: codesections++ created pull request #4532:
Clarify when `do` runs a block
13:18
19 Nov 2024
doc/main: 71be59f488 | raiph++ (committed using GitHub Web editor) | doc/Language/regexes.rakudoc
Finish s/`<|w>`/`<?wb>`/ et al in regexes.rakudoc

See github.com/Raku/doc/pull/4435.
I'm not 100% sure this commit will work smoothly as is. One change (or was it two?) involved what looks like meta information related to search indexes. I'm not familiar with that stuff. I did a mechanical translation and guessed it was likely it would work if there was an index entry for `<?wb>`. But maybe I misunderstand. And anyway, I don't know how to test it short of getting into setting up a whole doc testing s
20:07
doc/raiph-patch-2: 4b6d5e0266 | raiph++ (committed using GitHub Web editor) | xt/headings.rakutest
Finish s/`<|w>`/`<?wb>`/ in doc (headings.rakutest)

While `<|w>` works in Rakudo, it isn't official Raku, and while I personally like it, there's a chance it will go away. Its semantics are the same as `<?wb>`, which _is_ official Raku, so I've switched to that. (See also github.com/Raku/doc/commit/5c1a147...fee63efa.)
I meant my prior related commit (which changed the regex doc page) to be a PR because I wasn't 100% sure about the `X<...>` stuff and regardless of that I felt it could still do with a quick check by someone else. But I clicked the wrong button. Otoh, once I'd done that I thought it would almost certainly work and be wanted, and if it didn't it wouldn't be a big deal and would be easy for me to spot it even
But for _this_ change I'm making sure I do it as a PR. I still expect it to work, but it may not, and the consequence of that might be a waste of others' time, and even if it does it might not be wanted.
20:30
doc: raiph++ created pull request #4534:
Finish s/`<|w>`/`<?wb>`/ in doc (headings.rakutest)