Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

JabRef 3.3 on windows 10 cannot call texstudio.exe to push entries #1400

Closed
ghost opened this issue May 13, 2016 · 7 comments
Closed

JabRef 3.3 on windows 10 cannot call texstudio.exe to push entries #1400

ghost opened this issue May 13, 2016 · 7 comments
Labels
[outdated] type: bug Confirmed bugs or reports that are very likely to be bugs

Comments

@ghost
Copy link

ghost commented May 13, 2016

JabRef 3.3 on Windows 10

Steps to reproduce:

  1. Ctrl-L: Push entries to external application (TexStudio)

Error: cannot call the executable C:\Program Files\TexStudio\texstudio****.exe

The executable file should be C:\Program Files\TexStudio\texstudio.exe
But JabRef 3.3 added a slash "" before ".exe", which I believe caused the problem.
Reinstall JabRef 3.2, it works fine.

@stefan-kolb stefan-kolb added the [outdated] type: bug Confirmed bugs or reports that are very likely to be bugs label May 14, 2016
@stefan-kolb
Copy link
Member

Thank you for your report 😄
I can reproduce the behavior and we will work on a fix for this issue. Stay tuned.

@stefan-kolb
Copy link
Member

This should be fixed in current master. Please try the latest build from http://builds.jabref.org/master.

@matthiasgeiger
Copy link
Member

@stefan-kolb CHANGELOG 😉

@ghost
Copy link
Author

ghost commented May 14, 2016

Great! I am amazed by how quickly an issue could be fixed. Thank you for your great work!

@michaelemery
Copy link

michaelemery commented Mar 28, 2017

Having the same problem on macOS Sierra using JabRef 3.8.2
Path set to: /Applications/texstudio.app (selected using browse button)
Selecting texstudio from menu gives error:
Could not call executable '/Applications/textstudio.app'

@stefan-kolb
Copy link
Member

@michaelemery This seems like a different issue as it's on OSX. Feel free to open a separate issue.

@matthiasgeiger
Copy link
Member

@michaelemery Before opening a new issue please check #2613 as this seems to cover exactly your problem. Thanks!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
[outdated] type: bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

3 participants