Setting up Louw-Nida to move with BDAG?

Hi all!
I'm trying to incorporate semantic domains work into my Greek study. I've owned but never really used Louw-Nida before.
For my setup, I have BDAG as my primary lexicon. I link DBL Greek as a secondary lexicon as a "B" set to BDAG. However, LN doesn't move with BDAG when looking up words. If I prioritize LN over BDAG, then they both move, but since I want BDAG to be what pops to the top rather than LN, that workflow isn't as clean as I'd like it to be.
Is there a way to get LN to keep in-step with BDAG, but without being the main prioritized Greek lexicon? It's been a long while since I messed with some of the mechanics of this (more of a set-it-and-forget-it kind of guy), so I'm sure there's something I'm missing or doing wrong.
The Greek text I'm working with is the NA27 w/ Grammcord.
Thanks!
Comments
-
Have you linked LN with BDAG? BDAG is my top Greek lexicon. If I link connect BDAF, DBL Greek, and LN to the same linkset they all move together for me.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Adding, when I link BDAG and LN, moving either one, moves the other (priority should be irrelevant for linking; it's matching indices).
Now, it is true, (1) LN is a subset of BDAG (the lemma must be in both), and (2) LN lemmas can be strange, such as 'ἀστραπή (2)'
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0