« first day (1227 days earlier)      last day (548 days later) » 

05:25
Actually now that I look at it, Vyxal 3 grammar may be context free
minus the arity grouping at this stage
there's no left recursion present nor left factoring needed (I think) so there's no reason it shouldn't be parsable with a LL(1) parser
of course that's if the close all structures thing doesn't immediately make it context sensitive (or even unrestricted)
eh chat does that sometimes
okay nope nvm vyxal 3 grammar is not LL(1) because of the close everything
although it could still be context free
oh huh so turns out vyxal 3 grammar is context free
because to be context free, you need to have all lhs expressions contain a single non-terminal
so I suppose that means something like fast parse could be used for the parser
however, the custom parser gives more flexibility and control
as well as nice handling of arity grouping
so I reckon the custom parser will continued to be used
(spot the compiler design student :p)
06:18
but what if the close all thing was converted in like a pre-parse phase to be however many open structures come before it
that would probably make the grammar simpler
as expected, arity grouping makes it not LL(1)
(not LL(1) just means that a simple parser can't be used)
just some interesting observations now that I actually know what LL(1) entails :p
That shows that the arity grouping cfg wouldn't be parsable using something like basic recursive descent parsing
 
2 hours later…
PlaceReporter99 pushed a commit to Sandbox/master in Vyxal/Sandbox: Update cleanup.yaml
Now uses that action
 
2 hours later…
10:07
@VyxalBot conversation between bot and ONE human
!!/status
@PetəíŕdTheLinuxWizard I am doing at least 3
well, I guessed someone will enter this room instantly...
10:27
Lyxal pushed a commit to Vyxal/Lyxal-patch-1 in Vyxal/Vyxal: Update pyproject.toml
Lyxal created branch Lyxal-patch-1 in Vyxal/Vyxal
Lyxal opened pull request #1908 (Update pyproject to 2.21.10) in Vyxal/Vyxal
Lyxal merged pull request #1908 (Update pyproject to 2.21.10) in Vyxal/Vyxal
Lyxal deleted branch Lyxal-patch-1 in Vyxal/Vyxal
Lyxal pushed a commit to Vyxal/main in Vyxal/Vyxal: Update pyproject.toml
Lyxal pushed a commit to Vyxal/main in Vyxal/Vyxal: Merge pull request #1908 from Vyxal/Lyxal-patch-1
Hey wait I should make sure prod is prodded
!!/prod
vyxal-bot[bot] opened pull request #1909 (Update production (Aug 27 2023)) in Vyxal/Vyxal
Lyxal merged pull request #1909 (Update production (Aug 27 2023)) in Vyxal/Vyxal
Lyxal pushed a commit to Vyxal/production in Vyxal/Vyxal: Merge pull request #1909 from Vyxal/main
 
2 hours later…
12:07
85 messages moved to Trashcan
paper.oga
12:29
!!/status
@TheThonnu I am creating a new type of dance that involves flying.
12:53
!!/help issue
@TheEmptyStringPhotographer !!/issue open [in <repo name>] __Name__ "description": Open an issue in a repository (defaults to Vyxal).
!!/issue open [in Sandbox] Test "test"
Sorry The Empty String Photographer, I'm afraid I can't do that.
Ah'll be bahk.
(it was not)
@Ginger
I know, that was intentional
12:55
oh
good
I'm applying the latest updates, but I need to manually mess with the config files to do it this time
I was worried for a second there that it broke :p
@Ginger can you fix the pinging so that spaces are filtered? Because the correct way to ping me would be @TheEmptyStringPhotographer
Well, here we are again.
updates complete
I'm pretty happy that worked actually
was kinda worried that it'd break
12:58
!!/issue open [in Sandbox] TTESST "just work please"
Sorry The Empty String Photographer, I'm afraid I can't do that.
@TheEmptyStringPhotographer I'd love to, but I don't have any limbs.
@PetəíŕdTheLinuxWizard !!/issue open [in <repo name>] __Name__ "description": Open an issue in a repository (defaults to Vyxal).
12:59
!!/issue open [in Sandbox] Yes it worked "To help @PlaceReporter99"
Sorry Petəíŕd The Linux Wizard, I'm afraid I can't do that.
@Ginger what does this means
!!/issue open [in <Sandbox>] test "test"
Sorry The Empty String Photographer, I'm afraid I can't do that.
13:00
I'm Vyxal Bot 2.0.0 made by Ginger and Vyxal Corp.
All of my commands start with !!/
If you want help for a specific command, do !!/help <command name>.
New to Vyxal? Try !!/info for more information.

Command list: amilyxal, blame, coffee, cookie, die, goodbye, groups, hello, help, hug, idiom, info, issue, maul, permissions, ping, prod, pull, register, repos, run, status, sus
it means you're doing it wrong
!!/issue open [in Sandbox] __Yes it worked__ "To help @PlaceReporter99"
Sorry Petəíŕd The Linux Wizard, I'm afraid I can't do that.
!!/issue open in Sandbox Yes it worked "To help @PlaceReporter99"
you don't need the square brackets dingus
13:00
vyxal-bot[bot] opened issue #95 (Yes it worked) in Vyxal/Sandbox
@Ginger I was faster :p
why have the help description like that then?
@TheEmptyStringPhotographer don't shout, please.
@TheEmptyStringPhotographer that means it is optional
@PetəíŕdTheLinuxWizard what?
13:03
Petaird's right
the brackets meant it was optional
@TheEmptyStringPhotographer it means [this part] is optional.
@Ginger who’s Petaird?
@TheEmptyStringPhotographer meh.
sorry, I can't do accent marks
@TheEmptyStringPhotographer Typos happen.
Here, for y'all to copy: Petəíŕd
13:04
@PetəíŕdTheLinuxWizard no, you’re Petəíŕd
I attempted to Englishize Petəíŕd
@Ginger no problem.
@TheEmptyStringPhotographer well, that's clear it's "Petəíŕd".
Also you can call me Peter.
@TheEmptyStringPhotographer and?
@PetəíŕdTheLinuxWizard look at message above in sandbox
13:09
@TheEmptyStringPhotographer yes? I don't understand what you're trying to prove or show me.
PlaceReporter99 pushed a commit to VyxalBot2/spaces-impede-pinging in Vyxal/VyxalBot2: Spaces impede pinging
PlaceReporter99 created branch spaces-impede-pinging in Vyxal/VyxalBot2
PlaceReporter99 opened pull request #104 (Remove spaces in ping command) in Vyxal/VyxalBot2
@Ginger are you sure it isn’t Petdird?
GingerIndustries approved #104 (Remove spaces in ping command) in Vyxal/VyxalBot2
GingerIndustries merged pull request #104 (Remove spaces in ping command) in Vyxal/VyxalBot2
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: Merge pull request #104 from Vyxal/spaces-impede-pinging
GingerIndustries deleted branch spaces-impede-pinging in Vyxal/VyxalBot2
@lyxαl so in v3 you've put uppercase with factorial but lowercase isn't there yet
I think we should make uppercase/lowercase the string overloads of one range/zero range
Like Vyxal v2 and also Thunno 2
13:25
oops
forgor lowercase
Not-Thonnu created branch v3-add-range in Vyxal/Vyxal
don't worry, we can use uppercase + swap case :p
@lyxαl so are we moving uppercase to one range?
I mean, sure
might as well :p
what do I do with factorial's uppercase?
I mean, v2 has two uppercases as well :p
Good question
Leave it empty for now
Remove the overload case
13:32
:+1:
btw is uppercase in v2 twice for backwards compatability?
aww that peeking dragon wings
@TheThonnu probably not
one's vectorised, one isn't
and that peeking sky
so might make sense to remove the unvectorised one
(the one on grade up)
same with lowercase/grade down
13:53
@lyxαl just realised you have zero range already
It's the num overload of is-lowercase
oh wait that's [0, n]
nvm
Not-Thonnu pushed a commit to Vyxal/v3-add-range in Vyxal/Vyxal: Add [0..a) and [1..a]
nayakrujul opened pull request #1910 (Add [0..a) and [1..a]) in Vyxal/Vyxal
Lyxal approved #1910 (Add [0..a) and [1..a]) in Vyxal/Vyxal: "Cool beans homie. Cool beans. "
github-actions[bot] pushed a commit to Vyxal/v3-add-range in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
Not-Thonnu pushed a commit to Vyxal/v3-add-range in Vyxal/Vyxal: ‮change literate keywords
github-actions[bot] pushed a commit to Vyxal/v3-add-range in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
14:13
@lyxαl can I merge?
It's two simple commands, don't think user will have much to review
👍
@VyxalBot also
Anyhow I'm off for the night
14:18
@lyxαl is ¬ vectorised or not?
(logical not)
non
I'm still here for a little bit :p
Forgor vectoring one
Need to add that tomorrow somewhere
yeah that's what I was thinking
Anyhow bye lol
14:20
o/
Not-Thonnu created branch add-not in Vyxal/Vyxal
Not-Thonnu pushed a commit to Vyxal/add-not in Vyxal/Vyxal: Add logical not
nayakrujul opened pull request #1911 (Add logical not) in Vyxal/Vyxal
github-actions[bot] pushed a commit to Vyxal/add-not in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
Not-Thonnu pushed a commit to Vyxal/add-not in Vyxal/Vyxal: && and || as well
github-actions[bot] pushed a commit to Vyxal/add-not in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
14:43
!!/blame᠎ ‌‍⁠‍​᠎‌
Sorry Petəíŕd The Linux Wizard, I'm afraid I can't do that.
@PetəíŕdTheLinuxWizard It was parz's fault!
14:55
@lyxαl unfortunately, there doesn't appear to be a trivial way to not report merge commits
15:10
ysthakur approved #1911 (Add logical not, and, or) in Vyxal/Vyxal: "Lgtm"
ysthakur merged pull request #1911 (Add logical not, and, or) in Vyxal/Vyxal
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add logical not
ysthakur deleted branch add-not in Vyxal/Vyxal
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: && and || as well
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge pull request #1911 from Vyxal/add-not
 
1 hour later…
I'm Vyxal Bot 2.0.0 made by Ginger and Vyxal Corp.
All of my commands start with !!/
If you want help for a specific command, do !!/help <command name>.
New to Vyxal? Try !!/info for more information.

Command list: amilyxal, blame, coffee, cookie, die, goodbye, groups, hello, help, hug, idiom, info, issue, maul, permissions, ping, prod, pull, register, repos, run, status, sus
@TheEmptyStringPhotographer !!/prod(uction)? [repo name]: Open a pull request from main to production.
@thee Here's your coffee: ☕
@TheEmptyStringPhotographer !!/pull: Pull changes and restart (must be bot admin)
Sorry Petəíŕd The Linux Wizard, I'm afraid I can't do that.
🤢🤮 I hate coffee
@PetəíŕdTheLinuxWizard It was parz's fault!
Sorry Petəíŕd The Linux Wizard, I'm afraid I can't do that.
@TheEmptyStringPhotographer takes coffee back
!!/blame lame ame me e
16:29
Sorry The Empty String Photographer, I'm afraid I can't do that.
@TheEmptyStringPhotographer It was Petəíŕd The Linux Wizard's fault!
Ah you, ungrateful pig! Take coffee again!
!!/coffee thee
@thee Here's your coffee: ☕
16:33
I am a kind tiger, after all. Here's your tea:
in Charcoal Test, 31 secs ago, by SmokeDetector
@PetəíŕdTheLinuxWizard brews a cup of passionfruit tea for @thee
 
2 hours later…
18:27
@Ginger Gotta agree with Ginger
That said, does it matter if it isn't an svg?
I prefer the simpleness of the old logo (and also like the fact that it's not AI-generated), but I'd be fine with the new logo as long as drawing it isn't a problem anywhere
We need to test .toBool, ===, and similar helpers (in HelperTests)
 
4 hours later…
22:39
@user if it wasn't for elon susk I wouldn't have been interested in changing it, so blame him :p
23:15
dw, I'll make a vector version soon™

« first day (1227 days earlier)      last day (548 days later) »