You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made a backup of my libraries before testing the latest development version.
I have tested the latest development version and the problem persists
Steps to reproduce the behaviour
This seems to occur on Windows only if pwsh.exe is not installed, but powershell.exe installed.
Issue
The Jabref Browser Extension (Firefox) shows "Error while sending to JabRef" and no reaction from the client at all (either opened or not).
Possible Cause
This change on buildres/windows/JabRefHost.bat: JabRef/jabref#8432
There is probably an issue with the errorlevel check.
If I change the file back to only the @powershell.exe command, it works.
Appendix
...
Log File
Paste an excerpt of your log file here
The text was updated successfully, but these errors were encountered:
Thanks for the investigation @Tobi0! I think you are right, the second %errorlevel% does not reflect the outcome of the second test. In fact, a similar question has been raised here https://stackoverflow.com/questions/50348437/wrong-value-of-errorlevel-in-nested-if-in-bat-file. Could you please try the workaround/fix posted there, and if it indeed works open a PR at the jabref repo? That would be awesome!
JabRef version
5.6 (latest release)
Operating system
Windows
Details on version and operating system
Windows 10 20H2 19042.1706
Checked with the latest development build
Steps to reproduce the behaviour
This seems to occur on Windows only if
pwsh.exe
is not installed, butpowershell.exe
installed.Issue
The Jabref Browser Extension (Firefox) shows "Error while sending to JabRef" and no reaction from the client at all (either opened or not).
Possible Cause
This change on
buildres/windows/JabRefHost.bat
: JabRef/jabref#8432There is probably an issue with the errorlevel check.
If I change the file back to only the
@powershell.exe
command, it works.Appendix
...
Log File
The text was updated successfully, but these errors were encountered: