Re: [AUCTeX] BIBINPUTS

[Greg BOGNAR]

On Sat, 28 Jan 2006, Ralf Angeli wrote:

> * Greg BOGNAR (2006-01-28) writes:
> 
> >> * Greg BOGNAR (2006-01-26) writes:
> >
> >>> I have bibligraphy databases in a dedicated directory.  I set
> >>> BIBINPUTS for that directory.
> >
> >> How do you set BIBINPUTS?  In my case I have
> >> BIBINPUTS = .;$TEXMF/bibtex/bib//
> >> in /etc/texmf/texmf.cnf.
> >
> > Same here.  But I want to set it to ~/Documents/bibliographies or
> > something like that, not ~/texmf/bibtex/bib.  My bibliography
> > databases should be kept together with the rest of my documents.
> 
> So how do you set it?

In my .bashrc:

BIBINPUTS=.:$HOME/Documents/bibliographies//:

As I mentioned before, a latex job run from the terminal finds the 
databases, only Emacs doesn't.
 
> > Meanwhile, I got a solution from Fernando Tusell, I hope he does not
> > mind that I copy parts of his message here:
> >
> >> I had a problem similar to yours: starting a session under bash, I
> >> could find files pointed to by BIBINPUTS, but not otherwise.
> >
> >> It turned out that when I started Emacs from a graphical session in
> >> Gnome, the file .bashrc (where the environment variable BIBINPUTS is
> >> set) was not read. The simple fix in my case was to set BIBINPUTS in
> >> file .gnomerc (and later I found that making a link from .gnomerc to
> >> .bashrc also works, and I only have to change and maintain .bashrc).
> >
> > I use Fvwm, and the solution was the same: I just set BIBINPUTS again
> > in my .fvwm/config.  Now it all works.  But I doubt it has to do with
> > the graphical session; it does not work when I run Emacs without X.  
> > It seems that Emacs does not read .bashrc at all.
> 
> ,----[ bash(1) ]
> | When bash is invoked as an interactive login shell, or as a  non-inter-
> | active  shell with the --login option, it first reads and executes com-
> | mands from the file /etc/profile, if that file exists.   After  reading
> | that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile,
> | in that order, and reads and executes commands from the first one  that
> | exists  and  is  readable.  The --noprofile option may be used when the
> | shell is started to inhibit this behavior.
> `----
> 
> Perhaps you need to source .bashrc in .bash_profile.

Of course it is:

if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

Cheers,
Greg