« first day (1336 days earlier)      last day (439 days later) » 

02:48
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Mojo; Add lit keywords for syntax; add a new keyword for
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
03:25
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add lifts
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
 
11 hours later…
14:14
input support is now done
meaning the only thing left is the share button
 
3 hours later…
17:25
[Ginger] Bridget moment
 
4 hours later…
21:23
well, I think it's done
noice
reveal?
current feature list:
- header, code, footer, inputs
- pretty flag GUI
- automatic permalinks
- generate CGCC answer/CMC answer/quicklink
- syntax trigraph autocomplete
- element name/keyword autocomplete
- syntax highlighting
- nice terminal with ANSI escape support
did I miss anything?
deliterify?
and keyboard I guess
I plan to replace the keyboard with autocomplete; still trying to get it to work on mober tho
literate mode... isn't really supported yet?
@Ginger what
no keyboard?
21:28
I haven't written a highlighter for it
@mathscat sure, autocomplete has identical functionality
@Ginger it is, it has a few bugs tho
@mathscat no I mean in the new one
I haven't added support for literate mode beyond the flag to enable it
? literate mode is v3
oh
the new interpreter, dingus
that wasn't a question
cool cool
21:30
:p
but a keyboard or an element search would be nice tho
because of the tooltips
I mean, autocomplete basically functions as one
type a phrase and hit Ctrl-Space and it gives you a list of results
anyway, here's the UI as requested:
@lyxal thoughts?
22:01
AMiller42 created branch vyxal-fuzz in Vyxal/Vyxal
AMiller42 pushed a commit to Vyxal/vyxal-fuzz in Vyxal/Vyxal: Created fuzzer
AMiller42 pushed a commit to Vyxal/vyxal-fuzz in Vyxal/Vyxal: Moved fuzzer to separate file
@Ginger do you have plans for keyboard?
I know autocomplete exists, but keyboard provides the ability to see overloads
so does autocomplete :p
or at least it could if overloads were formatted better
Maybe instead of a keyboard you have the elements table
And have it as a scrollable reference
@Ginger on hover all at once
22:05
I made a very rudimentary fuzzer to try and identify uncaught exceptions that might pop up. You can specify the maximum size of program to try and the timeout for when it hits infinite loops. Like I said, it's really simple at the moment, and I probably won't update it all that much.
@Ginger And the ability to keyword search too
I don't expect you guys to really do anything with the fuzzer since I mostly made it for myself, but I figured I'd upload it just in case.
Ngl thought a fuzzer was to do with fizzbuzz
@lyxal already exists
22:07
the element autocomplete uses fuzzy search on both the name and the keywords
and how's this for overloads:
I meant a search outside of the code box
I like to be able to hover over everything to see what exists before commiting to typing something
@lyxal where outside of the code box?
where do I fit the table in
A tab, a div to the right or left, something toggable from top bar
Somewhere like that
22:09
hmmm
there are a few ways I could do that
@Ginger also, that doesn't show literate keywords
as I said, literate mode isn't done yet
(plus I have no clue how it would, since afaict that data's not in the keyboard's data file :b)
No but like the current keyboard has it as part of the tool tip
whuh? how
@Ginger it should be
22:10
I'm using all the data in that file to generate autocompletions
unless I missed something...
ohhhhh is that what keywords are?
that makes sense lmao, lemme add that real quick
@Ginger yes :p
options for element table:
- make it a tab on the code stuff UI
- make it a tab on the terminal
- make it an offcanvas (drawer that slides over the screen) triggered by a button in the topbar
Offcanvas I think
okay, I sure hope I can stuff another button in that bar d:
it's already quite cramped on mobile
how's this for keywords?
22:28
AMiller42 pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Catch empty generator
@AaroneousMiller what's the point?
Basically just to identify uncaught errors
GingerIndustries pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Fix Aaron not being idiomatic and causing the workflows to fail
:skull:
I ran jvm.reformat, I assumed it included stuff like that
guess not
22:42
@Ginger I am translating languages.
delicious
iono man, I definitely did the reformat
@AaroneousMiller For example, fun fact: If scans a modifier, bad things happen, even if the modifier is completely syntactically correct. Try it Online!
@Ginger I'd prefer them to be a bit more obvious/pertinent
how so?
I can put arbitrary HTML in the info box, so tell me what you want and I'll do it
Perhaps in the name box
Like where it has the name and symbol
22:45
that's definitely not going to fit, especially for elements like this:
which uh doesn't seem intentional
[user] I think there's Scala libraries for fuzzing, to make it a bit easier
@Ginger ruh roh the description has leaked into the keywords
@Ginger [user] Just use ellipses
[user] Oh wait yeah
@Bridget too late, I'm lazy
@lyxal there are a pretty large number of elements like that, from a cursory glance
22:46
[user] I didn't notice that
@AaroneousMiller [user] Fair enough
@Ginger *modifiers
It happens for all the modifiers it seems
thingies™
Which is probably because modifiers have a different data layout to elements
[user] If you want I can take a crack at using a fuzzing library (if it ends up being simpler/faster than your current code, it might be unnecessary complexiry)
right, I'm going to go ahead and commit the new code so yall can take a look at it (specifically the highlighter)
it's done :o
no going back now
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: fix order of modifier keyboard info
@Bridget go right ahead. It was hacked together in like half an hour, so I don't really care either way. In all honesty, I just wanted something to do, and I figured having a backlog of uncaught errors would keep me busy for a while. So it's really just a means to and end
@Ginger fixed
yay!
22:51
the keywords and description were around the wrong way
for modifiers
12.5k additions holy frick
[Ginger] if y'all wanna try out the site just checkout the branch and do npm install && npx webpack serve --progress
[Ginger] the highlighter is in src/latest/lang-vyxal.ts
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
[Ginger] please do tell me what you think of it, we value your feedback
I'll do that a bit later
I've decided I'll be doing the unthinkable and making a userscript today
22:57
[Ginger] :gasp:
[Ginger] what for?
Smokey
[Ginger] whar he doing
there's a userscript called "Smokey Pings After Message"
problem is that sometimes my headphones are connected to my phone
and I don't get to hear the pings
so I'm gonna make a modification to send it as a push notification
I know I said I was only ever going to make one userscript, but I did include the word "probably"
[Ginger] when'd you say that?

Lyxal's first and probably only userscript™

Apr 14, 2021 at 5:24, 8 minutes total – 29 messages, 4 users, 0 stars

Bookmarked Apr 15, 2021 at 12:58 by lyxal

23:06
lol I forgot about that script
23:32
@lyxal this is a rickroll, isn't it
No
doubt
[lyxal ♦️] How come those three messages didn't show up here?
I don't know, Bridget's been being weird lately
[lyxal ♦️] Probably that chat outage
23:35
Restart it?
already did
@lyxal so I try and run this in the console and it immediately starts opening hundreds of debuggers
Huh
Interesting
@Ginger technically I didn't lie
It's a 50% chance of rickroll upon visiting homepage
So not 100% a rickroll :p
[Ginger] I was pretty sure something was up d:
But the debugger thing tho I didn't make it do
it appears to be one of the options for the top Google result for "javascript obfuscator", which I suspect is what you used

« first day (1336 days earlier)      last day (439 days later) »