« first day (1290 days earlier)      last day (483 days later) » 

03:47
@Ginger if you're looking for bot features that would be useful for everyone, I've got something
!!/deliterate
convert literate to sbcs
!!/deliterate "6 9 add dup even? times"
@lyxal 6 9+:e×
for example
the hard part would be interfacing with the lexer
although there's the option to use the jar, the native executable or the js
04:15
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Add more modifier tests; Add floor and ceil; move all neighbours equal to ᵘ
pre-commit-ci[bot] pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: [pre-commit.ci] auto fixes from pre-commit.com hooks
github-actions[bot] pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
04:57
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Make until no change include first value
I did ^ completely on mobile
No clue if it even compiles
Ah
It doesn't
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Update MiscHelpers.scala
pre-commit-ci[bot] pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: [pre-commit.ci] auto fixes from pre-commit.com hooks
Well hey that's good news
That means it compiled
Ah no
It didn't
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Update MiscHelpers.scala
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Update MiscHelpers.scala
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Update MiscHelpers.scala
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Revert it and see if this fixes it
pre-commit-ci[bot] pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: [pre-commit.ci] auto fixes from pre-commit.com hooks
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Splat probably would go at the end
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Ah right you don't need from
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Update MiscHelpers.scala
Lyxal pushed a commit to Vyxal/v3-resume-implementing-stuff in Vyxal/Vyxal: Actually use ceiling for ceiling
06:07
@lyxal niiice
06:46
(not actually implemented yet :p)
 
2 hours later…
08:22
Lyxal opened issue #1956 (Modifier tests) in Vyxal/Vyxal
Lyxal opened issue #1957 (Check element tests are complete) in Vyxal/Vyxal
Oh
Well I guess that's okay
Lyxal opened issue #1958 (Move reject by element to be a dyadic overload of zip with) in Vyxal/Vyxal
Lyxal opened issue #1959 (Add a few more collector overloads) in Vyxal/Vyxal
Lyxal opened issue #1960 (Playtest the built-in set on some code golf questions) in Vyxal/Vyxal
Lyxal opened issue #5 (Make the dictionaries work online again) in Vyxal/vyxal.github.io
Lyxal opened issue #6 (Make versioning a thing on the website) in Vyxal/vyxal.github.io
Lyxal created repository Vyxal/Release-Prepping
Lyxal created branch main in Vyxal/Release-Prepping
Lyxal pushed a commit to Release-Prepping/main in Vyxal/Release-Prepping: Update README.md (@Ginger is it possible to ignore releases from certain repos?)
Lyxal opened issue #1 (Create the js move to pages branch thing) in Vyxal/Release-Prepping
Lyxal opened issue #2 (Test the release process to make sure all binaries are generated properly) in Vyxal/Release-Prepping
09:14
Hey @Ginger I came up with another thing that would be a good feature for the bot
!!/trash message-start message-end
@lyxal Command error: Unknown command.
No vyxal bot that wasn't for you to respond to
Anyhow it'd make the bot move a range of messages between start id and end id
Only moving messages present in this room
 
4 hours later…
12:46
ah
looks like dyadic modifier parsing might be broken
13:21
It's not the parsing
Rather, it seems to be that the context copy method I made doesn't seem to be deep copying the stack
The program I'm testing is:
4 5 <!!>: <!!>: + - +
Which works fine in its v2 equivalent
There's something about the nested modifier that is making it consume things it shouldn't be consuming
Some sort of accidental implicit somewhere
13:50
@lyxal is this in literate mode?
@lyxal thanks for the suggestions! I'll get started on them ASAP
@lyxal is the JAR capable of deliterateing input?
(like via a flag or smth)
I think so
l I believe
one sec
14:20
hmm nope
-l directly runs the literate code
You can access the lexed tokens though, eg. -l: 5 6 add -> List(Number("5"), Number("6"), Command("+"))
actually, I have a better idea
14:35
also:
@lyxal possible Vyxal logo design:
(inspired by your pfp)
 
2 hours later…
16:19
@mathscat Regarding this, would you need to insert a space between any other tokens except Number, Number?
I can't think of any off the top of my head.
If yes, then !!/deliterate shouldn't be too hard to implement
 
1 hour later…
17:28
@lyxal why is the v3 interpreter at the toplevel vyxal.github.io domain?
I'm of the opinion that we should have an official website instead of the scattered set of like 3 sites we have now, but having the interpreter at the toplevel domain means we can't put anything else there
one of the reasons for using scala was that the build can directly be hosted on github.io without relying on third-party websites like pa
but an official website does sound cool
18:01
@Ginger We could make it be at vyxal.github.io/interpreter if you want
There just isn't anything else to put at the toplevel domain right now
yes, please do before it's too late
No docs and stuff (we could move stuff from Vyxapedia to vyxal.github.io)
@Ginger That sounds...ominous
once v3 rolls out and permalinks start getting made we won't be able to change it
Ah good point
18:12
oh that's what you meant
Do we need a checklist or something of that sort for everything related to the interpreter / external stuff?
just to keep it all in one place
@user I propose /run or /vyxal :d
Good idea, /run is nice and short
@mathscat Sure, you could make an issue in the vyxal.github.io repo
 
3 hours later…
21:33
@Ginger there won't be a too late
oh really
If we need time to think about things like that, we'll take that time
No rushing into things
As long as is needed to make sure everything is set up smoothly
ah
good to hear
 
1 hour later…
23:00
@Ginger not yet
but it can be made to be
@Ginger actually, the JS already exports a deliterate function
@mathscat see ^
it's already a solved problem :p
the bot could simply run a request to a github pages endpoint
  /** Convert literate mode code into SBCS mode code */
  def sbcsify(tokens: List[Token]): String =
    val out = StringBuilder()

    for i <- tokens.indices do
      val token @ Token(tokenType, value, _) = tokens(i)
      val sbcs = sbcsifySingle(token)
      out.append(sbcs)

      if i < tokens.length - 1 then
        val next = tokens(i + 1)
        tokenType match
          case Number =>
            if value != "0" && next.tokenType == Number && next.value != "." &&
              !value.endsWith(".")
23:23
@lyxal Proposal to rename sbcsify to illiteratify :P
23:44
@lyxal what do you think of the logo image I uploaded
you just had to edit that didn't you :p
@lyxal not sure how this'd work, since Pages is static
@lyxal that's what we in the business call a "close one"
@Ginger what does it symbolise?
awesomeness :p
@Ginger it's also called "two dead body report noises" :p
23:46
AMONGUS
@Ginger I'll change it when I don't have exam prep to do (i.e. later today)
so you're using it? spicy
what for?
the orgaisaetob
imagin that says org and wasb;t tyo\ped one handed
right
and I guess the lang inherits it dues to being our primary project
yes
23:52
GingerIndustries pushed a commit to VyxalBot2/main in Vyxal/VyxalBot2: Make reactions case-insensitive

« first day (1290 days earlier)      last day (483 days later) »