when using ~ for a menu separator, you can only use one, the rest dont work. same for scripted menus.
This is just a documentation failure (sorry). Use ~1 for the first one, ~2 next, etc. (Actually any unique strings starting ~ will do.)
can [menus V] of block (()@addInput) be updated for this?
Why? Once you've made the menu, the different dividers all act the same.
set [menus V] of block ((test block::command)@addInput) to ([menus V] of block ((another block :: command)@addInput)
thx
There's a 
emoji with :tuit: I feel like you know but probably just forgot?
Yeah. Getting old. :~/
also, if jens is notified about this, the other thing I forgot to say is that primitive block menus are also messed up, because each separator uses ~, not ~1 ~2 ~3.
Thank you, I'm sure Jens will want to know this.
:)
also, I don't even know if what you said earlier works:
yes you can.
I'm extremely annoyed by this. I'm reading every single post in this forum and most of it is just from people who haven't published one. single. interesting. project and are only jerking around with metaprogramming and splitting hairs. We've made Snap! to foster creativity, self-expression, authorship, and learning CS principles. And all I'm ever seeing is bureaucrats. And I'm really restraining myself from getting mad, and then Brian hits me up with a direct message. Guys. Program something nice and interesting.
The direct message was about the problem for primitive blocks.
there is no problem. Some features are under construction and some will be under construction for longer. I'm sure @sathvikrias has plenty of opportunities to explore his creativity.