-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add a configuration option to prevent proactive reloading #297
Comments
While I sympathize, I'm worried about inflation of customization variables; we already have too many if you ask me. Perhaps a better solution would be to reload the bibliography in the background so that users don't have to wait? This could be implemented using threads which were introduced in Emacs 26. |
Titus von der Malsburg <[email protected]> writes:
While I sympathize, I'm worried about inflation of customization
variables; we already have too many if you ask me. Perhaps a better
solution would be to reload the bibliography in the background so that
users don't have to wait? This could be implemented using threads
which were introduced in Emacs 26.
Indeed, that would be a good compromise. I understand the desire to keep
the number of customisation variables to a minimum but I would argue
that reloading on each save is such an invasive behaviour that it does
warrant making an exception.
Marcin
|
Could you make a PR please? |
Sure. I think that's all it takes: PR #301. |
If I may, I'd like to raise this issue again. I've fixed what I think was a bug in the original PR and added a longer docstring that specifically addresses @tmalsburg question:
The answer is yes: changing the value of the variable after loading helm-bibtex has no effect. This is the PR: #443 |
See |
While I understand its rationale, I find the new proactive reloading of bibliography quite frustrating as it kicks in every time I save the BIB file. I wonder whether adding a variable that controls this behaviour would be an option?
The text was updated successfully, but these errors were encountered: