« first day (18 days earlier)      last day (182 days later) » 

01:34
@MDXF Oh thanks
I just deleted my answer on another question. Thanks for letting me know xD
 
3 hours later…
04:21
Oh lol... I had to do that too a while back
 
12 hours later…
16:09
MD XF has made a change to the feeds posted into this room
16:25
5 messages moved to trash
 
2 hours later…
18:03
@MDXF How does the interpreter handle U³2²4?
Does it rotate layer 3 twice, then layer 2 four times?
Also, which layer does U³²3 rotate?
Also, do you have a table containing the values of each character? I'd assume the first 128 characters are the same, but where do the superscripts fall in?
For now, I'll just assume the superscripts are decimal 128-137, but I'll change that once you reply.
18:30
@TehPers No, superscripts are command-dependent, not turn-dependent. So U³2²4 is equivalent to U³2 U³²4.
@TehPers It tries to rotate the 32nd layer, but if the cube is not large enough to handle it, it doesn't do anything.
@TehPers Cubically's codepage (table) is printable-ASCII-compatible, but the control codes are different (with the exception of the newline and the tab). The superscripts are 0x00-0x09 in Cubically's codepage and seemingly random values in UTF-8.
Okay, thanks!
I'm working on implementing the codepage
@MDXF I think it'd be better if this behaved as "rotate index 3 twice, rotate index 2 4 times". It just makes more sense in my head. I can't really justify it past that xD
@MDXF ?
@TehPers Proposition for a Rubik's Cube Stack Exchange :D
@MDXF I think that'd be better off as part of the Mathematics SE site
A lot of cube-related things aren't particularly on-topic there
It isn't?
I feel like it should be o_O
If not there, then where?
18:52
The first two things in Rubik's SE's description would - mathematics, theory - but the other things are less so - algorithms, solutions, permutations, mechanics, or design.
Of course, you might be right, it might get closed as a dupe of that; however, PPCG's "Esolangs SE" proposal has gotten closed as a dupe of Programmers SE... and questions about esolang development are most definitely not going to be well-received there.
Idk
I'm gonna look at how Jelly handles the codepage
19:53
Jelly performs conversions, the C interpreter doesn't. Idk which would be easier to do in Lua
I already have utf8 to char array
Oh sweet
Basically, I'm converting the string (program) to the UTF-8 character array, but each element in the array is actually the byte value of your codepage, or -1 if it doesn't exist in there
Then it can be converted to characters, where � is used for unknown characters
� is not part of the codepage. It's just used for characters without a spot in the codepage, like decimal value 184, or decimal value -29
Good idea
20:09
@MDXF It's just for the way my conversions work, not a suggestion for the language xD
Anyway, will superscripts only affect layer selection?
I know lol, I'm just saying it seems like a simple, efficient and foolproof way of doing it
Or will they be used for things in the future?
Superscript numbers will only be used for layer selection
I haven't decided whether or not superscript letters/symbols will be included in the codepage
@MDXF How else will you handle them?
That's the thing; I don't know. They will likely be useful for something in the future; they're not right now.
20:13
@MDXF Why not use subscripts instead?
How come, i.e. what makes subscripts better than superscripts?
Or do you mean use them for something else?
@MDXF Superscripts are used for exponentiation, and subscripts are more used for indexes in math
Like t_0, for example
That is true
Or F_0, F_1, F_2, etc
Has anyone used the superscripts on PPCG yet?
20:15
TIO doesn't support them yet
So no
I tried earlier...
Oh huh, must have been recently updated?
They're a bit broken but AFAIK they've generally worked for a few days
shrug
Regardless, nobody's used them yet
Just did a search
On an unrelated note, if you install chatcommands (via tampermonkey or something), typing /shrug in chat will auto-insert the shrugging emoticon xD
@TehPers Oh ok that's good
20:18
@MDXF shrug
Just in case someone had plans, until we find some other use for superscript numbers, I'll make them compatible, so you can use superscripts or subscripts to define layer depth
@TehPers lol
@MDXF Ok, I'll only support subscripts
Sounds good
Oh phew, Unicode subscripts are actually convenient
21:07
@MDXF In response to the issue with arguments being passed in from input, maybe allow superscript x do that? The thing is, this can also be done by setting the notepad to your input (or whatever) and decrementing it in a loop
What is the exec command?
@TehPers That's a great idea!
@TehPers Which exec command?
@MDXF Nevermind
Also, check the issues on your repo
@MDXF What would be used for input, what would be used for face value, and what would be used for notepad?
If you need uses for superscripts, you could do that I suppose
I'd have preferred a bit of consistency, where digits are constant values and superscripts are cube/notepad/input values
But it's too late for that
Hmm
I have another idea.
I'm a bit confused
Um
So you want to rotate the face 2 times? You can do R2.
Yeah
21:21
You want to rotate the face a number of times equal to the input, you can do R2 with a dot over the 2 or something
or hm
Idk
Why 2?
I want this to work in subscripts too
2 was just a random number
Give me a sec to think
Meaning you want R₁(foo) to work, where (foo) is whatever takes input as the argument?
That'd be the value of face 2
or something like that at least
Oh I see!
21:23
Basically, it'd be cool if you could do Rx, where x is the value of a face
Also Rₓ, aka rotate layer x
So R2 would rotate the right face twice, while R2ͯ would rotate the face index stored in face 2 twice
It'd rotate the right face x times, where x is the value of face 2
Yeah exactly, I just couldn't think of a good way to phrase it
And Rₓ₂3 would rotate the right face, x layers in, 3 times, where x is the value of face 2
Actually
Rather than messing with the numbers
Why not create another command?
Use a R with a circle over it or something
Hmm
21:30
The thing is, you'd need to support passing variables in as arguments and subscripts
If you're only going to have face rotation as letters, then you might as well create variants of it
the issue is, then they'd take 24 characters from the codepage on their own
Versus using superscripts for constants, and the digits for the value of that face (it's too late to do this though)
Well, I do have at least 127 more codepage slots open.
That's true
Dz is one character..?
Dz Dz
shrug
There are lots of much weirder Unicode characters, trust me xD
Number Forms is a Unicode block containing characters that have specific meaning as numbers, but are constructed from other characters. They consist primarily of vulgar fractions and Roman numerals. In addition to the characters in the Number Forms block, three fractions were inherited from ISO-8859-1, which was incorporated whole as the Latin-1 supplement block. == List of characters == == Block == == History == The following Unicode-related documents record the purpose and process of defining specific characters in the Number Forms block: == See also == Unicode symbols Latin scrip...
You could try using the roman numerals xD
@TehPers which Unicode character is this?
21:37
@MDXF ͯ
I see an empty message...
Is that a really really really tiny 2?
@MDXF No lol
Unicode has subscripted and superscripted versions of a number of characters including a full set of Arabic numerals. These characters allow any polynomial, chemical and certain other equations to be represented in plain text without using any form of markup like HTML or TeX. The World Wide Web Consortium and the Unicode Consortium have made recommendations on the choice between using markup and using superscript and subscript characters: "When used in mathematical context (MathML) it is recommended to consistently use style markup for superscripts and subscripts...However, when super and sub-scripts...
overscript miniscule x
xͯxͯxͯxͯxͯ
Oh lol. I meant which character is
r᷊ͬr᷊ͬr᷊ͬr᷊ͬr᷊ͬ
2ͯ`` is two characters lol (I give up)
Ah
We could use the U+1D7CE through U+1D7D7, mathematical bold characters
Or the U+1D7F6 monospace numbers
21:43
Are those digits?
Sure, that'd work too I guess
I think everything around U+1D7F6 is digits in different fonts
Scroll down to around the bottom of this
I like the bold ones since they stand out
But maybe the double striked ones?
𝟞
Either bold or double-striked, monospace will look the same as normal characters in most text editors and IDEs
They look very different, easy to spot the difference
Yeah. I don't really care, which would you prefer?
21:46
➀ lol
I prefer the double striked ones
More options on that page
Assuming this is the method used anyway lol, I've been adding all (two of) the possible methods here
I like it though
dingbat negative circled 1
What even is Unicode these days
Dingbat, that's what.
Lol
Oh my it goes farther: ➊ dingbat negative circled sans-serif digit one
Yep.
Is there anyway to rotate layer x? well with all these insane Unicodes there's probably U+FOOBAR subscript double-struck wingdingbat 2
21:51
Lol.
Assuming I understood your comment correctly - you mean is there a way to pass an argument to R (or L or whatever) telling it to turn the Xth layer, where X is the value stored in the argument passed?
Yes.
"Rotate layer x from right face twice, where x is the value of face 2" for example
Ok... that's also a good idea. Maybe that's what the bolded numbers could be, if we use the double-struck numbers for the number of turns?
So R𝟏𝟚 would rotate x layers in from the right face y times, where x is the faceval of 1 and y is the faceval of 2
It doesn't look consistent though
I'm thinking it'd be better to just ditch all of this and use a fancy looking x or n to indicate you want the input from the arguments
Though again, I'd prefer to just rewrite the language from scratch
Actually, hm
Would it be a bad idea to make a new RLUDFB command using a unicode character
And the layer will be taken from the face value instead?
It would be easier than rewriting the language and wouldn't invalidate all Cubically answers xD
I'm a bit confused about what's inconsistent about R𝟏𝟚; I might not be understanding what you mean by "consistent"
21:57
Subscript selects the layer
Oh yeah
Well now I'm just wondering... how useful will it actually be to take the layer as input?
It's something I'd like to add, and a good feature, but is it useful enough that it's worth either rewriting the language or using up most of the codepage slots?
Being able to store a value on a layer would be cool...
Select layer x, rotate it to face 0, do something, rotate it back
I don't know how possible this is
Hmm
I have a (possibly) better idea (might be alot worse)
I could make the notepad a tape instead of just a single value
Anything that lets us store more than one value at a time would probably make this language Turing complete
It'd make Cubically alot easier to use, but at the same time, it would remove some of the fun and the story behind it
Yeah actually it would completely remove the necessity to use the cube at all... it would basically make the language an extension of Brainf**k, especially since Kamil found a way to increment/decrement the notepad regardless of face values
22:04
@MDXF I don't really know what to do about that.
Just being able to select a layer would probably be enough
R₁1U₁1L₁1
Yeah maybe...
That will set the value of the middle layer in a 3x3 to 1
R₁1U₁1L₁1D₁1 this does it cleanly
Man, I don't know, maybe you can use the subscripts to select the value of a layer of the face?
I can't think of a way to store multiple values on the cube
Didn't Kamil find some 'cube incrementor'?
Yeah, but you can't store 2 values on the face
And the max cube value is 1259 for a 3x3
> multiple values
duh >.<
@TehPers How is that number so freakishly close to 1260?
22:08
The max period is 1260
giving you the values 0-1259
Oh so they're related. I see
... on a 3x3, at least
Yeah
Regardless, you can't pull a value from the cube, manipulate it, and revert the cube
If you take the value from the cube, and you store it in your notepad, you can't return the cube to the state it was in without messing up your notepad value
Meaning you can't duplicate a value
Speaking of 1260, I'm trying to find the max periods on larger sizes
1
Q: Determine the highest order of an element of a Rubik's Cube group

MD XFThe period of a sequence of moves on a Rubik's Cube is the number of times it must be performed on a solved cube before the cube returns to its solved state. For example, a $90$° clockwise turn on the right face has a period of four; a $180$° clockwise turn on the right face and a $180$° turn on ...

22:11
@MDXF How does that help you duplicate a value?
Actually, never mind. It's useful for returning the cube to a previous state, just not an unsolved one. I was distracted sorry xD
Another question: Would X, Y, and Z commands be useful? They'd do what they do here
@MDXF From what I read a while ago, this is really difficult to calculate
@MDXF I can't connect to that site
That's odd... some sort of internet restriction?
@MDXF I mean, I'm at work if that counts.
Lol maybe. My work restricts the internet archive for some reason
22:18
shrug
Anyway. X is basically R1R₁1R₂1
That'd do exactly nothing...
Y is U1U₁1U₂1, Z is F1F₁1F₂1
@TehPers how so?
@MDXF Because it'd be the equivalent of turning the cube sideways in your hand.
Pretty sure most cube solvers don't even rotate the middle face
Well that's the point; it'll switch around some face indexes. Might be useful, might not, doesn't hurt
22:24
I guess so...
I'm still looking at how to store multiple values at once
A lot of time seems to be spent on trying to do constant operations, like decrement and increment
It'd be neat to use the cube to store memory, but you also need it to provide constant values
Hmm
I don't know.
I'm gonna make a spinoff of the language with my ideas.
23:05
@MDXF I'm rewriting the language and reorganizing the codepage, as well as changing a lot of operators. I'll show you when I'm done, and hopefully that gives you some ideas.
23:21
All right, sounds good
I'll look into redesigning the codepage
Maybe, since we don't have any use for superscript numbers, subscript x could set the layer to x, and superscript x could set the layer to the face value of x?
It works, it's simple, and mostly consistent.
@MDXF You'll see what I have in mind.
I gotta go, but that's the start of it
So pretty similar to what I said earlier? since subscript for constant layer selection and superscript for face value layer selection

« first day (18 days earlier)      last day (182 days later) »