PidgeyUsedGust

I tried converting this answer to Jelly as follows, e.g. by creating a map to convert everything to e and using y, but I'm doing something wrong, any pointers?

That's pretty genius indeed!

Yeah, I saw that some new cases were added.

@JonathanAllan for codegolf.stackexchange.com/questions/111477/… I was trying something with finding the first pair from ØypØY into the input, but didn't have any success in getting to work.

Tried adding explanation to my answer, does it make sense? I hope I didn't make any mistakes. Or can it be golfed even more?

Beforehand, apologies for the many questions! But I'm not entirely sure how the order of arguments to dyads is determined. Say I have a monadic link that generates a list (e.g. 24Ḷ) and I want to index the argument. I got it working with 24Ḷ³ị, but I'm not entirely certain why it is required like this. Intuitively, ị24Ḷshould do it, but that just returns the list.

What's the shortest way to indefinitely loop code?

I use my own interpreter with debugging support, I might add the -v as default if nothing else is given.

I think it should be allowed because it's just a way of telling where to find input. Forcing to use i seems quite punishing.

How many bytes is the -v flag for ><> again?

Because, well, it might be part of the difficulty of the question to figure out the coordinates.

I asked in the question.

Yeah but where's the boundary for reasonability?

would {(x, y, v)} with v in [queen, no queen] be a valid input format for this question? Computing them in ><> is a pain :).

now with an explanation!

@DJMcMayhem happy f***cking birthday, V!

Is there a better way than 84* for pushing a space in ><>?

Damn, I hope with the bounty on the unknown turing completeness question no-one will run off with the idea I'm developing

1 ~ to go

I only need to fit 3 more instructions in my ><> program, soo close!

Any comments on debugging interpreter for ><>?

almost done with debuggable ><>!

to enable some sort in debugging in an interpreter

Would there be a way in Python to wait for user input without breaking buffered input on stdin?

Thanks

@MatthewRoh I had a similar idea of a graphical stack based golfing language about 2 weeks ago, do you have a place where you share ideas, maybe I can tag along?

I should really add debugging to fish.py

I get a 502 though

fishlanguage.com down for anyone else?

I'm still working on wishing V a happy birthday

@MatthewRoh I had a similar idea of making a stack based graphical golfing language like two weeks ago! Based on the Google logo challenge.

is there a ><> interpreter with debugging except from fishlanguage.com?

I was trying something very stupid

ah, thanks :)

I want to push the length of the initial stack to another cell for later comparisons.

Anyway to use p in ><> as a value push, rather than a push as character?

allowing the \n in turn allows for quite a nice ><> golf

True.

But still it kind of feels like cheating.

In this question if you use echo "string" | to fill stdin, can you abuse the fact that echo provides the \n or does it come with a penalty?

That's a strong right arm!

Somehow it won't print though

Thanks! ¯_(ツ)_/¯

Such a pity that the cool golfing language answers are immediately taken ¯_(ツ)_/¯

anyone?

Do answers in <>< need to count the -v flag when input is needed?

What's a good format for explanations for <><?

I didn't

Alright, thanks!

@Dennis which brainfuck implementation does TIO use?