(Global) keyboard shortcut to look up passage in preferred Bible

You have several options for a Search - the Command box, the search, panel, the inline search, the context menu search .. Alt+D takes you to the Command Box; Alt+S opens a search panel, Alt+Shift+S opens a search panel from a floating window; when the search term is in the command box Ctrl+Enter will search top Bibles; Ctrl+Shift+Enter will search the entire library. I think that covers the available options.

Basically, often Logos gets confused and sends me (several times a week) to Passage Study

I suspect the program is doing what you requested ... your cursor must be positioned on the desired entry in the drop down menu when you hit enter. If the menu was still populating when you made your selection, it can appear random as the continuing population of the menu changes what your cursor is on.

https://community.logos.com/discussion/comment/1169461#Comment_1169461

Thanks for the reply. None of those does what I'm looking for, though. "Look up the passage in your preferred Bible" seems fundamental to me. Honestly, e-Sword was much quicker and better in this (small) respect. Why not add a keyboard shortcut for it (like Ctrl-Enter) in the Command Box? (Like Alt-Enter, for example?) And why not fix the Ctrl-Enter bug and Shift-Enter bug that I mention above?

https://community.logos.com/discussion/comment/1169461#Comment_1169461

I suspect the program is doing what you requested ... your cursor must be positioned on the desired entry in the drop down menu when you hit enter. If the menu was still populating when you made your selection, it can appear random as the continuing population of the menu changes what your cursor is on.

In my opinion (you might differ), this is also a bug. If the menu is still populating, Enter should apply the first (default) item in the list, whatever that is, not the second or third.

https://community.logos.com/discussion/comment/1169479#Comment_1169479

"Look up the passage in your preferred Bible" seems fundamental to me.

It is there:

In an effort to increase usability, FL made the order of commands in the command box usage-specific. This means if you choose the Lookup command over the others for a number of times (say five times), it will be on top and thus will be executed when you just press enter.

EDIT: just did this several times and now it's reconfigured:

https://community.logos.com/discussion/comment/1169481#Comment_1169481

If the menu is still populating, Enter should apply the first (default) item in the list, whatever that is, not the second or third.

In my experience it does - I've never seen it otherwise. However, I may not always be 100% sure what the first item would be for a specific search - that way I, when I'm to hasty to wait for it to populate, I get to see the factbook more often than I like....

https://community.logos.com/discussion/comment/1169481#Comment_1169481

Enter should apply the first (default) item in the list, whatever that is, not the second or third.

If you have not positioned the cursor, it will take the first item. But if you have selected something further down the list, it believes that you placed your cursor where you want it. This is what I would expect.

https://community.logos.com/discussion/comment/1169492#Comment_1169492

I still maintain that the default actions of the search box need more work. I haven't had time to reply till now, but over the last week, this was confirmed several times again. Some of these have not been properly addressed by you (i.e., you could simply state, "yes, you are right; these are bugs or these are undesired and they need to be fixed.").

A. For example, trying to search for "O God, you are my God" (reference from Psalm 63:1), before the default action was to bring up the fuzzy Bible search. Now it brings you to a search for Factbook for "God". This is undesired; someone else in another thread mentioned the same, and the same is true in this thread too (NB.Mick mentioned that Factbook comes up too often). (This is when I am offline; I am not sure if the same is true online, though my guess is yes. I am aware that fuzzy search is an online search.)

B. Wanting to do a search for a passage with Shift-Enter, if you type fast, you have to type "Shift-Enter" twice. The same goes for Ctrl-Enter.

C. I have found that if I work offline, I get a better (i.e., consistent) response for looking up text citations in the search box. However, if the passage has a corresponding article in the Factbook, it opens up to that article instead of to the passage I want. See the difference between Exodus 13:17 and Exodus 13:16. This difference is undesired. It should be consistent.

Which brings me to my main request again: fix bug B above, and then add a shortcut similar to this for "Go to X_Citation in preferred Bible", such as Alt-Enter.

Thanks for your time and for your responses.

https://community.logos.com/discussion/comment/1170571#Comment_1170571

if the passage has a corresponding article in the Factbook, it opens up to that article instead of to the passage I want. See the difference between Exodus 13:17 and Exodus 13:16. This difference is undesired. It should be consistent.

For me it is consistent, and Lookup is the pre-selected top entry of the list which will be executed when hitting return:

same as

if you consistently open the Lookup several times in a row after putting in bible references and letting the menu populate, it will stick on top for this type of entry.

trying to search for "O God, you are my God" (reference from Psalm 63:1), before the default action was to bring up the fuzzy Bible search. Now it brings you to a search for Factbook for "God".

I don't know why you are bringing fuzzy search of biblical phrases into this discussion about having a keyboard shortcut for Lookup (which I actually think would be a beneficial addition to have). Personally, I don't recall searching phrases from the Command/Go-Box at all. Of course, entering this will offer Factbook over the search:

