NEW: OT391 The Shema, by Mark Futato

Our newest pre-pub is OT391 The Shema, taught by Old Testament scholar, Dr. Mark Futato.

Explore the depths of the Shema (Deut 6:4–9) and learn why this text is sacred not only to Jews but to Christians as well. Discover why Jesus quoted the Shema when asked what the greatest commandment is. Gain insight into the covenantal, volitional, and emotional aspects of love and what it means to “love the Lord your God with all your heart, all your soul, and all your strength.”

Find more posts tagged with

Mobile Education

Comments

Little Ike

I am going through the Logos Mobil Education course OT391. In segment 6 in the Todd Bishop video, I am not able to duplicate his result although I have watched the video several times and followed his clicks click for click. At around time marker 3:40, Todd wants to demonstrate how we can narrow the number of hits in the Bible Word Study to one book of the bible. In the video, he says the best way to do this is do an inline search using the Bible search and typing h:shema in the find box. When he types h:shema in the find box, he receives a drop down list that include entries that do not show up when I do a drop down box. After he selects his entry, the find box replaces the h:shema with the words Lemma etc. I have no choice but to select the Hebrew word for shema and I receive zero hits. h:shema is replaced with the Hebrew word I selected in the find box. To make matters worse, I started experimenting to see if I am on an update that requires a different way to do a search against a Hebrew word. I did a morph inline search on the word shema using the context search (inline using this resource). Now any time I try to do an inline search from the context menu, it changes from Bible to Morp and starts the search before I can stop it. Any one has any idea what is happening? By the way, I tried this on my desktop computer and the same thing is happening on it.

Thom Blair (Faithlife)

https://community.logos.com/discussion/comment/772379#Comment_772379

The screencast is correct. A future update to our software will resolve this issue.