Skip to content
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

Can JabRef automatic save (.bak,.sav) file in ~/.cache/jabref/ rather than the directory of the bib file #6688

Closed
hebinhao1993 opened this issue Jul 15, 2020 · 4 comments
Labels
[outdated] type: feature platform: linux status: freeze Issues posponed to a (much) later future status: stale Issues marked by a bot as "stale". All issues need to be investigated manually.

Comments

@hebinhao1993
Copy link

JabRef will genereate .bak and .sav file in the directory of the bib file. Can JabRef support generate these file in the diretory like ~/.cache/jabref/

@Siedlerchr
Copy link
Member

Currently not, but we are trying to change that backup concept as it can lead to timing issues when autosave is enabled,
Refs #6453

@hebinhao1993
Copy link
Author

Thank you for your reply.

@koppor
Copy link
Member

koppor commented Jul 16, 2020

On Windows, there could be %APPDATA% used.

@github-actions github-actions bot added the status: stale Issues marked by a bot as "stale". All issues need to be investigated manually. label Jan 12, 2021
@koppor koppor added the status: freeze Issues posponed to a (much) later future label Jan 12, 2021
@koppor
Copy link
Member

koppor commented Jan 12, 2021

@hebinhao1993 We know that this is an uncommon concept at users in the computer science field. However, we have many users in other fields. They do not know such directories. It is easier for them to have the backup file nearby.

Note that https://gitignore.io is fully aware of these extensions - they will be ignored at a git commit if you use their generated .gitignore file: https://www.toptal.com/developers/gitignore/api/jabref

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[outdated] type: feature platform: linux status: freeze Issues posponed to a (much) later future status: stale Issues marked by a bot as "stale". All issues need to be investigated manually.
Projects
None yet
Development

No branches or pull requests

3 participants