for instance BS using for BlendSrf or FS for FilletSrf
when i turn off instant it works as usual, of course also when i run the command without alias.
that has started quite some time ago.
I sure hope fixing all the unintended consequences of this utterly nonsensical rip-off-other-programs-that-don’t-working-anything-like-Rhino idea doesn’t break Rhino’s actual functionality.
I don’t see why it would break anything in Rhino. I wrote this as an optional feature that users can enable and use if that’s the workflow they prefer. The feature essentially does not exist unless you enable it.
besides the frustrated random off topic rant that has in sum less than zero to do with the issue, how do you think Rhino came about? you think NURBS, Meshes, let alone CAD generally is something unique to Rhino? or computers? your contribution is certainly not making the world a better, safer place.
We need the Gordon Ramsay version of the cad world, sometimes we all need to pull our heads from our asses and get a breath of fresh air called reality.
Filters out the bullshit and gets straight to the point.
the only truth about reality is that it keeps changing constantly.
and repeating in other settings 
@encephalon have you tried tuning the delays for those a bit?
It may help…It may not. But it’s worth a few min of fiddling to see.
absolutely, but while some commands may repeat so gleefully the mood may not. 
i rather not, generally Instant Alias Delay sounds like an oxymoron 
so i finally managed to sit on a computer to check your suggestion. i had set it to 0 because i did not want any delay at all. i understand the idea behind the delay of course and here i would wish that the setting could apply to specific aliases and not just overall. then some could trigger instantly while others open a layer of nested instants.
anyway it now works setting it to 1 ms which is probably as close to imperceptible as it can get even for the most impatient of us. thank you for the suggestion! i can not mark it as a solution though because it should still not happen, still a bug, even if its just a teeny weeny 1 ms bug 
glad that is working for you now.
The delay value being greater than zero is as designed and is necessary for the system to function.
you may find the need to change that value even a bit higher if you have aliases with more than a keystroke or two. For instance I have several that are 3 keys and I have my delay set to 300 ms.
I tend to model very fast and so far this is has not caused any stumbles here.
Of Course, your mileage may vary, adjust that delay value to your own preferences.
not sure why it would need a delay suddenly, it worked flawlessly having it set to 0 before.
reasons.
i also have reasons to type up bugs, its not for my amusement though.
and reporting stuff that is breaking non stop and not even getting explanations for it on the other side is quite ridiculous indeed.
Sorry about this, I do appreciate your bug report and am getting it added to our bugtracking system. I’m able to repeat what you are seeing