Do not see any bibtex entries about helm-bibtex HOT 8 CLOSED

Hi, thanks for reporting. Your BibTeX file works in my setup. Could you please provide your helm-bibtex configuration and version of Emacs?

from helm-bibtex.

Could you please load parsebib manually (load "parsebib.el") and see if this helps (see #23 for context).

from helm-bibtex.

Hi,

Thanks for the quick help. The manual (load "parsebib.el") fixed the issue.

My emacs version is 24.4.1, parsebib version is 20141219.1410.
If it is still relevant my config was just:

(autoload 'helm-bibtex "helm-bibtex" "" t)
(setq helm-bibtex-bibliography "~/Dropbox/Arbeit/Papers/bibliography.bib")

from helm-bibtex.

Hi @joostkremers, it seems there are more users who are having trouble when using parsebib with helm-bibtex. helm-bibtex uses two functions from parsebib.el: parsebib-find-next-item and parsebib-read-entry. Only the former has an autoload cookie. Could this cause the problem?

from helm-bibtex.

Hi, sorry for the late reply. Holidays 'n' all...

Although I added the autoload cookies, I'm actually pretty sure they're not really needed. After all, libraries such as dash don't have any autoload cookies and they work fine.

As to what is causing the issues then, I'm really not sure. First thing I'd try is to restart Emacs. Sometimes old compiled code (not necessarily .elc files, also code in e.g., macros) can cause strange, inexplicable things to happen. Also try (re)installing parsebib from a fresh Emacs instance. (The problem may be related to an incorrectly installed parsebib.el.)

from helm-bibtex.

I also think that the cookies are not needed. I read the documentation about autoloading but didn't find anything enlightening. You added autoload cookies for some of the functions and I though that this might perhaps be interpreted to implicitely mean that the other functions should not be automatically autoloaded. That's pure speculation, though.

I agree that this issue is easy to fix but ideally users shouldn't experience this problem in the first place. I think the strong expectation is that you install stuff through MELPA and that it just works without any manual intervention or restarting of Emacs.

from helm-bibtex.

I agree that users should not be seeing this problem, but since I’m not able to reproduce it, I cannot debug it. I installed parsebib myself through Melpa as a dependency of Ebib and had no issues. I also haven’t had any reports about problems (yet!) from people upgrading Ebib to the version using parsebib (knock on wood…)

This, combined with the fact that manually loading parsebib.el or reinstalling the parsebib package appears to solve the issue, leads me to believe that parsebib itself is not the cause of the problem. Rather, something seems to go wrong with the compilation. But without access to an actual Emacs session displaying the problem, it’s impossible to tell what.

If any new information turns up, or anyone can make a suggestion as to what I can do to solve the issue, I’ll gladly see what I can do.

BTW, I'm removing the autoload cookies again. If that had actually solved anything, the current issue wouldn't have existed...

from helm-bibtex.

Ok, I'm closing this issue for now.

from helm-bibtex.