🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). *** CONFERENCE TIME conf.raku.org *** This channel is logged for the purpose of keeping a history about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Log inspection is still being worked out
Set by lizmat on 6 August 2021.
lizmat
.oO( it's komkommertijd on #raku )
 08:38
El_Che (the Silly Season for the anglophones around here) 08:42
Altreus extra helpful weekly with all those video links on!
MasterDuke yeah, that was a new one to me 08:43
El_Che I think lizmat is happy about the reddit conversations to feel the komkommertijd :)
fill
lizmat actually, no: they drain me
El_Che sarcasm sign
Altreus turns out there are lots of proposals for sarcasm signs 09:48
El_Che normally I would make a commitee and charter joke, but for people sanity, I keep it in my filter :) 10:21
lizmat filter++ 10:27
lizmat afk& 11:09
lizmat clickbaits rakudoweekly.blog/2021/08/09/2021-...tcon-done/ 17:05
tonyo_ lizmat: most of my group thought is how to handle the auth .. does the group name suddenly occupy a username: `raku-community` so auth is `zef:raku-community` or should the auth be whoever is uploading and there's something else in the meta handling _who_ the org is 17:20
guess that's what the `owner` field is for 17:21
lizmat yeah, unless there's another owner, "raku-community" or "raku-community-modules" would be the owner 17:28
and if there's another owner, it wouldn't be a raku-community-module
now, on whoever is uploading: I don't think that's information that should be in the META 17:29
who uploaded it, is more a later forensics question than a decision on which module you should load for a given URI ?
ugexe just have usernames and orgs be the same similar to github 17:31
lizmat would work for me... although it should be github.com/gitlab.com agnostic ? 17:32
ugexe the auth shoudnt be something that changes much if ever, otherwise consumers will have be incentivized to not use them for e.g. `use Foo:auth<...>` 17:33
lizmat agree 17:35
tonyo_ it'll be specific to the eco - that was my feeling too .. `raku-community` would eat that username but that seems like nbd 17:36
ugexe yeah so really anything org related is pretty much separate from raku / meta6 17:46
you can fill out some arbitrary owner/whatever field automatically but that wouldnt realistically be consumed by anything 17:47
tonyo_ yea. okay we're on the same page about it
Xliff What does this error mean: Cannot call method 'package_at_key' on a null object 17:51
in method COERCE at /home/cbwood/Work/BizzellAppServer/app/lib/Bizzell/Inventory/Instance.pm6 ($WORK::Inventory::Instance) line 33
The package in question is definitely not defined, according to a .gist
This is in a method COERCE, btw. 17:52
aixylinux I just installed rakudo star bundle rakudo-star-2021.07-01-win-x86_64-msvc on Win 10. raku -u outputs strange characters. What is wrong? 20:08
C:\Users\danhale>raku -v
Welcome to 𝐑𝐚𝐤𝐮𝐝𝐨™ v2021.07.
Implementing the 𝐑𝐚𝐤𝐮™ programming language v6.d.
Built on MoarVM version 2021.07.
raku -v, sorry, not raku -u 20:09
[Coke] It's unicode; getting that font right on windows is hard. One sec, will find the ticket #. 20:14
hurm. I cannot find the ticket I thought I opened. 20:15
It's "Rakudo" and "Raku"; you'd need to a) be using the right codepage on windows, and b) have a font that can render those characters. 20:16
I think the plan is to make that ASCII if we're on windows. for now, it's cosmetic (but does indicate you might want to enable unicode in your shell) 20:17
ah, it was closed: github.com/rakudo/rakudo/issues/4379
read through that; it was closed in Jun, so I would have expected the fix to work in the .07 release 20:18
aixylinux Thanks for the quick response. The REPL displays correctly. chcp says codepage is 437. What ought it to be? 20:27
[Coke] says in the ticket. 20:31
(I always have to look it up)
aixylinux The ticket says chcp 65001. That produces different garbage. 20:32
[Coke] m: say chr(0x00Df) ; # will probably make this work.
camelia ß
[Coke] Yes.
aixylinux C:\Users\danhale>chcp 65001 20:33
Active code page: 65001
[Coke] which is the behavior I reported before lizmat closed the ticket.
aixylinux C:\Users\danhale>rakudo -v
Welcome to 𝐑𝐚𝐤𝐮𝐝𝐨™ v2021.07.
Implementing the 𝐑𝐚𝐤𝐮™ programming language v6.d.
Built on MoarVM version 2021.07.
[Coke] That's rendering ok here.
is that a cut and paste?
aixylinux I see here the copy/paste displays correctly. Thanks anyway, if it's a known issue, I can wait for a fix.
[Coke] (with it looking bad on your screen?)
aixylinux no it looks good in this window. (Chrome browser) 20:34
[Coke] I think the fix is "don't try to use that unicode on windows.". I think part of the issue is that windows unicode-aware fonts do not cover that character range.
aixylinux Ah so desu ka. Thanks for your help. 20:35
[Coke] yup, github.com/rakudo/rakudo/commit/5e1c97bae6 seems to show it using ASCII if we detect we're on windows.
Hai. 20:36
justsomeguy /c/c 22:43

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!