-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Automatically saving shared library will not be remembered #7516
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
Comments
@Siedlerchr After my experiment, open the .bib file which is bounded to the shared database will automatically update to the latest version in the database. However, the database will not save after modifying this .bib file. I still don't quite understand what this issue refers to. Could you please give me some help? |
It is about selecting the Bib file in the opening dialog of shared database connection (where you also can type in server address, user name and so on). This tick and the corresponding file path should be remembered like the other inputs in this dialog. |
Closed by #12934 Please head to https://builds.jabref.org/main to try it out. For any feedback, add a comment to the pull request at #12934. |
@koppor I think your bot action with "closed by checking is running amok" because it seems to interpret the issue numbers from CSL to our repo |
@Siedlerchr its not amok (killing multiple victims), but only shot wrong once? |
Seems like
Oliver Kopp ***@***.***> schrieb am Mo., 14. Apr. 2025, 16:57:
… @Siedlerchr <https://github.com/Siedlerchr> its not amok (killing
multiple victims), but only shot wrong once?
—
Reply to this email directly, view it on GitHub
<#7516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOFZGFU4VXBY3UJXFOHYL2ZPEEDAVCNFSM6AAAAAB3DFZN3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBRHE4TSMRVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
*koppor* left a comment (JabRef/jabref#7516)
<#7516 (comment)>
@Siedlerchr <https://github.com/Siedlerchr> its not amok (killing
multiple victims), but only shot wrong once?
—
Reply to this email directly, view it on GitHub
<#7516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACOFZGFU4VXBY3UJXFOHYL2ZPEEDAVCNFSM6AAAAAB3DFZN3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBRHE4TSMRVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
JabRef 5.3--2021-03-11--8bb7668
Linux 4.12.14-lp151.28.91-default amd64 (openSUSE 15.1 Leap)
Java 15.0.2
JavaFX 16+8
Steps to reproduce the behavior:
I briefly wondered whether this is a bug. But I think the functionality itself assumes that you do not have to specify the local database file again. The tick should be remembered. How do you think?
The text was updated successfully, but these errors were encountered: