« first day (597 days earlier)      last day (1178 days later) » 

00:37
chunkybanana opened issue #339 in Vyxal/Vyxal: Anything lambda-sort related is broken
01:22
how is it that v2.4 had better LL printing than v2.6?
01:39
Lyxal opened PR #340 (Vyxal/Vyxal) (Vyxal:quick-implementations → Vyxal:main): Add a few little things
01:51
chunkybanana approved on PR #340 (Vyxal/Vyxal): "Looks good to me, plus I really want sorting to be great again"
Wait, that fixes #339, right?
02:12
No
No it doesn't
It's some other fixes from yesterday
 
1 hour later…
03:23
@lyxal What do you think about having a function/modifier entirely separate from v that acts like foreach?
@rues that'd work for a quickfix, but it still wouldn't fully fix the issue
I don’t see this as an issue honestly
This is exactly how generators are meant to work
But we could do the fix you suggested in tge issue instead then (does_print or sth of tgat sort)
@rues I've used , as a join on newlines in some of my answers on cg in maps
It also allows for a 12 byte flagless fizzbuzz
But it doesn't need immediate fixing tho
04:23
@lyxal Same.
When's 2.6.1 coming along?
later today
because weekly release schedule
I have a 4-character change I want to make (ctx -> ctx=ctx), is it ok if I push that straight to main? (It's a bug in sort_by that's causing a lot of problems, and we probably don't want to release 2.6.1 with a known bug)
I'll change it because I've got some commits I need to push in a bit
Ok. Line 3006.
that's almost right near where I was working lol
I was touching line 2981
ighto pushed
04:38
elements.py is so big that you have to navigate it
it's better than having multiple element files though
Yes
It'd be nice to have an autosort
autosort?
As in all the element functions are automatically sorted
they already are sorted though
04:40
Never mind.
2 days ago, by emanresu A
Idea: What if we have https://vyxal-staging.pythonanywhere.com which pulls directly from main?
that's a good idea
Ok, I'll create the account and send you the details
One moment
I just realised I used my default password for the account
go to settings > deploy keys on the main repo and add it there
Ok, just gotta change the password
3 mins ago, by lyxal
go to settings > deploy keys on the main repo and add it there
actually no secrets
settings > secrets > new secret
04:49
Ok, done
now everyone can see it
everyone it the org that is
which is good
wait nvm people can't see it
lyxalcgcc {at} gmail {dot} com
Great, I've lost it from my clipboard too.
It's too secure
lol
04:54
Any way to get it back?
reset password after AoC
 
2 hours later…
07:28
Lyxal merged PR #340 (Vyxal/Vyxal) (Vyxal:quick-implementations → Vyxal:main): Add a few little things
Lyxal deleted branch Vyxal/quick-implementations
good.
07:48
Lyxal closed issue #332 (Apply to register unimplemented, Vyxal/Vyxal)
Time to do 2.6.1?
what do you think?
(lol I was working on the notes since #340 got merged)
> Comparison operators (like < and >) no longer error on two numbers.
ಠ_ಠ
07:52
chunkybanana closed issue #339 (Anything lambda-sort related is broken, Vyxal/Vyxal)
Do we have a PR for pushing 2.6.1 to production?
(Or does that automatically occur?)
@emanresuA not yet
@emanresuA Sympy decided it's a good idea to return a special Boolean class that int doesn't automatically turn into an integer
@lyxal ಠ_ಠ
So that Sympy boolean has to be converted to a normal python boolean (using bool) and then convert that to int
Thank you Sympy very cool
07:59
chunkybanana opened PR #342 (Vyxal/Vyxal) (Vyxal:permalink-host → Vyxal:main): Fixed #187
chunkybanana closed issue #232 (Ṫ breaks with R flag, Vyxal/Vyxal)
chunkybanana closed issue #164 (pythonanywhere whitelist for requests, Vyxal/Vyxal)
What's the deal with the on hold tag?
Since we've done rewrite?
08:22
I'd suggest keeping it or creating tags to indicate priority
The latter's probably a better idea
08:35
Does this need reviewing? (It's such a trivial change, I can just forcemerge it if that's ok)
@emanresuA sounds good to me
Make sure to merge onto prod after lol
chunkybanana merged PR #342 (Vyxal/Vyxal) (Vyxal:permalink-host → Vyxal:main): Fixed #187
chunkybanana closed issue #187 (permalink generates on lyxal.pythonanywhere.com even on forked domains, Vyxal/Vyxal)
Tags have been created and burninated, issues have been cleaned up and triaged, it's looking pretty good.
09:05
chunkybanana closed issue #5 (° no longer does function reference, Vyxal/Vylight)
chunkybanana closed issue #4 (Comment highlighting never stops, Vyxal/Vylight)
v1.1.3 released in Vyxal/Vylight
I'ma look for ways to unit test a codemirror parser
09:31
@emanresuA unit test the js that parses the vyxal
Iirc it's a separate file to code mirror
I'm sure there'd be a github workflow of sorts that provides js testing
Uh, not really. The parser is two functions passed to the codemirror api - one to setup an initial state, one to parse each character. The latter uses several things from the codemirror api as well.
 
13 hours later…
23:01
Should the yaml processing stuff be pulled out of documents/knowledge and put somewhere else? It feels wrong to put it there with all the text/yaml/md files
@rues what would be the name of the folder they'd be in?
No idea, gen maybe?
23:41
@rues I've found someone else who likes Scala and would want to contribute to Vyxal v3
:o
I am very happy :)
Who is it?
🎉🎉🎉
They were also planning on making a LLVM version of vyxal 2.6
Ooh, that'd be very interesting (although we'd need a proper server of our own, I think, because PA wouldn't let us run that)

« first day (597 days earlier)      last day (1178 days later) »