This is not only because Factbook comes first in the default order of commands for the box (after all, FL believes it is a very valuable tool that helps users a lot by informing them and/or directing them to the place they are likely get the info they want), but also because Search usually comes last in this default sort order.

I suspect this order will probably change when one enters phrases and consistently selects e.g. the search in the bible for several times in a row. But it's much more easy than that: just enter the phrase and click the search button instead of waiting for the list to come up, when you want a search to occur.

https://community.logos.com/discussion/comment/1170572#Comment_1170572

Hello again NB, once again I did not have opportunity to reply till now.

You are right, I should not have brought up the fuzzy Bible search in this thread. My general frustration is that Logos's new (and valuable) tool of Factbook has broken things. I understand that you are rightly proud of your new tool, but the command box "pushes" it too much, as I have shared in this thread. To further illustrate what I mean, keep reading.

Yes, you can train the command box to look up a given reference by default. I understand that. But the problem is that you have to redo the training for each and every reference for which Factbook has an entry. For example, after I had trained the command box to open the references in my preferred Bible, I had to redo that for at least the following four references over the week. 1 Samuel 15:22. Numbers 15:39. Matthew 11:1. Romans 15. The reason is because they have a Factbook entry. That is once again undesirable. Why should I have to think about that every time? Computers should just "work" every time. Buggy or inconsistent results means more programming work is needed. (I have done a lot of computer programming in the past.)

Thanks, Matt.

After writing this, I tried to get it to "fail" as I described above by typing other references for which Factbook had articles. I could not! But I do know this happened multiple times like I describe above. So either Logos was updated in the meantime or the further "training" made the search box results more consistent.

Dave Hooton

https://community.logos.com/discussion/comment/1170895#Comment_1170895

Yes, you can train the command box to look up a given reference by default. I understand that. But the problem is that you have to redo the training for each and every reference for which Factbook has an entry.

I underststand your frustration, for the training works for repeated references whilst a new reference seems to favour Factbook e.g. Neh 7, Neh 8 are trained for a Lookup but Neh 8:2 favours Factbook. Once entered, it was trained to a Lookup for 1 Sam 15:22, Num 15:39 & Mt 11:1. After a while*, though, it seemed to be trained for Lookup for any bible reference... until I entered Rev 12; where it favours a Layout!

This is in Logos 9.5 SR-1. I'll bring this thread to the attention of Faithlife.

* I've no idea how many repetitions produced this, or whether duplicate references were counted.

https://community.logos.com/discussion/comment/1170922#Comment_1170922

Thank-you. Very helpful.

https://community.logos.com/discussion/comment/1170946#Comment_1170946

One quick follow-up reply if anyone from Logos is reading this.

I believe it was the case before that if you were in a book, you could simply write the reference without the book. For example, if you were in Matthew, you could just write 5:47 to go to Matthew 5:47. You can't do this anymore. It goes to Factbook, and there is no way to train the command box to go to the reference. Small thing, but I think it was there before.

https://community.logos.com/discussion/comment/1171263#Comment_1171263

I believe it was the case before that if you were in a book, you could simply write the reference without the book. For example, if you were in Matthew, you could just write 5:47 to go to Matthew 5:47. You can't do this anymore.

I'm really not sure if this ever was the case, and an intentional use case or not.

https://community.logos.com/discussion/comment/1171263#Comment_1171263

For example, if you were in Matthew, you could just write 5:47 to go to Matthew 5:47.

I don't recall this being the case BUT the box did not clear out so one could reuse the Matthew that was there and just type the 5:47. I have not grown to like the auto-clear feature.

Andrew Batishko

https://community.logos.com/discussion/comment/1171263#Comment_1171263

I believe it was the case before that if you were in a book, you could simply write the reference without the book. For example, if you were in Matthew, you could just write 5:47 to go to Matthew 5:47. You can't do this anymore. It goes to Factbook, and there is no way to train the command box to go to the reference. Small thing, but I think it was there before.

This is possible in the navigation box in the resource panel, but not in the Go box.

https://community.logos.com/discussion/comment/1171288#Comment_1171288

For debugging' sake (and not because of impatience) I note two months after my original request that Factbook continues to pop up for different references from time to time, despite continued training of the search box. About four times last week that I remember.

I would be happy to be able to disable Factbook if that were an option (for other reasons too).

Dave Hooton

https://community.logos.com/discussion/comment/1177798#Comment_1177798

Factbook continues to pop up for different references from time to time, despite continued training of the search box.

As I said above, lookup can be consistently first for the same reference, otherwise it is consistently second to Factbook.

It would be worthwhile creating a suggestion for a Setting that would prefer Lookup consistently to Factbook.

https://community.logos.com/discussion/comment/1177844#Comment_1177844

Dave, how do I go about creating such a suggestion?

I note that I still often get Factbook first for a random Bible verse lookup, several times a day during normal use. Annoying.

Thanks for the reply, just saw your reply now.