-read-only behaviors differ

[therube]

-read-only behaviors differ, compared to not -read-only


Just noting that some behaviors differ if -read-only is set.



like "typeahead fast" (or whatever if might be called where you just start typing characters in the Results window)
- finds only 1st. char
- type: "0123"
finds: 0 1 2 3 (that is AN item that starts with 0, then, AN item that starts with 1, then,...)
rather then an item that starts with "0123"


(Other behaviors also differ.)

[void]

-read-only shouldn't affect the "jump to" search.

I haven't been able to reproduce the issue my end.

Maybe this is an instance issue?

Are you using a unique instance with -read-only?
Any notable setting changes listed under Help -> Troubleshooting Information?

[therube]

Are you using a unique instance with -read-only?

Yes, that would be the case.

Any notable setting changes listed under Help -> Troubleshooting Information?

I'll have to take a look...

[therube]

-read-only is not the issue.

jump_to_timeout=0

(once i found out where the particular instance with the issue was...)
who knows. maybe i was ... no clue?
maybe wanting to set it to "default", with the thinking that 0 was "default", but default is actually 1000.
or maybe... who knows.

so that was that issue.
& yes, this i must have done.
how, why, where... or how that got set in the particular -instance, got me.