« first day (596 days earlier)      last day (1179 days later) » 

02:11
@AaroneousMiller lol yeah we might even want to call it 2.7
Actually 2.7 might ve too much but releasing v2.6.1 def makes sense
I was planning to make the 2.6.1 release at the end of the week before y'all mentioned it lol
 
3 hours later…
05:15
Idea for errors: In the except block after debug, rerun with a debug mode which wraps every element in a try/except block.
 
5 hours later…
10:23
Great, gitcdn bad. Get something else :P
@emanresuA h'what?
@emanresuA doesn't work
It doesn't deliver it in the right format
You need a cdn to make it the right format
Also, it seems like it's just you
It's loading for me
Oh, as a script file? That's annoying
I cleared my cache and it still loaded for me
@emanresuA it also doesn't send the stylesheet properly
10:39
Ok, now I'm getting 503 errors
Works fine on safari, but not on chrome or firefox, so idk
o/ cos slep
11:01
o/
@emanresuA sounds like it could be a problem with your internet
FF returns status 200 for gitcdn for me
11:19
Lyxal closed issue #311 (`ḟ` doesn't overload for functions, Vyxal/Vyxal)
12:23
I've found the root cause of issue #28
vectorising print leaves the list on the stack
becuase it's just a generator
meaning you can do really janky stuff like this:
!!/run 1 2 3 Wv,_
@lyxal 0
so that means you can vectorise print and cancel the result
I feel like some sort of CnR could be made out of that
Lyxal closed issue #28 (Vectorised print commands not disabling implicit output, Vyxal/Vyxal)
because it's worthy of its own issue
!!/issue Internal way to force discarding of vectorised result Some commands like `,` need to not lazily evaluate their arguments/discard the value when vectorised bug difficulty:hard
(message response failed or the new message is not a command)
Vyxal-Bot opened issue #336 in Vyxal/Vyxal: Internal way to force discarding of vectorised result
 
4 hours later…
16:23
By the way, the input box opens every time I run the code, is it supposed to be a feature or can I disable that?
a-stone-arachnid opened issue #337 in Vyxal/Vyxal: `…` doesn't work
pxeger created branch Vyxal/337
pxeger opened PR #338 (Vyxal/Vyxal) (Vyxal:337 → Vyxal:main): Fix #337
17:03
vyxal.pythonanywhere.com seems to be down...
It's okay for me
17:59
cgccuser approved on PR #338 (Vyxal/Vyxal): "Looks good to me, this is an annoying thing about transpilation."
cgccuser closed issue #337 (`…` doesn't work, Vyxal/Vyxal)
cgccuser merged PR #338 (Vyxal/Vyxal) (Vyxal:337 → Vyxal:main): Fix #337
pxeger deleted branch Vyxal/337

« first day (596 days earlier)      last day (1179 days later) »