BUG: Command box ignores unambiguous command

Randy W. Sims

Typing an unambiguous command to open passage does not correct set that command as default. EG.

open passage guide to jn3.16

defaults to Open Passage Study Layout to John 3:16

If an unambiguous command is entered it should execute that command as the default.

Find more posts tagged with

Comments

MJ. Smith

Driven me nuts for years but the behavior is consistent. It is selecting the first item in the drop-down list if you have not selected an item from the list. This happens in a number of select boxes. It does have one advantage: it gives me lots of time to twiddle my thumbs while waiting for the list to populate. This results in very agile thumbs despite a bit of arthritis.

Reuben Helmuth

It does have one advantage: it gives me lots of time to twiddle my thumbs while waiting for the list to populate. This results in very agile thumbs despite a bit of arthritis.

🤣😂🤣

There really is no reason that disambiguated commands can't be respected (and auto-populate should defer to fully typed and executed commands).

Randy W. Sims

Driven me nuts for years but the behavior is consistent. It is selecting the first item in the drop-down list if you have not selected an item from the list. This happens in a number of select boxes. It does have one advantage: it gives me lots of time to twiddle my thumbs while waiting for the list to populate. This results in very agile thumbs despite a bit of arthritis.

[:D]

I recall this being discussed a few times before though I didn't look it up. The behaviour is ok for ambiguous commands but if a user types an unambiguous command it ought to be obeyed. I don't see justification for any app to do something different than what a user asks it directly and unambiguously to do. Ideally, it should also do it immediately. I typed the command and pressed enter and it still had to wait a second to finish building the completion list before executing (on a brand new Windows install on a i9 w/ 32GB RAM!). That could at least be hidden if not aborted as soon as a user hits enter.

Andrew Batishko

Unfortunately, the application does not know that the command is unambiguous until it finishes checking for all the different possible options for what the command might mean, so there isn't really a good way to speed this up.

MJ. Smith

Andrew, the problem isn't just time ... but that it overrides the command see the OP

Andrew Batishko

Typing an unambiguous command to open passage does not correct set that command as default. EG.

open passage guide to jn3.16

defaults to Open Passage Study Layout to John 3:16

If an unambiguous command is entered it should execute that command as the default.

We can do something like this, but only if you enter an exact match (ignoring case sensitivity). So, you would need to enter open passage guide to john 3:16

However, we are also combining this with promoting groups that you have recently run commands from ("Look Up", "Layout", etc), which may also improve things in every day use.

Randy W. Sims

We can do something like this, but only if you enter an exact match (ignoring case sensitivity). So, you would need to enter open passage guide to john 3:16

So there will be no bible ref notation expansion? eg. jn3.16? That's disappointing but still a huge step forward. Thank you for that.

Philana R. Crouch

Typing an unambiguous command to open passage does not correct set that command as default. EG.

open passage guide to jn3.16

defaults to Open Passage Study Layout to John 3:16

If an unambiguous command is entered it should execute that command as the default.

This has been improved in 8.4 Beta 2.