Titus von der Malsburg

> and adding 256 directories to helm-bibtex-library-path is a little ... kludgey. You could do this automatically with two or three lines of elisp. > I will investigate the naming...

I haven't tried it but it should be ok.

One thing I don't understand is this: If you make a new entry with Papers, you end up with a PDF with a cryptic name but you will also have...

Elaborating my comment above: For example, we could allow the user to specify custom transformations that are applied to the BibTeX file before it is parsed by helm-bibtex. The benefit...

Re your comment: That sounds like a good solution from the helm-bibtex perspective.

But note that Dropbox doesn't understand softlinks. Last time I tried it, Dropbox replaced softlinks by hard copies of the files. Since your group seems to rely on Dropbox, this...

Re other cloud services: they may very well have the same issues with softlinks. The underlying problem is that not all file systems support softlinks (e.g., FAT32) and cloud services...

I intentionally disabled highlighting because I find it distracting: ``` elisp (defvar helm-source-fallback-options '((name . "Fallback options") (match (lambda (_candidate) t)) (candidates . helm-bibtex-fallback-candidates) (no-matchplugin) (nohighlight) (action . helm-bibtex-fallback-action)) "Source...

Hm, not sure what is going on. I also noticed that some of my other helm sources either show or not show highlighting and I can't find out why. Perhaps,...

I have never seen a formal and complete definition of the BibTeX format, but my impression was that each field is expected to occur only once in an entry. Elsevier...