Some commands not auto-completing

Something has just popped up where some commands like say BlendSrf and MatchSrf have to be fully typed out.

It looks fine on my side, and I tested it in RhinoWIP (9.0.25362.12305, 2025-12-28)

Nope it’s not working here. I also see one of my macros doing the same thing. Turning “use fuzzy autocomplete” back on fixes it.

The latest WIP has fixed this on some commands but not all…

So the 01-13 WIP has many commands fixed but still not all…?

I haven’t found any issue in my testes. Could you please specify which commands are currently not functioning properly on your end? Thank you.

Hi,

HideSwap and LockSwap are two…

It works properly on my end, and fyi.

Not here…

Also UntrimAll isn’t working.

And ExtendSrf.

UnlockSelected

MatchSrf

Scale1D/2D

Selobjectswithhistory

Selparents

These autocomplete for me if I type HideS or LockS.

These autocomplete for me if I type enough characters to make the selecting unique.

Work In Progress
(9.0.26013.12305, 2026-01-13)
Windows 11

Funny, none of those working here.

Are Autocomplete commands and Use fuzzy autocomplete on in Options > Rhino Options > Appearance?

Also in Options > Rhino Options ? Advanced there is AppearanceSettings.popularity_based_inline_autocomplete

I have “fuzzy autocomplete” off, as one should.

I have “fuzzy autocomplete” in V8 and V9, and do not recall any problems.

Autocomplete works in V9 if “fuzzy autocomplete” is on, and does not work if it is off. That is the cause of what you are experiencing.

Autocomplete works in V8 independent of whether “fuzzy autocomplete” is off or on.

The effect of “fuzzy autocomplete” has changed between V8 and V9. No idea if the change was intentional.

It’s bad gimmicky interface design, always has been.

Yes…? It works on many commands just not all, enough to make the WIP unusable.

Hi Jim -

I’ve written this up as RH-91508 Autocomplete: Fails without Fuzzy Autocomplete

Off-topic: I would discourage users on Discourse to edit their posts to add important information. Unless that modification is referred to in a new post, that information will not be seen by anyone who read the first version of that post.
-wim

Thanks Wim. Based on the notes in RH-91508 it looks like it has been fixed. I assume we’ll see it next week’s release.

So far so good with the latest WIP.