Re: [Ebib-users] Configuration of Ebib with ebibrc

[Joost K. <joo...@fa...>]

Hi Phil,

Your case is getting more and more puzzling...

> I have come to the conclusion that Ebib doesn't like remote files. I
> have attached the latest version of my ebibrc file. I said before that
> I use a laptop and a desktop. My .emacs.d directory is stored on
> Dropbox, this directory is symlinked to each computer, This seems to
> work fine for Emacs customisation; each computer has an identical
> version of Emacs.

Note that the files in your Dropbox folder aren't really remote files:
they are stored on your local disk and kept in sync with the Dropbox
server.

But what's puzzling to me is that my setup seems to be the same as
yours. My .emacs.d is a symlink to a folder inside my Dropbox folder
(~/Dropbox/Settings/emacs.d to be exact).

I've also switched over to per-directory keywords files, just for
testing, and so far haven't run into any trouble. When I copy a .bib
file to temporary directory and open it in Ebib, all the keywords are
shown in red as expected, and when I hit `K s` on an entry, the keywords
are stored and saved.


> Rather than use a per-directory keywords file I have been testing a
> single keywords file. But Ebib doesn't seem not be able to find the
> ebib-keywords.txt file if it is stored in a symlinked .emacs.d
> directory. Local files on each computer seem to work fine, but when I
> moved it over to the .emacs.d directory, all the keywords appear in
> red, which seems to me to indicate that the keywords list has not been
> accessed.

Yes, it does... Like I said, your case is very puzzling... Note that
changing the setting `ebib-keywords-file` may require a complete restart
of Emacs (not just Ebib) to take effect. (I'm not entirely sure why that
is the case, something to do with the way Emacs handles customisable
variables, I think.)

Could you check the value of the variables `ebib-keywords-file` and
`ebib--keywords-files-alist` (note the double dash in the latter) while
Ebib is running? The easiest way would be to use the *scratch* buffer
(provided you haven't customised its major mode). So start Ebib and
lower it again, then switch to the *scratch* buffer and type the name of
the variable followed by `C-j`. Then the variable's value should appear
on the next line. (If it's very long, its value will be collapsed, which
is indicated with three dots near the end. You can put the cursor on it
and hit RETRUN to make it visible).

> I have another observation. I had a bib file, the first line of which
> was @comment. This file didn't open correctly, but when I edited the
> @comment out, all was well.

Could you send me the .bib file with the @comment, or at least the
@comment itself? There shouldn't be any problem opening a file with a
comment on the first line.

Best,

Joost




-- 
Joost Kremers
Life has its moments