JabFox does not import into open .bib in JabRef if JabRef is already open

[partha-deb]

Using JabRef, Firefox and JabFox on Window 10. When JabRef is closed, JabFox works as expected. But, when JabRef is already open, JabRef seems to go through Zotero but then does not import into the open instance of JabRef. JabRef is "listening" to port 5050. Any suggestions? Thanks.

[tobiasdiez]

If you have JabRef open and double click a bib file in Windows Explorer, does JabRef uses the previously opened instance or opens a new one? Which JabRef version are you using?

[partha-deb]

Hi Tobias,

Thanks for your attention. To answer your questions:

1. when JabRef is open and I double click a bib file, it opens in the
   same instance - as a new tab - in JabRef.
2. JabRef is version 3.3.

Best.

Partha

On 6/20/2016 9:10 AM, Tobias Diez wrote:

If you have JabRef open and double click a bib file in Windows
Explorer, does JabRef uses the previously opened instance or opens a
new one? Which JabRef version are you using?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#27 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFf9TKf4eg1466f2Ysd3ikAbDdvGCRkSks5qNpE2gaJpZM4I4a7f.

Partha Deb
Professor of Economics
Director of Graduate Studies
Hunter College
ph: (212) 772-5435
fax: (212) 772-5398
http://econ.hunter.cuny.edu/parthadeb/

Emancipate yourselves from mental slavery
None but ourselves can free our minds.
- Bob Marley

[tobiasdiez]

Thanks Partha for the follow-up. Sadly, I have no real idea about the reason for this issue. You might try:

• make sure that only one version of JabRef is installed and that the path in the JabFox preferences is set correctly
• update to JabRef 3.4
• change the port from 5050 to something else
• open JabRef and run the following command path-to-jabref.exe --importToOpen path-to-some-bib. Does JabRef now uses the previously opened instance or opens a new one?

[tobiasdiez]

Closing this issue due to inactivity 💤
Please reopen the issue with additional information if the problem persists.

Moreover, I think this issue is a consequence of JabRef/jabref#1554.