-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automatically added file link has absolute instead of relative path #3476
Comments
Hi,
|
Hi, all of these 3 were set in Jabref 4.0 and are still set in the development version I'm using now (1. checked, 2. set to |
Is the location of the bibfile the same as /home/bitzer/papers? If not then uncheck the combobox |
Yes, the bibfile is in /home/bitzer/papers itself. Also the issue persists in the newest version JabRef-4.1-dev--snapshot--2017-12-08--master--6f39151a7.jar |
Ah I now can reproduce your behavior. It is the auto link which adds it as absolute path. If you manually select the file, it is correct. I will be working on a fix for this |
Cool, thank you! |
JabRef 4.1-dev--snapshot--2017-11-30--master--d45d7ca38
Linux 3.16.0-38-generic amd64
Java 1.8.0_151
on Mint 17 (Ubuntu 14.04)
Steps to reproduce:
I just switched from v4.0 to the latest development version, because Medline import did not work in v4.0 anymore. Unfortunately, now files appear to be added with absolute paths to the library. E.g., I added entry Lake2016 and Jabref now automatically adds the corresponding file as
/home/bitzer/papers/Lake2016.pdf
instead of asLake2016.pdf
as before. So I have to manually edit the file link to get the relative path. Is that intended behaviour and how do I get Jabref to automatically add relative links again?The text was updated successfully, but these errors were encountered: