Skip to content

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

Closed
1 task done
m-mauersberger opened this issue Mar 12, 2021 · 6 comments · Fixed by #9000
Closed
1 task done

Automatically saving shared library will not be remembered #7516

m-mauersberger opened this issue Mar 12, 2021 · 6 comments · Fixed by #9000

Comments

@m-mauersberger
Copy link
Contributor

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:

  1. Open a shared database, tick the 'automatically save the library to'.
  2. See how it works properly.
  3. Reopen the database: You have to type in the local BIB file again.

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?

@Siedlerchr Siedlerchr added component: shared-database [outdated] type: bug Confirmed bugs or reports that are very likely to be bugs labels Mar 12, 2021
@ruanych
Copy link
Contributor

ruanych commented Apr 25, 2021

@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?

@m-mauersberger
Copy link
Contributor Author

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.

Copy link
Contributor

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.

@Siedlerchr Siedlerchr reopened this Apr 14, 2025
@Siedlerchr
Copy link
Member

@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 Siedlerchr moved this from Done to Normal priority in Prioritization Apr 14, 2025
@github-project-automation github-project-automation bot moved this from Normal priority to Done in Prioritization Apr 14, 2025
@koppor
Copy link
Member

koppor commented Apr 14, 2025

@Siedlerchr its not amok (killing multiple victims), but only shot wrong once?

@Siedlerchr
Copy link
Member

Siedlerchr commented Apr 14, 2025 via email

@koppor koppor removed the [outdated] type: bug Confirmed bugs or reports that are very likely to be bugs label Apr 14, 2025
@koppor koppor removed their assignment Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants