From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using the standalone ConTeXt, how do I add access to my texmf-local tree
Date: Sun, 1 Mar 2015 23:04:08 +0100 [thread overview]
Message-ID: <C3EF5C05-D0DE-4623-9D33-B38F2A8A23EA@gmail.com> (raw)
In-Reply-To: <6F7CEDB6-DB5A-4FAF-A4A2-A7F959081161@rna.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1372 bytes --]
> Am 01.03.2015 um 22:56 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>
> On 01 Mar 2015, at 11:59, Hans Hagen <pragma@wxs.nl <mailto:pragma@wxs.nl>> wrote:
>
>> On 3/1/2015 11:48 AM, Gerben Wierda wrote:
>>> I’m trying to migrate to mkiv and I’m running into a host of troubles.
>>> Here is one:
>>>
>>> publications > wrote a new auxiliary file 'prd_book.aux'
>>> This is BibTeX, Version 0.99d (TeX Live 2014)
>>> The top-level auxiliary file: prd_book.aux
>>> The style file: cont-no.bst
>>> I couldn't open database file gwierda.bib
>>> ---line 3 of file prd_book.aux
>>> : \bibdata{gwierda
>>> : }
>>>
>>>
>>> The reason is that by using this command
>>>
>>> (. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
>>>
>>> I may have the latest ConTeXt compiling test.tex (it just adds that to
>>> te front of PATH), but I’ve lost access to additions I keep in
>>> /usr/local/texlive/texmf-local and ~/Library/texmf)
>>>
>>> How do I make sure the standalone ConTeXt gets access to these?
>>
>> you can try \usemodule[oldbibtex]
>
> Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree.
>
> I couldn't open database file gwierda.bib
> ---line 3 of file prd_book.aux
> : \bibdata{gwierda
> : }
Where do you have your bib file?
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 4786 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-03-01 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 10:48 Gerben Wierda
2015-03-01 10:59 ` Hans Hagen
2015-03-01 21:56 ` Gerben Wierda
2015-03-01 22:04 ` Wolfgang Schuster [this message]
2015-03-01 22:16 ` Gerben Wierda
2015-03-01 23:15 ` Wolfgang Schuster
2015-03-02 6:42 ` Gerben Wierda
2015-03-02 8:36 ` Hans Hagen
2015-03-04 13:52 ` Ulrike Fischer
2015-03-04 16:58 ` Hans Hagen
2015-03-04 18:06 ` Ulrike Fischer
2015-03-05 0:40 ` Hans Hagen
2015-03-05 9:34 ` Ulrike Fischer
2015-03-06 8:22 ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-03-06 9:52 ` Hans Hagen
2015-03-06 9:59 ` Hans Hagen
2015-03-06 12:08 ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-03-06 13:45 ` Hans Hagen
2015-03-06 14:14 ` Procházka Lukáš Ing. - Pontex s. r. o.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C3EF5C05-D0DE-4623-9D33-B38F2A8A23EA@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).